OpenRig
← All of OpenRig 0.7.14

ChangedOpenRig 0.7.14

If the start is reported pending, don't start the daemon again until you've followed the restart steps the message prints; rig daemon stop can't stop that child.

If the start is reported pending: the CLI waits 20 s, then may print "Daemon startup is pending after the readiness deadline". Readiness remains unconfirmed. It leaves the child running and the startup reservation retained, without recording the daemon. Inspect the address and log it prints. The child may later answer, and status can then report it running, but that does not finish this start's recording or release its reservation. Don't start it again until the steps below are done. The message's restart steps stop that child and clear the reservation: stop the named child PID and wait for it to exit, inspect daemon-start.lock, and only when both recorded launcher and child PIDs are absent, archive the lock and run rig daemon start. On a large database the new start can be reported pending again; reaching a recorded start this way hasn't been tested. rig daemon stop cannot stop that unpublished child.