https://bugzilla.redhat.com/show_bug.cgi?id=1394791
Nigel Babu <nig...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |CURRENTRELEASE
Flags|needinfo?(nig...@redhat.com |
|) |
Last Closed| |2016-11-15 07:17:31
--- Comment #4 from Nigel Babu <nig...@redhat.com> ---
I mean, literally that.
Write the PID of your current script into a file at the start and clean up at
the end. Before you write the PID file, check if a stale one exists, if it
does, check if the process is still running, if it does, don't run a second
time.
I don't know why the scripts were not finishing. The only useful thing to do is
make sure it doesn't happen again.
The machine is restarted and you should be able to run the crons now.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/token.cgi?t=NlPqzUMjzE&a=cc_unsubscribe
_______________________________________________
Gluster-infra mailing list
Gluster-infra@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-infra
