Couchbase
  • Why NoSQL?
  • Couchbase Server
  • Download
  • Resources
  • Careers
Home | Forums | Membase | Memcached Server 1.0.3

Difinitive answer on single IP setup?

2 replies [Last post]
  • Login or register to post comments
Mon, 05/24/2010 - 01:17
terry_brown
Offline
Joined: 04/20/2010
Groups: None

hey folks,

I have a dual IP'd machine here (our dev machines have a couple to mimic hosting) - membase by default always seems to choose the wrong one (would be nice to be able to specify the IP during setup btw).

I've followed the instructions in the administrative guide on page 32/33 about unregistering the server, registering it with the IP, then starting it.

It seems to be up and running (the web console runs) though it's still showing my old IP (10.0.0.120) - there's no way (as suggested in point 8 of the instructions on page 33) of removing that node and my new IP (192.168.10.120) isn't showing.

I've tried running shell.bat, and the last few commands are as follows:

=PROGRESS REPORT==== 24-May-2010::09:10:41 ===
supervisor: {local,net_sup}
started: [{pid,<0.52.0>},
{name,auth},
{mfa,{auth,start_link,[]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]
",{{1> badmatch,{er
=INFO REPORT==== 24-May-2010::09:10:41 ===
Protocol: "inet_tcp": register error: {{badmatch,{error,duplicate_name}},
[{inet_tcp_dist,listen,1},
{net_kernel,start_protos,4},
{net_kernel,start_protos,3},
{net_kernel,init_node,2},
{net_kernel,init,1},
{gen_server,init_it,6},
{proc_lib,init_p_do_apply,3}]}
ror1> ,{shutdown,{dist_manager_ap
=SUPERVISOR REPORT==== 24-May-2010::09:10:41 ===
Supervisor: {local,net_sup}
Context: start_error
Reason: {'EXIT',nodistribution}
Offender: [{pid,undefined},
{name,net_kernel},
{mfa,{net_kernel,start_link,
[['ns_1@10.0.0.120',longnames]]}},
{restart_type,permanent},
{shutdown,2000},
{child_type,worker}]

p,start,[normal,[]]}}}},[{ns_bootstrap,start,0},{init,start_it,1},{init,start_em,1}]}}

Crash dump was written to: erl_crash.dump
init terminating in do_boot ()

_________________________________________________________
and the only entry I can see that could relate to that in the logs is:

INFO REPORT <6099.42.0> 2010-05-24 09:15:13
===============================================================================
alarm_handler {set,{system_memory_high_watermark,[]}}

does that mean anything to anyone?

Anything else I can try?

Thanks for all help.

Cheers,
terry

Top
Mon, 05/24/2010 - 01:48
terry_brown
Offline
Joined: 04/20/2010
Groups: None

ignore me :)

I 'joined' the main cluster in the web interface, which seemed to add the good 'node' and then by expanding the down node I was able to remove it.

The documentation on this may well be perfect for a sysadmin, though as a humble developer, I struggled for sure!

Cheers,
Terry

Top
Tue, 05/25/2010 - 22:48
ingenthr
Offline
Joined: 03/16/2010
Groups:

Hi Terry,

Glad you got things worked out. We're looking to simplify the way we manage this process in the multiple interface case. For now, there are a few manual steps. Thanks for the feedback.

Regards,

- Matt

Top
  • 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