In this case we need to look at the standard console after running the couchdb server manually:
$ sudo /usr/local/etc/init.d/couchdb stop
* Stopping database server couchdb [ OK ]
$ sudo -u couchdb couchdb
Apache CouchDB 1.1.1a1187836 (LogLevel=info) is starting.
=CRASH REPORT==== 29-Nov-2012::16:35:18 ===
crasher:
initial call: application_master:init/4
pid: <0.31.0>
registered_name: []
exception exit: {bad_return,
{{couch_app,start,
[normal,
["/usr/local/etc/couchdb/default.ini",
"/usr/local/etc/couchdb/local.ini"]]},
{'EXIT',
"libicuuc.so.42: cannot open shared object file: No such file or directory"}}}
in function application_master:init/4
ancestors: [<0.30.0>]
messages: [{'EXIT',<0.32.0>,normal}]
links: [<0.30.0>,<0.7.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 987
stack_size: 24
reductions: 176
neighbours:
=INFO REPORT==== 29-Nov-2012::16:35:18 ===
application: couch
exited: {bad_return,{{couch_app,start,
[normal,
["/usr/local/etc/couchdb/default.ini",
"/usr/local/etc/couchdb/local.ini"]]},
{'EXIT',"libicuuc.so.42: cannot open shared object file: No such file or directory"}}}
type: temporary
At that point I bet you can correct a lot of stuff but I save time in this cases with a fresh installation using a POB recipe remotely through the help of remoto-IT. Here is such recipe.
Especially after a release upgrade expect to get package corruption. More on Ubuntu release upgrades soon.
No comments:
Post a Comment