I have cron restart both GDM and SRSS nightly.... I did have an unfixable 26D (before trying the "fix" I mentioned earlier), and doing a pkill gdm took care of it, but as mentioned doing so would bring down sessions in the entire lab and several faculty workstations, not a good thing. I tried randomly running pkill -9 gdm-binary while I had several test session open, and this mad ea huge mess. the logged in sessions were fine and the current login screen were fine, however attempting to log in via SunRay would hang at 26B this time, and the only fix to get past that for that one SunRay would be to run pkill -9 gdm-binary again, but this would have to happen every time someone logs into a SunRay device for the fisrt time since the command was run..... Not sure why 26B this time instead of 26D.... The only fix that worked to get things back to normal (Sunray and GDM restart brought all SunRays to 26B) was to do a utstop, bring the OS down to init 3, bring OS back to init 5, then finally do a utstart (this series of steps has taken care of almost any Sunray issue I have ever had, but obviously brings down all sessions).
On Thu, Jun 20, 2013 at 10:50 AM, Karl Rossing <[email protected]>wrote: > On 2013-06-20 2:46 AM, Philippe BOURDEU d'AGUERRE wrote: > >> A softer way is to do: >> >> pkill -9 gdm-binary >> >> It doesn't interrupt current sessions. >> > Over time, the 26d's become unfixable. I have found that rebooting the > server is the only way to fix it. > > I now reboot out SR servers every night via cron in order to ensure that > we don't get to an unfixable 26d state. > > I'll try "pkill -9 gdm-binary" and hopefully I no longer need to reboot > the servers. > > Karl > > > > > > > CONFIDENTIALITY NOTICE: This communication (including all attachments) is > confidential and is intended for the use of the named addressee(s) only and > may contain information that is private, confidential, privileged, and > exempt from disclosure under law. All rights to privilege are expressly > claimed and reserved and are not waived. Any use, dissemination, > distribution, copying or disclosure of this message and any attachments, in > whole or in part, by anyone other than the intended recipient(s) is > strictly > prohibited. If you have received this communication in error, please > notify > the sender immediately, delete this communication from all data storage > devices and destroy all hard copies. > ______________________________**_________________ > SunRay-Users mailing list > [email protected] > http://www.filibeto.org/**mailman/listinfo/sunray-users<http://www.filibeto.org/mailman/listinfo/sunray-users> > -- Greg Rodenhiser Technical Services Engineer College of the Holy Cross
_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
