SERVER_ERROR proxy write to downstream

Reinstalled it, and this time created the first bucked with no replication from the start, and get the same problem

Here's the log:

Event Module Code Time
Created bucket "default" of type: membase
menelaus_web012 01:20:34 - Thu May 26, 2011
Client-side error-report for user "Administrator" on node 'ns_1@192.168.1.102':
User-Agent:Mozilla/5.0 (Windows NT 5.1) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
Got unhandled error: Uncaught TypeError: Cannot call method 'getResponseHeader' of undefined
At: http://localhost:8091/js/all.js:13063
Backtrace:
Function: collectBacktraceViaCaller
Args:

---------
Function: appOnError
Args:
"Uncaught TypeError: Cannot call method 'getResponseHeader' of undefined"
"http://localhost:8091/js/all.js"
13063
---------

menelaus_web102 01:18:08 - Thu May 26, 2011
Membase Server has started on web port 8091 on node 'ns_1@192.168.1.102'. menelaus_app001 01:18:08 - Thu May 26, 2011
Initial otp cookie generated: mcndwhopsyqsltou ns_node_disco003 01:18:07 - Thu May 26, 2011

Cristian, unfortunately we don't currently support Windows XP and in fact have some known issues with it.

Can you try installing on Windows Server 2008 or Windows 7 and see if that resolves your issues?

Perry

Hi Perry,

Thanks for you reply!

Unfortunately I dont have any Windows Server 2008 nor Windows 7 computer here. But I'm going to try it on a Centos Linux server on EC2 when I have the time.

Now I'm using SimpleDB, and the plan was to see if Membase would be a more cost effective solution, that is, running several EC2 instances with Membase vs. keep using SimpleDB. And to see how much work it'd require to maintain the Membase instances working fine and automatically scaling in and out.

Cheers!,

Cristian

Thanks Cristian, let us know how it goes.

We've heard of lots of customers who use Membase after switching from SimpleDB for the costs, the performance gains and also the ability to have more "control" over your own data.

Perry