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.
On Tue, Apr 17, 2012 at 8:50 AM, Robert Newson <[email protected]> wrote:
> The test suite frequently calls _restart for test isolation.
>
> B.
>
> On 17 April 2012 11:40, Mike Kimber <[email protected]> wrote:
>> Hopefully a quick question:
>>
>> I have a Centos 5.8 VM and to be honest it does not seem to be in great
>> shape as its performs very slowly. Obviously not a couchdb issue. However I
>> am observing my couchdb (tried 1.1.1 and 1.2) install restarting itself:
>>
>> [Tue, 17 Apr 2012 08:21:43 GMT] [info] [<0.2527.0>] 172.25.1.168 - - GET
>> /test_suite_foobar/ 200
>> [Tue, 17 Apr 2012 08:21:43 GMT] [info] [<0.2527.0>] 172.25.1.168 - - POST
>> /_restart 200
>> [Tue, 17 Apr 2012 08:21:50 GMT] [info] [<0.2688.0>] Apache CouchDB has
>> started on http://64.57.221.185:5984/
>> [Tue, 17 Apr 2012 08:21:50 GMT] [info] [<0.2781.0>] 172.25.1.168 - - GET /
>> 200
>>
>> So question if something takes two long to complete ion couchdb will it
>> restart itself?
>>
>> This happen's when I run the test suite and also Replication.
>>
>> Mike
