On Tue, Jun 10, 2014 at 12:15:05PM +0530, Juned Khan wrote: > Due to some reason i have stooped Bucardo, but it didn't stop. and now > whenever i am trying to start it again its not starting up.
How did you stop it, and how do you know it didn't stop? > root@db01:/home/inex# bucardo status The output you included from bucardo status shows that the last time Bucardo tried to sync, it did so successfully. That doesn't mean Bucardo is running. > root@db01:/home/inex# bucardo start > Checking for existing processes > Cannot start, process 27630 is already running > (file=/var/run/bucardo/bucardo.mcp.pid) This tells you why it didn't start. Bucardo keeps the process ID of its master process in a file, and if that file exists when it is asked to start, it will refuse, thinking Bucardo might be running already. Commit 65b740874be13166c7257ce0353cb525e18b64b8 changes that behavior, so if you upgrade to the very latest code, it should as you expect even when the file exists, provided the PID inside the file doesn't refer to an existing process. -- Josh Tolley [email protected] 801-987-0252 End Point Corporation http://www.endpoint.com
signature.asc
Description: Digital signature
_______________________________________________ Bucardo-general mailing list [email protected] https://mail.endcrypt.com/mailman/listinfo/bucardo-general
