The NorthScaleServer service terminated with the following error:
The process terminated unexpectedly.
1) windows firewall is turned off
2) there is a second server in the cluster. this server is running on a VM on the problem machine, so this second server is never running when the first server starts up.
also, if I try running northscale console (which is on port 8090, since 8080 is taken) then the service crashes.
Ahh, we've definitely seen issues with a node that is part of a cluster coming up when other nodes in the cluster are completely inaccessible. It's being fixed for the next version...
Can you make sure both servers are up and retry?
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/overviewCall or email "sales -at- membase -dot- com" today!
Thanks, Perry. Because one is a VM running on the first, I can't do that, but I am happy to wait for the next release. Do you know when that may be?
Our 1.6 release is currently scheduled for the end of Sept. I may be able to get you a beta version before then, email me on the side: perry -at - northscale -dot- com and we can coordinate if you're interested.
I had this issue running the latest release. I would start the service, and it would run for a second or two, then it would automatically stop. The error message in the Event Viewer was this:
I managed to get it working by deleting [B]config.dat[/B] in the following location:
I'm not sure why that worked, or what happened to the config.dat.
Actually I didn't delete it the first time, I simply renamed it "config.dat.old". When I started the service again, it created a new config.dat. I have attached the "config.dat.old" file in case you can figure out from it what went wrong.
We can't really see much from the config file, but I'll take a look at the logs if you want to attach them (dump_logs.bat). That error message is the same one we've seen a few time and while we're still tracking it down, it seems to be related to:
-Firewall issues (either Windows firewall or ICS client)
-IP address of the server changing from what was originally configured
Do you know if either of these apply to your situation?
Ah, yeah I'm guessing it's the IP address changing then. Was trying this on my development laptop - doesn't use a static IP.
Yes, that's a known issue for us and something we will be addressing in a later release.
© 2013 COUCHBASE All rights reserved.