[bind10-dev] shutdown of boss and msgq dieing

Jelte Jansen jelte at isc.org
Wed Feb 24 09:28:50 UTC 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/23/2010 10:19 PM, Jeremy C. Reed wrote:
> I had bind10 running.
> 
> I ran the test script: src/bin/stats/test/shutdown.py
> 
> My bind10 process logged:
> 
> [XX] Boss got command:
> shutdown
> 
> Later I tried it again:
> 
> Server started.
> [XX] Boss got command:
> shutdown
> [XX] check for command
> Process msgq (PID 20950) died.
> The msgq process died, shutting down.
> Stopping the server.
> Sending SIGTERM to b10-cmdctl (PID 12707).
> Sending SIGTERM to b10-auth (PID 11356).
> Sending SIGTERM to b10-cfgmgr (PID 14943).
> Process b10-cmdctl (PID 12707) died.
> All processes ended, server done.
> 
> I can't reproduce. shutdown doesn't work for me again. How to do a 
> shutdown? (Please see test script above.)
> 
> Now looking at this again I see above doesn't show the shutdown causing 
> the shutdown, but actually msgq died. I have had msgq die a few times 
> today. I don't know what is causing it.

can it be that the previous msgq didn't shut down and is now blocking
the new one? (and all communications)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuE8VIACgkQ4nZCKsdOncUyMACeKurfOxqb2f0y1XsrEnqiNPIv
e2EAoK1zdh6+azBke8TNt9sHqI1A663a
=1zsj
-----END PGP SIGNATURE-----



More information about the bind10-dev mailing list