Here is negative session ID's that say accept but it still fails to start the login manager on the terminal.
Aug 27 16:03:53 desktopserver gdm[3003]: gdm_xdmcp_decode: Received opcode REQUEST from client 192.168.0.39 Aug 27 16:03:53 desktopserver gdm[3003]: gdm_xdmcp_handle_request: Got REQUEST from 192.168.0.39 Aug 27 16:03:53 desktopserver mountd[29651]: authenticated mount request from 192.168.0.7:658 for /opt/ltsp/i386 (/opt/ltsp/i386) Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_handle_request: xdmcp_pending=1, MaxPending=4, xdmcp_sessions=0, MaxSessions=100, ManufacturerID= Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_display_dispose_check (192.168.0.39:0) Aug 27 16:04:03 desktopserver gdm[3003]: gdm_auth_secure_display: Setting up access for 192.168.0.39:0 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_auth_secure_display: Setting up access Aug 27 16:04:03 desktopserver gdm[3003]: gdm_auth_secure_display: Setting up access for 192.168.0.39:0 - 1 entries Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_display_alloc: display=192.168.0.39:0, session id=-1194644016, xdmcp_pending=2 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_send_accept: Sending ACCEPT to 192.168.0.39 with SessionID=-1194644016 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_decode: Received opcode REQUEST from client 192.168.0.39 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_handle_request: Got REQUEST from 192.168.0.39 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_handle_request: xdmcp_pending=2, MaxPending=4, xdmcp_sessions=0, MaxSessions=100, ManufacturerID= Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_display_dispose_check (192.168.0.39:0) Aug 27 16:04:03 desktopserver gdm[3003]: gdm_display_dispose: Disposing 192.168.0.39:0 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_auth_secure_display: Setting up access for 192.168.0.39:0 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_auth_secure_display: Setting up access Aug 27 16:04:03 desktopserver gdm[3003]: gdm_auth_secure_display: Setting up access for 192.168.0.39:0 - 1 entries Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_display_alloc: display=192.168.0.39:0, session id=-1194644015, xdmcp_pending=2 Aug 27 16:04:03 desktopserver gdm[3003]: gdm_xdmcp_send_accept: Sending ACCEPT to 192.168.0.39 with SessionID=-1194644015 On Mon, 2007-08-27 at 15:59 -0600, Roy Souther wrote: > Has anyone else seen this problem? > > A client called me this morning about not having a GDM login manager > anymore, just a grey screen and the X mouse icon. I messed with it for > hours and found nothing wrong other then the gdm logs when I have > debug on is showing negative session ID's, but not allways. > > So to find out if the negative session ID's are acceptable or not I > set my GDM to debug and restarted it, now my network is down and I > cannot login it. > > As you can see in the log below, GDM some times is giving a negative > session ID and some times not. In both cases the terminal cannot get a > login screen. > > Does GDM have a time bomb in it, set to go off today? > > > Aug 27 15:34:19 desktopserver gdm[382]: gdm_xdmcp_decode: Received > opcode MANAGE from client 192.168.0.39 > Aug 27 15:34:19 desktopserver gdm[382]: gdm_xdmcp_handle_manage: Got > MANAGE from 192.168.0.39 > Aug 27 15:34:29 desktopserver gdm[382]: gdm_xdmcp_handle_manage: Got > Display=0, SessionID=-1381689503 Class=MIT-unspecified from > 192.168.0.39 > Aug 27 15:34:29 desktopserver gdm[382]: gdm_xdmcp_handle_manage: > Failed to look up session id -1381689503 > Aug 27 15:34:29 desktopserver gdm[382]: gdm_xdmcp_send_refuse: Sending > REFUSE to -1381689503 > Aug 27 15:45:06 desktopserver gdm[1980]: gdm_xdmcp_decode: Received > opcode REQUEST from client 192.168.0.39 > Aug 27 15:45:06 desktopserver gdm[1980]: gdm_xdmcp_handle_request: Got > REQUEST from 192.168.0.39 > Aug 27 15:45:16 desktopserver gdm[1980]: gdm_xdmcp_handle_request: > xdmcp_pending=1, MaxPending=4, xdmcp_sessions=0, MaxSessions=100, > ManufacturerID= > Aug 27 15:45:16 desktopserver gdm[1980]: > gdm_xdmcp_display_dispose_check (192.168.0.39:0) > Aug 27 15:45:16 desktopserver gdm[1980]: gdm_auth_secure_display: > Setting up access for 192.168.0.39:0 > Aug 27 15:45:16 desktopserver gdm[1980]: gdm_auth_secure_display: > Setting up access > Aug 27 15:45:16 desktopserver gdm[1980]: gdm_auth_secure_display: > Setting up access for 192.168.0.39:0 - 1 entries > Aug 27 15:45:16 desktopserver gdm[1980]: gdm_xdmcp_display_alloc: > display=192.168.0.39:0, session id=1915051245, xdmcp_pending=2 > Aug 27 15:45:16 desktopserver gdm[1980]: gdm_xdmcp_send_accept: > Sending ACCEPT to 192.168.0.39 with SessionID=1915051245 > > > Royce Souther > www.SiliconTao.com > Let Open Source help your business move beyond. > > For security this message is digitally authenticated by GnuPG. > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _____________________________________________________________________ > 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.freenode.net Royce Souther www.SiliconTao.com Let Open Source help your business move beyond. For security this message is digitally authenticated by GnuPG.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_____________________________________________________________________
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.freenode.net
