Installed Windows Server 2003 but no response

Hello,

Thanks for you post. What port are you connecting to via telnet?

bhawana

Thanks for the Reply Bhawana,

I was connecting via 11211

boboofid,

I hope your deployment is going smooth. Please don not hesitate to write to us if you come across any problems.

Would you mind sharing what  application are you building? Is this a new application or are you replcaing an existing solution? How much data do you expect?

-Bhawana

 boboofid, is there any Windows firewall in place here?

How many nodes are you attempting to run?

Thanks

Perry

Hello Perry,

There is not a windows firewall in place, the old Northscale Memcached server ran fine, also the memcached from jellycan works just fine.

I am trying to run a single node.

Thanks,

Kyle

 Thanks Kyle.  Can you send over the full output of http://<IP>:8091/diag where IP is the IP address of your Membase server?  You'll probably want to zip the output before sending.

Perry

Hello Bhawana,

The deployment is, frankly, not going smooth and has been a huge time sink. Given the professionalisim surrouding this product I was expecting it to work right out of the box and that expectation has not been met in my case. I can understand this is likely not the expirience of the general population but it is a huge letdown personally after the smooth expirience I had with the Northscale Memcached server.

I am not building a single application but seeking to make caching available to a suite of applications that are developed and maintained on a WIMP server by me and my team. This is an internal corporate application suite and so it does not need to scale to internet levels but our data load is still approximately Ooodles. We were looking to this product to patch a limitation we have where we have a single database server in the US and numerous PHP servers around the world with a single node running locally on each of the php servers to maintain a cache of slowly changing data and ease the slowdown we are expiriencing with the latency fo sheer distance.

Thanks,

Kyle

 Kyle, can you check to see what IP address your server currently has?  If it does not match 10.251.34.91 then I believe the problem has to do with the IP address changing after the first installation of the server.  We have a workaround here: http://wiki.membase.org/display/membase/Using+Membase+in+the+Cloud to let it use localhost.

If that's still not the problem, please send me the output of the diagnostic dump (perry -at- membase -dot- com) and I'll have a look.  I'm sure we can get this resolved for you...

Perry

Did you guys get this sorted ?

I am seeing exactly the same issue as the one here I believe
I am running a memcache server on MS Server 2003 R2 x64
I run a single node server , its definitely not an IP problem as I registered the node on 127.0.0.1.

ns_1@127.0.0.1:ns_memcached:374: Unable to connect: {error,
{badmatch,
{error,closed}}}, retrying.

PROGRESS REPORT <4975.118.0>

Can you help ... I would appreciate that

Rafal

Rafal, was the server working properly and then stopped or has it not functioned at all?

Can you please send the output of http://:8091/diag (you'll have to compress it) to perry -at- couchbase -dot- com?

Thanks.

Perry

Have sent you an email.
Thanks

After some investigation I figured that :
memcached.exe stops listening after I start the service

and when i start it from command line:

memcached.exe -p 11210 -v

i get the following :

168: sasl result code: -1
168: Unknown sasl response: -1
180: sasl result code: -1
180: Unknown sasl response: -1
192: sasl result code: -1
192: Unknown sasl response: -1
204: sasl result code: -1
204: Unknown sasl response: -1
216: sasl result code: -1
216: Unknown sasl response: -1
228: sasl result code: -1

Sounds like : http://techzone.couchbase.com/forums/thread/memcached-not-listening

any solution for this?

thanks

You'll actually need a bit more on the command-line to start this memcached properly:
memcached.exe –vvv –p –E /ep.so –r –e “dbname=/default-data/default”

I have your logs and am working with our engineers to diagnose. As I mentioned, we don't officially support Windows 2003 and so we need to spend a bit more time reproducing that environment. It would be really helpful to know whether this is working properly for you on a more recent operating system.

Perry

Thanks Perry , much appreciate it
This is working perfectly on 2008 Win Server
Had some issues on 2003 Win Server Virtual Machine but finally got it working
Still not working on all 3 machines - 2003 Win Server (Physical Box). We do have 3 network interfaces on each of these boxes , not sure if that is making any difference. To make sure there is no ip conflict or so I disabled 2 adapters on one of these boxes

rafal

Hi Perry,

I think I have made some progress on this
I managed to start memcached.exe manually on port 11210

 memcached.exe -vvv -p 11210 -E "C:\Program Files\Membase\Server\bin\bucket_engine\bucket_engine.so" -r

and the telnet succeeded  telnet localhost 11210

the problem now is when i start membaseserver it creates another memcached process

so i think it might be working if i start it from command line as I did for memcached

how can i start moxi etc from the command line

I also tried

start membaseserver
kill the memcache process
start if from command line but then again 2 memcached processes are running and the console outputs:

2720: going from conn_parse_cmd to conn_nread
2720 - Running task: (conn_nread)
2720 - Running task: (conn_nread)
2720 - Running task: (conn_nread)
2720 - Running task: (conn_nread)
2720: mech: ``PLAIN'' with 14 bytes of data
2720: sasl result code: -1
2720: Unknown sasl response: -1
>2720 Writing an error: Auth failure
<2720 Writing bin response:
<2720 0x81 0x21 0x00 0x00
<2720 0x00 0x00 0x00 0x20
<2720 0x00 0x00 0x00 0x0c
<2720 0x00 0x00 0x00 0x00
<2720 0x00 0x00 0x00 0x00
<2720 0x00 0x00 0x00 0x00

Regards,
Rafal