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
I'm looking to run couchdb to play with as a potential backend to web
applications. I just installed the system-wise daemon:
apt-get install couchdb
If I remove couchdb with --purge the log file is removed so it's the
right log file for the service.
After reinstalling couchdb and tailing the
Sorry, forgot the log file attachment:
** Attachment added: couch_sample.log
http://launchpadlibrarian.net/49320672/couch_sample.log
--
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
Thanks for the info. Could you also attach your ini file for couch? It
really seems like one couchdb is starting ok and working, and a second
couchdb is in a respawn loop and shutting down with an error when it
can't bind to the already in use port.
--
fresh install couchdb dumps errors and
Attaching ini files:
default.ini
** Attachment added: default.ini
http://launchpadlibrarian.net/49329319/default.ini
--
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
Attaching local.ini
** Attachment added: local.ini
http://launchpadlibrarian.net/49329361/local.ini
--
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
Confirmed on load on Ubuntu Server 10.04 under KVM after hitting this
URL:
http://192.168.122.5:5984/_utils/index.html
URL never loads, and couch sits and spins with the above error.
** Changed in: couchdb (Ubuntu)
Status: New = Confirmed
--
fresh install couchdb dumps errors and crash
