Thanks Bob! tmpwatch is the evil culprit.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bob Doolittle Sent: Monday, January 04, 2010 1:10 PM To: SunRay-Users mailing list Subject: Re: [SunRay-Users] gdm misbehaving Do you have any scripts that clean up files in /tmp periodically/automatically? /var/opt/SUNWut/displays is a symlink to /tmp/SUNWut/config/displays -Bob Quayle, Bill wrote: > Happy New Year! > > I have a condition that is giving me some issues. It seems that someone is > losing track of what sessions are running and attached, and gdm doesn't like > it. > > Here's a snippet from the messages log: > > Jan 4 12:49:25 srprtocc03c utxsun: > Jan 4 12:49:25 srprtocc03c utxsun: Can not determine token ID > Jan 4 12:49:26 srprtocc03c utxconfig: Error: could not open file > '/var/opt/SUNWut/displays/11' for reading. > Jan 4 12:49:26 srprtocc03c utxsun: Error: could not open file > '/var/opt/SUNWut/displays/11' for reading. > Jan 4 12:49:26 srprtocc03c utxsun: > Jan 4 12:49:26 srprtocc03c utxsun: Can not determine token ID > Jan 4 12:49:26 srprtocc03c gdm[6112]: deal_with_x_crashes: Running the > XKeepsCrashing script > Jan 4 12:49:26 srprtocc03c gdm-XKeepsCrashing: GDM can't start X server. > Jan 4 12:49:26 srprtocc03c utxconfig: Error: could not open file > '/var/opt/SUNWut/displays/14' for reading. > Jan 4 12:49:26 srprtocc03c utxsun: Error: could not open file > '/var/opt/SUNWut/displays/14' for reading. > Jan 4 12:49:26 srprtocc03c utxsun: > Jan 4 12:49:26 srprtocc03c utxsun: Can not determine token ID > Jan 4 12:49:26 srprtocc03c gdm[6112]: deal_with_x_crashes: Running the > XKeepsCrashing script > Jan 4 12:49:26 srprtocc03c gdm-XKeepsCrashing: GDM can't start X server. > Jan 4 12:49:26 srprtocc03c utxconfig: Error: could not open file > '/var/opt/SUNWut/displays/16' for reading. > Jan 4 12:49:26 srprtocc03c utxsun: Error: could not open file > '/var/opt/SUNWut/displays/16' for reading. > Jan 4 12:49:26 srprtocc03c utxsun: > Jan 4 12:49:26 srprtocc03c utxsun: Can not determine token ID > Jan 4 12:49:27 srprtocc03c utxconfig: Error: could not open file > '/var/opt/SUNWut/displays/11' for reading. > Jan 4 12:49:27 srprtocc03c utxsun: Error: could not open file > '/var/opt/SUNWut/displays/11' for reading. > Jan 4 12:49:27 srprtocc03c utxsun: > Jan 4 12:49:27 srprtocc03c utxsun: Can not determine token ID > Jan 4 12:49:27 srprtocc03c utxconfig: Error: could not open file > '/var/opt/SUNWut/displays/19' for reading. > Jan 4 12:49:27 srprtocc03c utxsun: Error: could not open file > '/var/opt/SUNWut/displays/19' for reading. > > utsession -p indeed shows no session for these display numbers. > > A restart of the server cleans it up, but it will come back in a few days. > (restarting these servers is not usually an option. They are production > servers and the sessions on these servers are typically active for > 1 month, > with no disconnection.) > > OS is RHEL 5.2 > SRSS is 4.1 > > "netstat -na" shows plenty of sockets available for new sessions, and the > displays above not taken. > > "ps -ef|grep gdm" shows the displays above not active. > > I'm not sure what is causing this condition, but would really like to find > out what it could be and how to fix it without impacting the rest of the > running sessions. > > Thanks! > > -Bill > > _______________________________________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/mailman/listinfo/sunray-users > _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
