couchbase-server is not running

Can you do an "/etc/init.d/couchbase-server stop" and then do a "ps -U couchbase" to see if any processes are running? I suspect an epmd may continue running, which may need to be killed.

Then try a start from there.

Just to check, you did rm or move everything that was in /opt/couchbase after uninstall of the old version, right? The data files are not (necessarily) compatible between builds and may change until release.

well, for me i have removed all couchbase related data, rebooted my amazon ec2 instance.
reinstalled it now and it's seems :couchbase-server is running.
i can login into webconsole as well.

Getting a similar issue, i was testing the 1.8 version in 2 different server(both centos with same specs), and then i decide to try the 2.0 beta, after i uninstall the 1.8 version and remove the /opt/couchbase/ folder, i was able to install the .rpm file for redhat(Both same issue).
After installing the rpm i get this
[root@XXX couch]# rpm -i couchbase-server-community_x86_64_2.0.0-beta.rpm
Starting couchbase-server[ OK ]

You have successfully installed Couchbase Server.
Please browse to http://XXXXX:8091/ to configure your server.
Please refer to http://couchbase.com for additional resources.

Please note that you have to update your firewall configuration to
allow connections to the following ports: 11211, 11210, 11209, 4369,
8091 and from 21100 to 21299.

By using this software you agree to the End User License Agreement.
See /opt/couchbase/LICENSE.txt.

[root@XXX couch]#

But the service doesnt start correctly the only thing running is this one
103 6819 1 0 18:42 ? 00:00:00 /opt/couchbase/lib/erlang/erts-5.8.5/bin/epmd -daemon
even if I stop the service using "/etc/init.d/couchbase-server stop" that process keep running in background(i killed manually a bunch of time reintalling the hole couchbase).

This happen in 2 servers with a previous install of couchbase, on 3rd server(same specs as the previous 2 servers) i didnt install the 1.8 version and i was able to install the 2.0 without a problem.

I think that something is missing inside of my OS that is not in /opt/couchbase something that is not replaced by the new rpm.

Someone have an idea about this?

Thanks

Hi -

Not sure if you ever resolved this error but I encountered it as well when upgrading Couchbase 1.8 to 2.0. The fix for my system was to (1) uninstall Couchbase 1.8 using the package manager and (2) clear the old couchbase DB using rm -rf /opt/couchbase (3) install couchbase 2.0.

At some point I also had to modify /etc/security/limits.conf but I think that's no longer needed if you follow the above steps:
couchbase soft nofile 1000000
couchbase hard nofile 1000000

HTH
-aed

I ran into the same issue with 1.8 to 2.0 GA. I just posted about it. Sorry I didn't find this earlier.

I also had to delete /opt/couchbase

Hi all,
Nope i didnt resolve this issue on those 2 servers.
I Still have the same issue, one thing that i noted if I uninstall couchbase 2.0(not working error described in my first post) and i install 1.8 again. couchbase works and run smothly. I am without ideas.

Adding more infor from the error log

"
....Everything God so far
[user:info,2013-01-10T9:43:43.140,ns_1@127.0.0.1:ns_server_sup<0.341.0>:menelaus_sup:start_link:44]Couchbase Server has started on web port 8091 on node 'ns_1@127
.0.0.1'.
[error_logger:info,2013-01-10T9:43:43.140,ns_1@127.0.0.1:error_logger<0.5.0>:ale_error_logger_handler:log_report:72]
=========================PROGRESS REPORT=========================
supervisor: {local,ns_server_sup}
started: [{pid,<0.401.0>},
{name,menelaus},
{mfargs,{menelaus_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,infinity},
{child_type,supervisor}]

[error_logger:info,2013-01-10T9:43:43.141,ns_1@127.0.0.1:error_logger<0.5.0>:ale_error_logger_handler:log_report:72]
=========================PROGRESS REPORT=========================
supervisor: {local,mc_sup}
started: [{pid,<0.423.0>},
{name,mc_couch_events},
{mfargs,
{gen_event,start_link,[{local,mc_couch_events}]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,worker}]

[error_logger:info,2013-01-10T9:43:43.141,ns_1@127.0.0.1:error_logger<0.5.0>:ale_error_logger_handler:log_report:72]
=========================PROGRESS REPORT=========================
supervisor: {local,mc_sup}
started: [{pid,<0.424.0>},
{name,mc_conn_sup},
{mfargs,{mc_conn_sup,start_link,[]}},
{restart_type,permanent},
{shutdown,brutal_kill},
{child_type,supervisor}]

and its gone.....

[ns_server:debug,2013-01-10T9:43:43.144,ns_1@127.0.0.1:<0.400.0>:ns_pubsub:do_subscribe_link:132]Parent process of subscription {master_activity_events,<0.399.0>}
exited with reason killed
[ns_server:info,2013-01-10T9:43:43.144,ns_1@127.0.0.1:mb_master<0.376.0>:mb_master:terminate:302]Synchronously shutting down child mb_master_sup
[error_logger:error,2013-01-10T9:43:43.144,ns_1@127.0.0.1:error_logger<0.5.0>:ale_error_logger_handler:log_report:72]
=========================CRASH REPORT=========================
crasher:
initial call: mc_tcp_listener:init/1
pid: <0.425.0>
registered_name: []
exception error: no match of right hand side value {error,eaddrinuse}
in function mc_tcp_listener:init/1
ancestors: [mc_sup,ns_server_sup,ns_server_cluster_sup,<0.58.0>]

I have all the ports unbind on that server dont know why have this error {error,eaddrinuse}