Charles,
It seems that you have a couple of problems.
1) Looks like KDM is running (or attempting) to run more than once on
the server.
2) The workstation is attempting to write to the workstation's /dev
directory. Are you using
an X server on the workstation that isn't part of an LTSP package ?
3) The server ends up crashing. Maybe due to problem #2 above.
It doesn't seem like #1 and #2 are related. I'd try to solve #2 first.
Jim.
Charles Marcus wrote:
>This probably isn't an LTS problem, but on the outside chance it is, or that
>someone knows what may be going on...
>
>I am having a problem with an LTS server crashing down in Miami (I'm in
>Atlanta). I'm in the process of building a new system with LTS 2.09
>(waiting for the release, actually), StarOffice 6, the latest kernels, KDE
>and everything else, and would really rather not fly down there right now,
>and then again when I get their new hardrive ready. Anyway...
>
>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)
>
>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
>Nov 29 18:17:06 sfla su(pam_unix)[15378]: session closed for user nobody
>Nov 29 18:18:54 sfla kdm[1556]: Unknown session exit code 253 from process
>13341
>Nov 29 18:18:54 sfla su(pam_unix)[15397]: session opened for user nobody by
>(uid=0)
>Nov 29 18:18:54 sfla kernel: fh_verify: ltsroot/dev permission failure,
>acc=3, error=30
>Nov 29 18:18:54 sfla kernel: fh_verify: ltsroot/dev permission failure,
>acc=3, error=30
>Nov 29 18:18:54 sfla su(pam_unix)[15397]: session closed for user nobody
>Nov 29 18:18:56 sfla kdm[1556]: Unknown session exit code 253 from process
>15408
>Nov 29 18:18:56 sfla su(pam_unix)[15416]: session opened for user nobody by
>(uid=0)
>Nov 29 18:18:56 sfla kernel: fh_verify: ltsroot/dev permission failure,
>acc=3, error=30
>Nov 29 18:18:56 sfla kernel: fh_verify: ltsroot/dev permission failure,
>acc=3, error=30
>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
>Nov 29 18:18:56 sfla su(pam_unix)[15416]: session closed for user nobody
>
>I'd appreciate any help or pointers anyone can give. I am not a programmer,
>so please keep that in mind...
>
>Thanks!!
>
>-----------------
>Charles Marcus
>I.T. Director
>Media Brokers International
>770-516-9234 x224
>770-516-8918 fax
>
>
>
>_____________________________________________________________________
>Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
>For additional LTSP help, try #ltsp channel on irc.openprojects.net
>
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
