CAM Mode Gotcha
By ThinGuy on Sep 24, 2007
There are few gotcha's here and there in Controlled Access Mode (note this is CAM under Sun Ray 3.x and 2.x, not the new Kiosk under SRSS 4 U2). None more elusive than this one that seems to rear it's ugly head about once a year. After I have them check "here and there" and everything is OK, it usually means that /var/adm/sulog is full. The only problems is that I always seem to forget about sulog. :(
Under CAM 2.x and 3.x, one of the CAM scripts has root su to one of the CAM users which then runs your CAM script. If this log is full (50 MB limit), then the CAM Startup will bail and you'll be left with cycling Sun Rays. And since that server won't have any sessions on it, it will always get the new sessions in a FOG since it is the least loaded. Big headache.
If you enable debugging (the "there" link above) you'll see something like this happen right before the session gets torn down:
/opt/SUNWbb/bin/bbrootsession: 8057 File Size Limit Exceeded
If you look at /opt/SUNWbb/bin/bbrootsession, you'll see that's where it's trying to do the su and that little message means that sulog is full.
Simple fix is to assume root, rm /var/adm/sulog;touch /var/adm/sulog and things will once again be happy.
And no, I don't know the history behind sulog having that limit. But one way or another, that's a lot of su'ing to fill that log so either your Sun Ray Servers have been up for a real long time, or your script does have a problem in it that causing it to cycle.
Finally, with Sun Ray Software 09/07 Kiosk has been totally re-written to use PAM. The su doesn't happen anymore.