The error: {error_info,{exit,eaddrinuse,
makes me think there is another couchdb instance already running. Can
you tell me more of the story of how you went about setting this up (I
just want to be able to think through what could have happened so that
things ended up like this)?
I'll also explain some more about CouchDB in Ubuntu just in case it
helps with understanding how things fit together, and then maybe some
other clues will show up about where the bug is.
In Ubuntu, we use couchdb as part of the standard desktop installation,
but don't run a system-wide CouchDB instance on the default port. This
is done with the desktopcouch package and python module. If you are
looking to write a user application with CouchDB, I recommend looking at
quickly, desktopcouch, and slipcover to get some ideas for what is
possible - none of this is advertised very well right now but we will be
adding a lot of info on it to the new developer manual in 10.10.
If you are looking to write a server application that communicates with
a standard CouchDB on the system port, installing the couchdb package
should take care of bringing the server up for you, and futon should
work ok. The couchdb package actually only contains the init script, all
the binaries are in the couchdb-bin package.
CouchDB depends on having a javascript engine available, and it uses
libmozjs.so (this is the mozilla spidermonkey js engine). In Ubuntu,
this library is only available as part of the xulrunner package, and
I've seen some interesting crash situations before where couchdb
appeared to load ok, but as soon as you tried to use something like
futon it would crash when trying to load a missing libmozjs.so. From the
error report you pasted it looks like a port conflict rather than a
missing .so, but I'm mentioning it just in case you are working on a
server app and start wondering why xulrunner is pulled in when
installing couchdb.
--
fresh install couchdb dumps errors and crash report into log file
https://bugs.launchpad.net/bugs/587108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
