Re: [Ltsp-discuss] Server crashing - help!!

[Jason A. P. <pat...@pc...>]

Charles Marcus wrote:

>Everything seems to be running fine, except for these seemingly innocuous
>messages which happen every 5 minutes on the dot, all day every day (anybody
>know what these mean or how I can get rid of them?)
>
>Nov 29 18:14:42 sfla kdm[15117]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:42 sfla kdm[15119]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:43 sfla kdm[15121]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:43 sfla kdm[15123]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:43 sfla kdm[15125]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:44 sfla kdm[15127]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:44 sfla kdm[15129]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:44 sfla kdm[15131]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:45 sfla kdm[15133]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>Nov 29 18:14:45 sfla kdm[15135]: Can't lock pid file /var/run/xdm-pid,
>another kdm is running (pid 1556)
>
exactly as it is saying.  It respawns xdm/kdm too quickly because there 
is already another instance running, and if 10 or more spawn within 
something like a two minute period or 30 seconds something like that, 
then init will pause attempting to start that process for 5 minutes. 
 Then try again, thinking that the application is possibly 
misconfigured.  This gives the system administrator a chance to change 
what's (potentially) wrong so that the application/daemon will work 
without the system being so loaded that it becomes unresponsive, etc. etc.

>Then, here's what happens when the server dies:
>
>Nov 29 18:17:06 sfla kernel: fh_verify: ltsroot/dev permission failure,
>acc=3, error=30
>Nov 29 18:17:06 sfla kernel: fh_verify: ltsroot/dev permission failure,
>acc=3, error=30
>
harmless.  seems that you have an unpatched version of X that is still 
attempting to change the ownership of the tty on which it is running. 
 This will go away in the newest version of LTSP and/or if you were to 
run X 4.

>Nov 29 18:18:56 sfla kernel: Unable to handle kernel paging request at
>virtual address 0001000c
>Nov 29 18:18:56 sfla kernel:  printing eip:
>Nov 29 18:18:56 sfla kernel: c0113a82
>Nov 29 18:18:56 sfla kernel: pgd entry dbb4a000: 0000000000000000
>Nov 29 18:18:56 sfla kernel: pmd entry dbb4a000: 0000000000000000
>Nov 29 18:18:56 sfla kernel: ... pmd not present!
>Nov 29 18:18:56 sfla kernel: Oops: 0002
>Nov 29 18:18:56 sfla kernel: CPU:    0
>Nov 29 18:18:56 sfla kernel: EIP:    0010:[schedule+194/944]
>Nov 29 18:18:56 sfla kernel: EIP:    0010:[<c0113a82>]
>Nov 29 18:18:56 sfla kernel: EFLAGS: 00010096
>Nov 29 18:18:56 sfla kernel: eax: 00000008   ebx: dbbe0000   ecx: dbbe0000
>edx: 00000009
>Nov 29 18:18:56 sfla kernel: esi: 00000000   edi: 0000000d   ebp: dbbe1fbc
>esp: dbbe1f9c
>Nov 29 18:18:56 sfla kernel: ds: 0018   es: 0018   ss: 0018
>Nov 29 18:18:56 sfla kernel: Process sort (pid: 15424, stackpage=dbbe1000)
>Nov 29 18:18:56 sfla kernel: Stack: 40017000 dbbe0000 00000006 dbbe0000
>c02ad600 dbbe0000 40016734 bffffd8c
>Nov 29 18:18:56 sfla kernel:        bfffda48 c01090f5 4015d700 00000000
>400e4654 40016734 bffffd8c bfffda48
>Nov 29 18:18:56 sfla kernel:        0000e325 0000002b 0000002b ffffffff
>0804f0e2 00000023 00010286 bfffda2c
>Nov 29 18:18:56 sfla kernel: Call Trace: [reschedule+5/12]
>Nov 29 18:18:56 sfla kernel: Call Trace: [<c01090f5>]
>Nov 29 18:18:56 sfla kernel:
>Nov 29 18:18:56 sfla kernel: Code: 89 50 04 89 02 c7 43 3c 00 00 00 00 8b 55
>e4 c7 42 14 00 00
>
Wow!  Kernel oops.  Don't really know how to help you there.  Did you 
compile your own kernel for the server?  If so, you might want to 
upgrade to one of the later versions (2.4.14 or 2.4.16 might do OK).  If 
not, RedHat has 2.4.9 kernel RPM's available.

-- 
Jason A. Pattie
lt...@pc...