Home | Forums | Membase | Membase Server 1.7.x

Port server moxi on node 'ns_1@10.249.212.166' exited with status 139

5 replies [Last post]
Wed, 11/16/2011 - 03:42
zhouxin
Offline
Joined: 11/16/2011
Groups: None

Port server moxi on node 'ns_1@10.249.212.186' exited with status 139. Restarting. Messages: 2011-11-16 18:38:22: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (13)
2011-11-16 18:38:22: (cproxy_config.c.326) env: MOXI_SASL_PLAIN_PWD (11)

Port server moxi on node 'ns_1@10.249.212.206' exited with status 139. Restarting. Messages: 2011-11-16 18:38:46: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (13)
2011-11-16 18:38:46: (cproxy_config.c.326) env: MOXI_SASL_PLAIN_PWD (11)

how can i do?

Top
Fri, 11/25/2011 - 13:55
ingenthr
Offline
Joined: 03/16/2010
Groups:

You don't say anything about which version you're running. There were some bugs fixed in the most recent releases (1.7.1 and 1.7.2), but we'd need more info (core file, etc.) to diagnose further.

Top
Tue, 01/17/2012 - 14:16
enkrypt3d
Offline
Joined: 11/01/2011
Groups: None

I'm seeing the exact same errors for no reason whatsoever on version 1.7.2r-20-g6604356....... please advise as this doesn't make any sense......

Top
Thu, 01/26/2012 - 08:04
LittleBuddha87
Offline
Joined: 11/17/2011
Groups: None

Hi i have the same problem =>

Port server moxi on node 'ns_1@127.0.0.1' exited with status 139. Restarting.
Messages: 2012-01-25 18:33:01: (cproxy_config.c.317) env: MOXI_SASL_PLAIN_USR (5)
2012-01-25 18:33:01: (cproxy_config.c.326) env: MOXI_SASL_PLAIN_PWD (14)

Top
Wed, 02/01/2012 - 15:08
enkrypt3d
Offline
Joined: 11/01/2011
Groups: None

Same issue here running on 1.7.2..... Upgrading to 1.8.0 is kind of a pain as you have to completely remove membase and install couchbase. there is no more membase. :(

Top
Wed, 02/01/2012 - 17:28
ingenthr
Offline
Joined: 03/16/2010
Groups:

You can actually do a "rolling" upgrade from Membase Server 1.7.2 to Couchbase Server 1.8.0.

See http://www.couchbase.com/docs/couchbase-manual-1.8/couchbase-getting-sta...

I'm going to check with the rest of the team to see if there are any changes here which may have fixed this issue.

Status 139 is segmentation violation (i.e. segfault). The good part here is that Membase Server is restarting the Moxi service so it should just appear as a momentary interruption to any clients. That said, we'd need to get more information on the crash. The installer does, by default, increase the core file size. Does your system have a core file for moxi? If so, can you open an issue at couchbase.com/issues and attach it?

Top