Bug#290916: gdm problem

Thu, 10 Mar 2005 09:00:41 -0800

This is a multi-part message in MIME format.
--------------020408070104030800080804
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

This is just to followup on a bug that had been reported earlier, this 
is the type of thing we get populating our syslog when gdm goes south on 
us, it happens about 2 times a day to us and brings down our entire 
library so it is an issue we need to find a fix for.  At first we had to 
reboot, then tried just restarting gdm, finally if we can find the slave 
pid as we did below, killing that pid seems to work.  We have also been 
able to replicate it on our 'training server'.  Not consistently and not 
on purpose, but it happened when we were testing mounting and unmounting 
a floppy.  I will try to get a more comprehensive log for you, but this 
is really the gist of it.

Mar  9 16:02:59 svserv gdm[5987]: gdm_display_unmanage: Stopping 
sv246.svnet:0 (slave pid: 16008)
Mar  9 16:03:09 svserv gdm[5987]: whack_old_slave: GOT ANOTHER SIGTERM 
(or it was 10 secs already), killing slave again

killing pid 16008 fixed sv without restarting gdm.

-- 
Sonja L. Baldwin
IT tech/Staff Instructor
Yakima Valley Regional Library
509-452-8541 ext 733

--------------020408070104030800080804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
 <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#333333">
This is just to followup on a bug that had been reported earlier, this
is the type of thing we get populating our syslog when gdm goes south
on us, it happens about 2 times a day to us and brings down our entire
library so it is an issue we need to find a fix for.&nbsp; At first we had
to reboot, then tried just restarting gdm, finally if we can find the
slave pid as we did below, killing that pid seems to work.&nbsp; We have
also been able to replicate it on our 'training server'.&nbsp; Not
consistently and not on purpose, but it happened when we were testing
mounting and unmounting a floppy.&nbsp; I will try to get a more
comprehensive log for you, but this is really the gist of it. 
 
Mar&nbsp; 9 16:02:59 svserv gdm[5987]: gdm_display_unmanage: Stopping
sv246.svnet:0 (slave pid: 16008)
 
Mar&nbsp; 9 16:03:09 svserv gdm[5987]: whack_old_slave: GOT ANOTHER SIGTERM
(or it was 10 secs already), killing slave again
 
 
 
killing pid 16008 fixed sv without restarting gdm.
<pre class="moz-signature" cols="72">-- 
Sonja L. Baldwin
IT tech/Staff Instructor
Yakima Valley Regional Library
509-452-8541 ext 733</pre>
</body>
</html>

--------------020408070104030800080804--