On Tue, Apr 8, 2014 at 12:35 AM, Michael Salmon <[email protected]> wrote:
> Hi folks, > > I had deployed a 2.2 community ami server, but wanted to add an elastic IP > and DNS to it on EC2 (after it had been in use). Keeping the data wasn't > important in this case. I reviewed the instructions for this migration > relative to 2.2 and 1.8 versions to better understand the design/behavior > but the documentation includes a step to modify the couchbase-server script > in a way which doesn't match the contents of the script (see below). I made > the closest change possible, changed the IP, but after running 'service > couchbase-server start', the db was not accessible. In the end I had to > erase the rpm, clean out /opt/couchbase and reinstall the rpm. It would be > good to understand how to properly do this in the future. > > Here is the delta on the couchbase-server script & documentation: > - there was no mnesia directory on my box as noted in the docs (note I had > only been running a single node cluster) > - the start function had no "-run ns_bootstrap" parameter, just "-run > ns_babysitter_bootstrap". I added the -name ns_1@ parameter anyway, and I > also even tried adding -ns_bootstrap > Hm. Not sure I can see any instructions to change initscripts for that in 2.2. 2.2 does have native support for assigning names to host. But doesn't support renaming node that's set up. So simplest thing for you is to simply uninstall the package, then install the package. Then proceed with wizard/cli as usual and assign hostname. -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
