Home | Forums | Couchbase | Couchbase Server 1.8.x

Port server moxi on node exited with status X. Restarting.

4 replies [Last post]
Tue, 09/11/2012 - 10:31
scepak
Offline
Joined: 09/11/2012
Groups: None

Hi,

I'm getting this error on live servers Win Server 2003 32 bit & 2008 64 bit. 

Port server moxi on node 'ns_1@192.168.243.12' exited with status 3. Restarting. Messages: 2012-09-10 17:13:21: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (7)
2012-09-10 17:13:21: (cproxy_config.c.326) env: MOXI_SASL_PLAIN_PWD (9)
Assertion failed!
 
Program: d:\Program Files\Couchbase\Server\bin\moxi.exe
File: cproxy_protocol_b2b.c, Line 56
 
Expression: uc->noreply == false
 
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I couldn't find any help on the forum or anywhere else. Seems that moxi.exe crashes or is terminated and restarts but caching stops working.

It started happening after new code release + windows updates + server restart so it's a bit hard to track down. It happens under normal load.

Top
Thu, 09/13/2012 - 23:37
mikew
Offline
Joined: 03/14/2011
Groups:

Are you using 1.8.0 or 1.8.1?

Top
Fri, 09/14/2012 - 01:23
scepak
Offline
Joined: 09/11/2012
Groups: None

I was using 1.8.0 when it started happening and upgraded to 1.8.1 on one of the servers but it's still a problem.

Top
Mon, 09/17/2012 - 17:01
katana
Offline
Joined: 05/09/2012
Groups: None

doubt the Windows updates or Server restart have anything to do with this issue.

After moving to ver 1.8.1, are you seeing the errors in your Windows event log pointing to the exact same assert line#
cproxy_config.c.326 and cproxy_protocol_b2b.c, Line 56?

someone else seems to have reported a similar symptom too - http://www.couchbase.com/issues/browse/MB-5464

are you using the MOXI on the Couchbase Server side or the Client side?

If those MOXI crashes are resulting in Windows crash dump files, would be very curious to take a look at them to see what the stack looked like leading up to the crash. We should be able to make a few tunable changes (MOXI.CFG side) that will make this problem go away, atleast temporarily.

Top
Mon, 09/24/2012 - 08:25
scepak
Offline
Joined: 09/11/2012
Groups: None

I updated both to 1.8.1 now so would have to downgrade to answer your question.

That someone else is me.. :)

I'm using moxi on server side.

I don't have any crash dump files. There is a log event on win server 2008 but nothing in there. What tunable changes in moxi.cfg could I try?

Top