this is a symptom of a bug in the code, if you can find the point
in the log file where is began, then |
there might be a clue in the log how the master got into that state.
Also, once the master gets in this state there is no way to fix things. You'll just have to restart
all of the daemons, including the master.
On 7/16/2014 7:41 AM, kschwarz@xxxxxxxxxxxxxx wrote:
DaemonCore: async_pipe is signalled, but async_pipe_signal is false