Couchbase
  • Why NoSQL?
  • Couchbase Server
  • Download
  • Resources
  • Careers
Home | Forums | Membase | Membase Server 1.6.x

Membase server randomly exiting/crashing

3 replies [Last post]
  • Login or register to post comments
Thu, 01/20/2011 - 15:15
vertigo
Offline
Joined: 01/17/2011
Groups: None

Hello there, We're currently running some tests to work out if membase is a viable solution for us. However we seem to be encountering random crashes/graceful exits. We can't determine exactly why this is but here is an output from browse_logs. Perhaps someone can point us in the right direction as to why this may be happening? Log is as follows:

PROGRESS REPORT <5650.7.0> 2011-01-20 14:56:05
===============================================================================
application mnesia
started_at 'ns_1@127.0.0.1'

CRASH REPORT <5650.116.0> 2011-01-20 14:56:05
===============================================================================
Crashing process
initial_call {ns_mnesia,init,['Argument__1']}
pid <5650.116.0>
registered_name []
error_info
{exit,{{case_clause,{aborted,{badarg,schema,unknown}}},
[{ns_mnesia,ensure_schema,0},
{ns_mnesia,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]},
[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}
ancestors [ns_server_sup,ns_server_cluster_sup,<5650.52.0>]
messages []
links [<5650.125.0>,<5650.72.0>]
dictionary []
trap_exit true
status running
heap_size 377
stack_size 24
reductions 257

SUPERVISOR REPORT <5650.72.0> 2011-01-20 14:56:05
===============================================================================
Reporting supervisor {local,ns_server_sup}

Child process
errorContext start_error
reason
{{case_clause,{aborted,{badarg,schema,unknown}}},
[{ns_mnesia,ensure_schema,0},
{ns_mnesia,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}
pid undefined
name ns_mnesia
start_function {ns_mnesia,start_link,[]}
restart_type permanent
shutdown 10000
child_type worker

ERROR REPORT <5650.99.0> 2011-01-20 14:56:05
===============================================================================
rb: ERROR! A report on bad form was encountered. It can not be printed to the log.

Details:
"2011-01-20 14:56:05" {{{2011,1,20},{14,56,5}},
{error_report,<5650.51.0>,
{<5650.99.0>,std_error,
{mochiweb_socket_server,235,
{child_error,shutdown}}}}}

rb: Logging resumed...

SUPERVISOR REPORT <5650.54.0> 2011-01-20 14:56:05
===============================================================================
Reporting supervisor {local,ns_server_cluster_sup}

Child process
errorContext start_error
reason shutdown
pid undefined
name ns_server_sup
start_function {ns_server_sup,start_link,[]}
restart_type permanent
shutdown infinity
child_type supervisor

INFO REPORT <5650.7.0> 2011-01-20 14:56:05
===============================================================================
application ns_server
exited {shutdown,{ns_server,start,[normal,[]]}}
type temporary

Top
  • Login or register to post comments
Thu, 01/20/2011 - 16:49
bhawana@membase
Offline
Joined: 10/29/2010
Groups: None

If you don't see the crash message again - it should be fine. This just means that your mnesia directory somehow got corrupt. Do you see the data being written to your cluster. Can you retrieve it fine?

Please let me know if you have more questions.

Bhawana

__________________

Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!

Top
  • Login or register to post comments
Thu, 01/20/2011 - 18:19
vertigo
Offline
Joined: 01/17/2011
Groups: None

Well, the actual issue is that now we start membase and about 20 seconds later it the server shuts down.

It's possibly unrelated to the previous problem but I have included a full log from when the server starts to when it shuts down.

I have uploaded the log here: http://pastebin.com/yEGcn8Ks

 

EDIT: Found the cause of this: the ip addresses of the nodes changed.

Top
  • Login or register to post comments
Fri, 01/21/2011 - 11:44
bhawana@membase
Offline
Joined: 10/29/2010
Groups: None

Looks like your problem was solved.

We recommend that one uses hostnames instead of IP addresses in installations where the IP addresses could change.

Here is a link to our Best Practices Document that many find quite useful:

http://wiki.membase.org/display/membase/Membase+Best+Practices

Please let me know if you have more questions.

Bhawana

__________________

Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!

Top
  • Login or register to post comments
  • Login or register to post comments
  • Login
  • Register

Company

  • About Us
  • Leadership
  • Customers
  • Partners
  • Contact Us

Product

  • Couchbase Server
  • Couchbase SDKs
  • Use Cases
  • Documentation
  • Forums

Open Source

  • Couchbase Project
  • Couchbase vs. CouchDB

Commercial

  • Subscriptions & Support
  • Training & Services

News

  • Blog
  • Newsletter
  • Press Releases
  • Buzz

Follow Us

    
  • Customer Login
  • Terms of Service
  • Privacy Policy
  • Trademark Policy
  • Site Map

© 2013 COUCHBASE All rights reserved.

Sign in to Couchbase Community

close
  • Create new account
  • Request new password
You are logging into the Forums, Wiki and Issue Tracker