Hi, I am a colleague of Peter's and he asked me to look into this matter while he's away on vacation (happy sailing Pete). So I poked around the affected system a bit and decided to change some permission, particularly of the directory /var/opt/SUNWkio from root-root to root-utkiosk, and for some magical reason the problem went away. Later when changing the permission of said directory back to root-root the problem did not come back. This is quite baffling. In any case after a fresh reinstall of SRSS/SRWC + all the patches (I blew away the /var/opt/SUNW* directories before reinstalling) no more problem were observed. So perhaps it was a botched installation of SRSS/SRWC, or application of patches thereof that caused the problems (there were many manual steps in one of the patches, one of which may have been missed).
In any case I think we got the problem licked. Hai Vu Mitel Networks http://www.mitel.com mailto:[email protected] 613-592-5660 x2853 [email protected] Sent by: [email protected] 08/26/2009 01:40 PM Please respond to SunRay-Users mailing list <[email protected]> To SunRay-Users mailing list <[email protected]> cc Subject Re: [SunRay-Users] Trouble with SRSS 4.1 / SRCW 2.1 latest patches on RHEL 5.3 OOPS, ignore that last one -- stupidly forgot to set executable permissions back on the initsession script ... my bad. Now getting exact same dialogs as before, even with the .dmrc file now having permissions = 644. -- Peter [email protected] Sent by: [email protected] 26/08/2009 12:41 Please respond to SunRay-Users mailing list To: SunRay-Users mailing list <[email protected]> cc: Subject: Re: [SunRay-Users] Trouble with SRSS 4.1 / SRCW 2.1 latest patches on RHEL 5.3 Thanks Joerg, > ... In any case there should be a $HOME/.dmrc file for the kiosk user. It > should be owned by the kiosk user, but permissions should be 600. ... > Can you check that file? Checked it. $HOME/.dmrc exists at time we're seeing the error dialogs, permissions = 600. > If the .dmrc error is indeed the one causing your problem, you can try > to change the line that says 'chmod 600 $_theDMRCFile' in the > /opt/SUNWkio/lib/initsession script to say '644' in place of '600' to > work around the problem. So, I tried that, inside setGDMSessionStarter () function (right?) and am now getting a different error dialogs at session start: "Error starting Kiosk session: invalid Kiosk session configuration. [OK]" then a little later "Authentication failed. [OK]" At that time, also see the following in SRSS logs " utauthd: SessionManager0 NOTICE: EMPTY: ACTIVE session kiosk:utkioskconfig:refresh[22134]: Enabled Kiosk Mode for display ':13' gdm[19493]: pam_kiosk: pam_sm_authenticate: Initiating Kiosk session with user utku4 gdm[19493]: pam_kiosk: pam_sm_setcred: Child process /opt/SUNWkio/lib/initsession failed with exit code 2. " During the new error dialogs. $HOME does not exist for the kiosk user (/var/opt/SUNWkio/home/ is empty). Note, /var/opt/SUNWkio/home/ has permissions 750, so expected that the chmod may be flunking. However, still get same result even with this dir set to permissions 777. Unsure if it is safe to change permissions of the ../home/ dir anyway, seems like could easily have bad side-effects. I'm attempting tracing down what specifically is complaining. Where should I look for output of logError? (Expect that's a dumb question ;^) -- Peter _______________________________________________ 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
