On 19 April 2012 02:34, Gustavo Fonseca <[email protected]> wrote: > Hi, > I had the same situation, but the (re)start happens after a sequence > os error entries: > > [Tue, 17 Apr 2012 17:18:56 GMT] [error] [<0.19.0>] {error_report,<0.9.0>, > [Tue, 17 Apr 2012 17:18:56 GMT] [error] [<0.19.0>] {error_report,<0.9.0>, > [Tue, 17 Apr 2012 17:18:56 GMT] [error] [<0.19.0>] {error_report,<0.9.0>, > [Tue, 17 Apr 2012 17:18:56 GMT] [error] [<0.19.0>] {error_report,<0.9.0>, > [Tue, 17 Apr 2012 17:18:56 GMT] [error] [<0.19.0>] {error_report,<0.9.0>, > [Tue, 17 Apr 2012 17:18:56 GMT] [info] [<0.30.0>] Apache CouchDB has > started on http://192.168.1.83:5984/ > > Could it be just another process being started to handle the > increasing requests, or the CouchDB had actually restarted for some > reason? > > Regards, > Gustavo.
There is only one CouchDB Erlang application. Do you see anything like this prior in the logs? >>> [Tue, 17 Apr 2012 08:21:43 GMT] [info] [<0.2527.0>] 172.25.1.168 - - POST >>> /_restart 200 Is it while running test suite? If not, can you try running it in interactive mode for a while? sudo or login as couchdb user, then couchdb -i to watch the erlang goodness fly past. Pasting the logs somewhere & other related info will help too. A+ Dave
