couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <paul.joseph.da...@gmail.com>
Subject Re: Cannot Start Couchdb: "init terminating in do_boot"
Date Sat, 19 Dec 2009 23:05:53 GMT
There's no good way to kill all couchdb processes safely. Generally,
`ps ax | grep couch` should give you the list and then you can just
`kill -KILL $PID` for each pid that comes back.

The most common errors for this sort of thing are that you haven't got
correct permissions set on each of the directories that CouchDB needs
access to. There's a list in the README of what needs to be set.

Paul Davis

On Sat, Dec 19, 2009 at 6:01 PM, viatropos <lancejpollard@gmail.com> wrote:
>
> Hi there,
>
> Every now and then I get this error when trying to start/use couchdb 0.9:
>
> $ couchdb
> Apache CouchDB 0.9.0 (LogLevel=info) is starting.
> {"init terminating in
> do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
>
> Crash dump was written to: erl_crash.dump
> init terminating in do_boot ()
>
> The first part of the /usr/local/var/lib/couchdb/erl_crash.dump is at the
> bottom of this post.
>
> If I run it with sudo, sometimes it works, sometimes I get the above error.
> When I had it working a few days ago, I ran the couchdb command without sudo
> and it was running fine.
>
> If I run "couchdb stop", I get this:
>
> Apache CouchDB 0.9.0 (LogLevel=info) is starting.
> {"init terminating in
> do_boot",{{badmatch,{error,shutdown}},[{couch_server_sup,start_server,1},{erl_eval,do_apply,5},{erl_eval,exprs,5},{init,start_it,1},{init,start_em,1}]}}
> init terminating in do_boot ()
>
> So I've read that this is because I need to use a different port and that
> something is using port 5984, but I would like to use the default one with
> couchdb as I don't have anything else that would be using 5984.  I'm running
> a Rails/CouchRest app.  Is there a way to just quit all couchdb processes
> and start over without reinstalling?
>
> Here's a list of my running processes, I'm on Ubuntu 8.10 running on
> slicehost:
>
> $ ps -A
>  PID TTY          TIME CMD
>    1 ?        00:00:00 init
>    2 ?        00:00:00 kthreadd
>    3 ?        00:00:00 migration/0
>    4 ?        00:00:00 ksoftirqd/0
>    5 ?        00:00:00 watchdog/0
>    6 ?        00:00:02 events/0
>    7 ?        00:00:00 khelper
>   18 ?        00:00:00 xenwatch
>   19 ?        00:00:00 xenbus
>   28 ?        00:00:00 migration/1
>   29 ?        00:00:00 ksoftirqd/1
>   30 ?        00:00:00 watchdog/1
>   31 ?        00:00:02 events/1
>   32 ?        00:00:00 migration/2
>   33 ?        00:00:00 ksoftirqd/2
>   34 ?        00:00:00 watchdog/2
>   35 ?        00:00:02 events/2
>   36 ?        00:00:00 migration/3
>   37 ?        00:00:00 ksoftirqd/3
>   38 ?        00:00:00 watchdog/3
>   39 ?        00:00:03 events/3
>   65 ?        00:00:00 kblockd/0
>   66 ?        00:00:00 kblockd/1
>   67 ?        00:00:00 kblockd/2
>   68 ?        00:00:00 kblockd/3
>   78 ?        00:00:00 kseriod
>  125 ?        00:00:00 pdflush
>  126 ?        00:00:00 pdflush
>  127 ?        00:00:02 kswapd0
>  128 ?        00:00:00 aio/0
>  129 ?        00:00:00 aio/1
>  130 ?        00:00:00 aio/2
>  131 ?        00:00:00 aio/3
>  209 ?        00:00:00 accel_watch/0
>  210 ?        00:00:00 accel_watch/1
>  211 ?        00:00:00 accel_watch/2
>  212 ?        00:00:00 accel_watch/3
>  1103 ?        00:00:00 ksnapd
>  2079 ?        00:00:00 kjournald
>  2294 ?        00:00:01 udevd
>  3509 tty4     00:00:00 getty
>  3510 tty5     00:00:00 getty
>  3512 tty2     00:00:00 getty
>  3513 tty3     00:00:00 getty
>  3515 tty6     00:00:00 getty
>  3546 ?        00:00:01 syslogd
>  3565 ?        00:00:00 dd
>  3568 ?        00:00:00 klogd
>  3586 ?        00:00:00 sshd
>  3634 ?        00:00:00 mysqld_safe
>  3676 ?        00:00:40 mysqld
>  3677 ?        00:00:00 logger
>  3821 ?        00:00:00 nginx
>  3822 ?        00:00:04 nginx
>  3823 ?        00:00:04 nginx
>  3825 ?        00:00:00 nginx
>  3826 ?        00:00:04 nginx
>  3842 ?        00:02:25 ruby
>  3846 ?        00:02:25 ruby
>  3862 ?        00:00:03 monit
>  3896 ?        00:00:00 cron
>  3906 tty1     00:00:00 getty
>  3910 ?        00:00:55 beam.smp
>  5770 ?        00:00:00 sshd
>  5774 ?        00:00:00 sshd
>  5776 pts/1    00:00:00 bash
>  5890 pts/1    00:00:00 ps
>
>
> First page of output from erl_crash.dump:
>
> =erl_crash_dump:0.1
> Sat Dec 19 10:14:27 2009
> Slogan: init terminating in do_boot ()
> System version: Erlang (BEAM) emulator version 5.6.3 [source] [64-bit]
> [smp:4] [async-threads:0] [kernel-po$
> Compiled: Sat Jul 12 09:31:11 2008
> Atoms: 6082
> =memory
> total: 6386480
> processes: 1046494
> processes_used: 1020814
> system: 5339986
> atom: 432593
> atom_used: 400042
> binary: 37338
> code: 3593353
> ets: 230688
> =hash_table:atom_tab
> size: 4813
> used: 3422
> objs: 6082
> depth: 7
> =index_table:atom_tab
> size: 6144
> limit: 1048576
> entries: 6082
> =hash_table:module_code
> size: 97
> used: 61
> objs: 97
> depth: 4
> =index_table:module_code
> size: 1024
> limit: 65536
> entries: 97
> =hash_table:export_list
> size: 2411
> used: 1672
> objs: 2831
> depth: 7
> =index_table:export_list
> size: 3072
> limit: 65536
> entries: 2831
> =hash_table:secondary_export_table
> size: 97
> used: 0
> objs: 0
> depth: 0
> =hash_table:process_reg
> size: 47
> used: 27
> objs: 33
> depth: 2
> =hash_table:fun_table
> size: 397
> used: 266
> objs: 439
> depth: 5
> =hash_table:node_table
> size: 11
> used: 1
> objs: 1
>
>
> Thanks so much for your help.  I can't seem to find any simple way to start
> and stop couchdb and avoid these errors...
>
> Lance
> --
> View this message in context: http://n2.nabble.com/Cannot-Start-Couchdb-init-terminating-in-do-boot-tp4193056p4193056.html
> Sent from the CouchDB Development mailing list archive at Nabble.com.
>

Mime
View raw message