Paul Davis wrote:
To be honest, I have absolutely no idea. And I'm running out of ideas
on how best to start figuring out what's going on here.
The only thing I can think of is to start tearing into the init
scripts and boot sequence bit by bit until you find something
surprising. And by that I mean:
Find the exact erl command used to start couchdb by echoing from the script.
Run that directly, see if it gives any usable info.
If not, start tearing into the startup procedure with Erlang print
statements to see where it gets to.
That's obviously not a lot of awesome, but I really can't think of
anything better right now.
I don't think that I am able to do that ...
Oh, though, you might throw an strace in to see if the VM is halting
on something tragic. Something like:
$ sudo su - couchdb
$ strace -f couchdb
You'll want to put that output on friendpaste or somewhere though
rather than directly in the email cause it should be fairly large.
Paul
Thats what I can do ;-). Her is the URL:
http://www.friendpaste.com/qA0EhBi5VnNY6mbyxmSwh
By the way ... the output stopped here (withe some lines before):
[pid 16930]
open("/usr/local/lib/erlang/lib/stdlib-1.16.3/ebin/erl_posix_msg.beam",
O_RDONLY|O_LARGEFILE) = 8
[pid 16930] read(8,
"FOR1\0\0$0BEAMAtom\0\0\4\303\0\0\0\217\rerl_posi"..., 9272) = 9272
[pid 16930] close(8) = 0
[pid 16930] epoll_wait(3, {}, 256, 0) = 0
[pid 16930] clock_gettime(CLOCK_MONOTONIC, {21987, 677071837}) = 0
[pid 16930] getcwd("/usr/local/var/lib/couchdb"..., 8191) = 27
[pid 16930] clock_gettime(CLOCK_MONOTONIC, {21987, 678609183}) = 0
[pid 16930] epoll_wait(3, <unfinished ...>
[pid 16941] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed
out)
[pid 16941] munmap(0xb77d7000, 1048576) = 0
[pid 16941] futex(0x8221880, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 16941] futex(0x8221904, FUTEX_WAIT_PRIVATE, 9, NULL^C <unfinished ...>
Process 16941 detached
Maybe this is not a normal behaviour. You can see that I stopped after NULL.
I hope it helps ...
Cheers
Andy
