Re: [SunRay-Users] 26D problems SRSS 5.1
Hi all, we tried to modify gdm-2.16.0-56.el5.src.rpm (Red Hat) settings MAX_CONNECTIONS to 100. It doesn't work. Maybe we have done something wrong, but when our 2 server FOG were online again, the SunRays got no login screens. So we stopped this experiment. When we start the FOG again with the original gdm, we saw, it needed a long for the SunRays to come up and work properly. And of course, we have still the 26D problem. Sometimes i think, there is a communication problem between the two servers. When a 26D appears, i have also the problem to access Sessions in the GUI of one of the servers. When 26D is gone, i have no problems with the GUI to access Sessios. I want to know, if this 26D problem only appears in FOGs or also in standalone systems. Detlev -- Detlev | Institut fuer Mikroelektronische Systeme Habicht | D-30167 Hannover +49 511 76219662 habi...@ims.uni-hannover.de + Handy+49 172 5415752 --- ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
I setup a service request at Red Hat. This is the answer: Red Hta do not have gdm version with MAX_CONNECTIONS set to 100. You may try using third party gdm or recompiling the gdm from source after changes the MAX_CONNECTIONS values in source code. But please note that as per Red hat production suport policy, Red Hat do not provide support for it. Well, we have do it self Detlev P.S.: I have no knowledge to do such things, but i will try it. I am still reading doc. I think, we have to create a patch script for the source rpm. Am 15.02.2011 um 20:44 schrieb Karl Rossing: On 02/08/11 09:24, Meik Hellmund wrote: in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) I'm interested in the steps required to get this to work on Redhat. Thanks 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 SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
I'm testing with fedora 14 for the time being. I tried replacing the gdm with the one provided with the SRS install but that did not work well. I have to look into why a bit more. Karl On 02/16/11 02:10, Detlev Habicht wrote: I setup a service request at Red Hat. This is the answer: Red Hta do not have gdm version with MAX_CONNECTIONS set to 100. You may try using third party gdm or recompiling the gdm from source after changes the MAX_CONNECTIONS values in source code. But please note that as per Red hat production suport policy, Red Hat do not provide support for it. Well, we have do it self Detlev P.S.: I have no knowledge to do such things, but i will try it. I am still reading doc. I think, we have to create a patch script for the source rpm. Am 15.02.2011 um 20:44 schrieb Karl Rossing: On 02/08/11 09:24, Meik Hellmund wrote: in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) I'm interested in the steps required to get this to work on Redhat. Thanks 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 SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users 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 SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On 02/08/11 09:24, Meik Hellmund wrote: in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) I'm interested in the steps required to get this to work on Redhat. Thanks 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 SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On 02/08/11 16:24, Meik Hellmund wrote: On Tue, 8 Feb 2011 15:58:43 +0100 Detlev Habicht habi...@ims.uni-hannover.de wrote: We have to recompile gdmdynamic? Yes, in fact all of gdm Or is there a config file somewhere in the system? there is a comment in daemon/gdm-net.c: this should be configurable ..but it seems nobody did it Detlev P.S.: I am using Red Hat. in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) No idea what the equivalent yum/rpm commands are. - Meik Hi Meik, this finally seems to fix our problem. The patched gdm for ubuntu 10.4 now runs for some days without problems. For those, who are also running ubuntu 10.4 I have updated the wiki accordingly: http://wiki.sun-rays.org/index.php/SRSS_4.2_on_Ubuntu_10.04_(i386,_amd64) man thanks for the help Carsten -- Max Planck Institut fuer marine Mikrobiologie - Network Administration - Celsiustr. 1 D-28359 Bremen Tel.: +49 421 2028568 Fax.: +49 421 2028565 PGP public key:http://www.mpi-bremen.de/Carsten_John.html ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
Hello again, i am a little bit confused. Maybe i have made a mistake. And maybe a second time :-} Normally i install the gdm from Sun. Maybe i have forgotten this the last time. So i find now from Red Hat this: gdm-2.16.0-56.el5 Sun has this: gdm-2.16.7-2.1_01.sunray.x86_64.rpm Maybe some of the people here with 26D problems have also forgotten to install the Sun version of gdm??? I can't test gdm in the moment. So i don't know if this helps. But one questions: I don't find the source for the Sun version. Is here someone who knows a URL to it? Thanx. Detlev Am 08.02.2011 um 16:24 schrieb Meik Hellmund: On Tue, 8 Feb 2011 15:58:43 +0100 Detlev Habicht habi...@ims.uni-hannover.de wrote: We have to recompile gdmdynamic? Yes, in fact all of gdm Or is there a config file somewhere in the system? there is a comment in daemon/gdm-net.c: this should be configurable ..but it seems nobody did it Detlev P.S.: I am using Red Hat. in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) No idea what the equivalent yum/rpm commands are. - Meik -- Meik Hellmund Mathematisches Institut, Uni Leipzig e-mail: meik.hellm...@math.uni-leipzig.de http://www.math.uni-leipzig.de/~hellmund ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
You should not normally install the version of gdm included with the product manually. That version will be installed automatically by the installer *if appropriate*. I believe the only appropriate situation for installing that version is on SLES 10, which had a significantly downrev version of GDM which had bugs affecting Sun Ray performance. In spite of the apparent version number differences Red Hat has (apparently) incorporated the necessary patches in their recent releases, and thus should be preferentially used. Again, utinstall should do the right thing here. What version of Red Hat are you running? If you're experiencing problems this might be worth a try, but my expectation is that it will not help. Thanks, Bob On 02/09/11 06:01, Detlev Habicht wrote: Hello again, i am a little bit confused. Maybe i have made a mistake. And maybe a second time :-} Normally i install the gdm from Sun. Maybe i have forgotten this the last time. So i find now from Red Hat this: gdm-2.16.0-56.el5 Sun has this: gdm-2.16.7-2.1_01.sunray.x86_64.rpm Maybe some of the people here with 26D problems have also forgotten to install the Sun version of gdm??? I can't test gdm in the moment. So i don't know if this helps. But one questions: I don't find the source for the Sun version. Is here someone who knows a URL to it? Thanx. Detlev Am 08.02.2011 um 16:24 schrieb Meik Hellmund: On Tue, 8 Feb 2011 15:58:43 +0100 Detlev Habichthabi...@ims.uni-hannover.de wrote: We have to recompile gdmdynamic? Yes, in fact all of gdm Or is there a config file somewhere in the system? there is a comment in daemon/gdm-net.c: this should be configurable ..but it seems nobody did it Detlev P.S.: I am using Red Hat. in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) No idea what the equivalent yum/rpm commands are. - Meik -- Meik Hellmund Mathematisches Institut, Uni Leipzig e-mail: meik.hellm...@math.uni-leipzig.de http://www.math.uni-leipzig.de/~hellmund ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On Fri, 04 Feb 2011 17:44:20 +0100 Carsten John cj...@mpi-bremen.de wrote: Hi folks, we are still having problems. What I found out in the meantime is that definitely gdm is the problem. It works for about a day (or a few days?). Then suddenly gdm does not provide login service any more, resulting the DTUs to hang in 26D. Obviously gdmdynamic stops communication with gdm. A gdmdynamic -l -v at the command line does not give any results and needs to be interrupted via CTRL+c. I think I see the same problem on a quite new installation. strace shows that gmdynamic gets a SERVER_BUSY answer (see http://projects.gnome.org/gdm/docs/2.20/controlling.html , section 7.3.22) from the gdm master process and waits and tries again and waits I increased MAX_CONNECTIONS in daemon/gdm-net.c from 15 to 100 and this seems to help. I have no idea why the problem appears now and not earlier. Some changes from gdm 2.20.7 to 2.20.11 or some changes in the linux kernel or in the SRSS code? I can't reconstruct it. - Meik -- Meik Hellmund Mathematisches Institut, Uni Leipzig e-mail: meik.hellm...@math.uni-leipzig.de http://www.math.uni-leipzig.de/~hellmund ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
We have to recompile gdmdynamic? Or is there a config file somewhere in the system? Detlev P.S.: I am using Red Hat. Am 08.02.2011 um 15:35 schrieb Meik Hellmund: On Fri, 04 Feb 2011 17:44:20 +0100 Carsten John cj...@mpi-bremen.de wrote: Hi folks, we are still having problems. What I found out in the meantime is that definitely gdm is the problem. It works for about a day (or a few days?). Then suddenly gdm does not provide login service any more, resulting the DTUs to hang in 26D. Obviously gdmdynamic stops communication with gdm. A gdmdynamic -l -v at the command line does not give any results and needs to be interrupted via CTRL+c. I think I see the same problem on a quite new installation. strace shows that gmdynamic gets a SERVER_BUSY answer (see http://projects.gnome.org/gdm/docs/2.20/controlling.html , section 7.3.22) from the gdm master process and waits and tries again and waits I increased MAX_CONNECTIONS in daemon/gdm-net.c from 15 to 100 and this seems to help. I have no idea why the problem appears now and not earlier. Some changes from gdm 2.20.7 to 2.20.11 or some changes in the linux kernel or in the SRSS code? I can't reconstruct it. - Meik -- Meik Hellmund Mathematisches Institut, Uni Leipzig e-mail: meik.hellm...@math.uni-leipzig.de http://www.math.uni-leipzig.de/~hellmund ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On Tue, 8 Feb 2011 15:58:43 +0100 Detlev Habicht habi...@ims.uni-hannover.de wrote: We have to recompile gdmdynamic? Yes, in fact all of gdm Or is there a config file somewhere in the system? there is a comment in daemon/gdm-net.c: this should be configurable ..but it seems nobody did it Detlev P.S.: I am using Red Hat. in Debian you just do: apt-get build-dep gdm(install all libraries etc neccessary for building gdm) apt-get source gdm (get the source) cd gdm-2.20.11 vi daemon/gdm-net.c (change the parameter) dpkg-buildpackage -b -uc (build the package) dpkg -i ../gdm_2.20.11-4_amd64.deb (install) No idea what the equivalent yum/rpm commands are. - Meik -- Meik Hellmund Mathematisches Institut, Uni Leipzig e-mail: meik.hellm...@math.uni-leipzig.de http://www.math.uni-leipzig.de/~hellmund ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
Hello, we have similar problems and maybe the same. I can also see the gdm user for example. Mostly we see this problem when a user tries to login via smartcard or want to go to another terminal (with the smartcard). Sometimes this problem appears for a smartcard and so the problem goes with the smartcard. Sometimes this problem appears for a terminal only. And every time only a few user have this problem. The last days we had the effect, waiting 5 until 15 minutes solved the problem and the effect was gone. We have a two server FOG and when i login in the Admin GUIs always one of this servers can't show the sessions or show no sessions. As i say, a few minutes later everything was ok again. We are running Red Hat Linux. So it would be nice to see a solution :-) Greetings Detlev Am 04.02.2011 um 17:44 schrieb Carsten John: Hi folks, we are still having problems. What I found out in the meantime is that definitely gdm is the problem. It works for about a day (or a few days?). Then suddenly gdm does not provide login service any more, resulting the DTUs to hang in 26D. Obviously gdmdynamic stops communication with gdm. A gdmdynamic -l -v at the command line does not give any results and needs to be interrupted via CTRL+c. gdm also does not produce any further messages in syslog after the crash (debug mode is enabled). An ps -fax | grep gdm shows various alredy connected Xnewt sessions and some : \_ [gdm] defunct as well as gdmdynamic -b -d $SOME-NUMBER processes. The strange thing is that utsession -p shows sessions belonging to the user gdm after the crash. That never showed up before: utsession -p Token ID Registered Name Unix IDDisp State -- -- - Payflex.5011eb6900130100 ??? 13 D Payflex.5011eb6b00130100 ??? gdm19 D Payflex.5011eb7300130100 ??? 11 U Payflex.5011eb7600130100 ??? gdm31 D Payflex.5011eb7d00130100 ??? gdm23 D pseudo.00144f96d6c4??? gdm14 U pseudo.00144f9826a0??? X 34 U pseudo.00144f98290c??? gdm25 D pseudo.00144fa17e25??? X 41 U pseudo.00144fa65a8a??? gdm22 U pseudo.00144fa65b1e??? gdm45 D pseudo.00144fa7f723??? X 16 U pseudo.00144fa7f75b??? X 30 U pseudo.00144fa7f765??? XX 40 U pseudo.00144fa807a3??? gdm28 D pseudo.00144fa807b1??? gdm18 U pseudo.00144fa807be??? X 42 U pseudo.00144fa80858??? gdm37 U pseudo.00144fd18b3a??? 33 U pseudo.00144fd37c84??? 43 U pseudo.00144fd37c8e??? gdm24 D pseudo.0021283a2717??? gdm27 D pseudo.002128763446??? gdm20 D pseudo.002128763447??? gdm17 U pseudo.00212876348f??? XXX12 U Our gdm.conf (gdm 2.20) as follows: grep -v -e ^# /etc/gdm/gdm.conf | sed -e '/^$/d' [daemon] AutomaticLoginEnable=false AutomaticLogin= TimedLoginEnable=false TimedLogin= TimedLoginDelay=30 Greeter=/usr/lib/gdm/gdmlogin DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games RootPath=/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/games User=gdm Group=gdm LogDir=/var/log/gdm PostLoginScriptDir=/etc/gdm/PostLogin/ PreSessionScriptDir=/etc/gdm/PreSession/ PostSessionScriptDir=/etc/gdm/PostSession/ DisplayInitDir=/etc/gdm/Init FailsafeXserver= XKeepsCrashing=/etc/opt/SUNWut/gdm/XKeepsCrashing.sunray RebootCommand= HaltCommand= SuspendCommand= HibernateCommand= SystemCommandsInMenu=HALT;REBOOT;HIBERNATE;SUSPEND;CUSTOM_CMD AllowLogoutActions=HALT;REBOOT;HIBERNATE;SUSPEND;CUSTOM_CMD RBACSystemCommandKeys= ServAuthDir=/var/lib/gdm BaseXsession=/etc/gdm/Xsession SessionDesktopDir=/usr/share/gdm/BuiltInSessions/:/usr/share/xsessions/:/var/lib/menu-xdg/xsessions/:/etc/dm/Sessions/ DefaultSession=default.desktop UserAuthDir= UserAuthFBDir=/tmp UserAuthFile=.Xauthority StandardXServer=/usr/X11R6/bin/X Xnest=/usr/share/gdm/gdmXnestWrapper -br -audit 0 XnestUnscaledFontPath=true FirstVT=7 VTAllocation=false SoundProgram=/usr/lib/gdmplay DynamicXServers=true
Re: [SunRay-Users] 26D problems SRSS 5.1
On 02/04/2011 06:28 PM, Bob Doolittle wrote: Can you please share the output of gdmflexiserver --command VERSION? -Bob Hi Bob, root@capella: ~ # gdmflexiserver --command VERSION GDM 2.20.10 thx Carsten ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
[SunRay-Users] 26D problems SRSS 5.1
Hi folks, we are still having problems. What I found out in the meantime is that definitely gdm is the problem. It works for about a day (or a few days?). Then suddenly gdm does not provide login service any more, resulting the DTUs to hang in 26D. Obviously gdmdynamic stops communication with gdm. A gdmdynamic -l -v at the command line does not give any results and needs to be interrupted via CTRL+c. gdm also does not produce any further messages in syslog after the crash (debug mode is enabled). An ps -fax | grep gdm shows various alredy connected Xnewt sessions and some : \_ [gdm] defunct as well as gdmdynamic -b -d $SOME-NUMBER processes. The strange thing is that utsession -p shows sessions belonging to the user gdm after the crash. That never showed up before: utsession -p Token ID Registered Name Unix IDDisp State -- -- - Payflex.5011eb6900130100 ??? 13 D Payflex.5011eb6b00130100 ??? gdm19 D Payflex.5011eb7300130100 ??? 11 U Payflex.5011eb7600130100 ??? gdm31 D Payflex.5011eb7d00130100 ??? gdm23 D pseudo.00144f96d6c4??? gdm14 U pseudo.00144f9826a0??? X 34 U pseudo.00144f98290c??? gdm25 D pseudo.00144fa17e25??? X 41 U pseudo.00144fa65a8a??? gdm22 U pseudo.00144fa65b1e??? gdm45 D pseudo.00144fa7f723??? X 16 U pseudo.00144fa7f75b??? X 30 U pseudo.00144fa7f765??? XX 40 U pseudo.00144fa807a3??? gdm28 D pseudo.00144fa807b1??? gdm18 U pseudo.00144fa807be??? X 42 U pseudo.00144fa80858??? gdm37 U pseudo.00144fd18b3a??? 33 U pseudo.00144fd37c84??? 43 U pseudo.00144fd37c8e??? gdm24 D pseudo.0021283a2717??? gdm27 D pseudo.002128763446??? gdm20 D pseudo.002128763447??? gdm17 U pseudo.00212876348f??? XXX12 U Our gdm.conf (gdm 2.20) as follows: grep -v -e ^# /etc/gdm/gdm.conf | sed -e '/^$/d' [daemon] AutomaticLoginEnable=false AutomaticLogin= TimedLoginEnable=false TimedLogin= TimedLoginDelay=30 Greeter=/usr/lib/gdm/gdmlogin DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games RootPath=/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/games User=gdm Group=gdm LogDir=/var/log/gdm PostLoginScriptDir=/etc/gdm/PostLogin/ PreSessionScriptDir=/etc/gdm/PreSession/ PostSessionScriptDir=/etc/gdm/PostSession/ DisplayInitDir=/etc/gdm/Init FailsafeXserver= XKeepsCrashing=/etc/opt/SUNWut/gdm/XKeepsCrashing.sunray RebootCommand= HaltCommand= SuspendCommand= HibernateCommand= SystemCommandsInMenu=HALT;REBOOT;HIBERNATE;SUSPEND;CUSTOM_CMD AllowLogoutActions=HALT;REBOOT;HIBERNATE;SUSPEND;CUSTOM_CMD RBACSystemCommandKeys= ServAuthDir=/var/lib/gdm BaseXsession=/etc/gdm/Xsession SessionDesktopDir=/usr/share/gdm/BuiltInSessions/:/usr/share/xsessions/:/var/lib/menu-xdg/xsessions/:/etc/dm/Sessions/ DefaultSession=default.desktop UserAuthDir= UserAuthFBDir=/tmp UserAuthFile=.Xauthority StandardXServer=/usr/X11R6/bin/X Xnest=/usr/share/gdm/gdmXnestWrapper -br -audit 0 XnestUnscaledFontPath=true FirstVT=7 VTAllocation=false SoundProgram=/usr/lib/gdmplay DynamicXServers=true GdmXserverTimeout=30 [security] AllowRoot=true AllowRemoteRoot=true AllowRemoteAutoLogin=false RelaxPermissions=1 CheckDirOwner=true SupportAutomount=false DisallowTCP=true PamStack=gdm UtmpLineAttached=/dev/console UtmpLineRemote= UtmpPseudoDevice=false [xdmcp] Enable=false [gui] GtkTheme=Human [greeter] Browser=true MinimalUID=1000 Exclude=nobody IncludeAll=true LocaleFile=/etc/gdm/locale.conf Logo=/usr/share/pixmaps/gdmDebianLogo.xpm ConfigAvailable=false DefaultWelcome=true DefaultRemoteWelcome=true BackgroundColor=#00 GraphicalThemedColor=#00 GraphicalTheme=Human GraphicalThemeDir=/usr/share/gdm/themes/ GraphicalThemeRand=false SoundOnLoginFile=/usr/share/sounds/question.wav PreFetchProgram=/usr/lib/gdm/gdmprefetch @/etc/gdm/gdmprefetchlist [chooser] HostImageDir=/usr/share/hosts/ Hosts= Broadcast=true Multicast=false [debug] Enable=true Gestures=false [servers] 0=Standard device=/dev/console [server-Standard] name=Standard server command=/usr/X11R6/bin/X
Re: [SunRay-Users] 26D problems SRSS 5.1
Can you please share the output of gdmflexiserver --command VERSION? -Bob On 02/04/11 11:44, Carsten John wrote: Hi folks, we are still having problems. What I found out in the meantime is that definitely gdm is the problem. It works for about a day (or a few days?). Then suddenly gdm does not provide login service any more, resulting the DTUs to hang in 26D. Obviously gdmdynamic stops communication with gdm. A gdmdynamic -l -v at the command line does not give any results and needs to be interrupted via CTRL+c. gdm also does not produce any further messages in syslog after the crash (debug mode is enabled). An ps -fax | grep gdm shows various alredy connected Xnewt sessions and some : \_ [gdm]defunct as well as gdmdynamic -b -d $SOME-NUMBER processes. The strange thing is that utsession -p shows sessions belonging to the user gdm after the crash. That never showed up before: utsession -p Token ID Registered Name Unix IDDisp State -- -- - Payflex.5011eb6900130100 ??? 13 D Payflex.5011eb6b00130100 ??? gdm19 D Payflex.5011eb7300130100 ??? 11 U Payflex.5011eb7600130100 ??? gdm31 D Payflex.5011eb7d00130100 ??? gdm23 D pseudo.00144f96d6c4??? gdm14 U pseudo.00144f9826a0??? X 34 U pseudo.00144f98290c??? gdm25 D pseudo.00144fa17e25??? X 41 U pseudo.00144fa65a8a??? gdm22 U pseudo.00144fa65b1e??? gdm45 D pseudo.00144fa7f723??? X 16 U pseudo.00144fa7f75b??? X 30 U pseudo.00144fa7f765??? XX 40 U pseudo.00144fa807a3??? gdm28 D pseudo.00144fa807b1??? gdm18 U pseudo.00144fa807be??? X 42 U pseudo.00144fa80858??? gdm37 U pseudo.00144fd18b3a??? 33 U pseudo.00144fd37c84??? 43 U pseudo.00144fd37c8e??? gdm24 D pseudo.0021283a2717??? gdm27 D pseudo.002128763446??? gdm20 D pseudo.002128763447??? gdm17 U pseudo.00212876348f??? XXX12 U Our gdm.conf (gdm 2.20) as follows: grep -v -e ^# /etc/gdm/gdm.conf | sed -e '/^$/d' [daemon] AutomaticLoginEnable=false AutomaticLogin= TimedLoginEnable=false TimedLogin= TimedLoginDelay=30 Greeter=/usr/lib/gdm/gdmlogin DefaultPath=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games RootPath=/usr/local/bin:/usr/local/sbin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/bin/X11:/usr/games User=gdm Group=gdm LogDir=/var/log/gdm PostLoginScriptDir=/etc/gdm/PostLogin/ PreSessionScriptDir=/etc/gdm/PreSession/ PostSessionScriptDir=/etc/gdm/PostSession/ DisplayInitDir=/etc/gdm/Init FailsafeXserver= XKeepsCrashing=/etc/opt/SUNWut/gdm/XKeepsCrashing.sunray RebootCommand= HaltCommand= SuspendCommand= HibernateCommand= SystemCommandsInMenu=HALT;REBOOT;HIBERNATE;SUSPEND;CUSTOM_CMD AllowLogoutActions=HALT;REBOOT;HIBERNATE;SUSPEND;CUSTOM_CMD RBACSystemCommandKeys= ServAuthDir=/var/lib/gdm BaseXsession=/etc/gdm/Xsession SessionDesktopDir=/usr/share/gdm/BuiltInSessions/:/usr/share/xsessions/:/var/lib/menu-xdg/xsessions/:/etc/dm/Sessions/ DefaultSession=default.desktop UserAuthDir= UserAuthFBDir=/tmp UserAuthFile=.Xauthority StandardXServer=/usr/X11R6/bin/X Xnest=/usr/share/gdm/gdmXnestWrapper -br -audit 0 XnestUnscaledFontPath=true FirstVT=7 VTAllocation=false SoundProgram=/usr/lib/gdmplay DynamicXServers=true GdmXserverTimeout=30 [security] AllowRoot=true AllowRemoteRoot=true AllowRemoteAutoLogin=false RelaxPermissions=1 CheckDirOwner=true SupportAutomount=false DisallowTCP=true PamStack=gdm UtmpLineAttached=/dev/console UtmpLineRemote= UtmpPseudoDevice=false [xdmcp] Enable=false [gui] GtkTheme=Human [greeter] Browser=true MinimalUID=1000 Exclude=nobody IncludeAll=true LocaleFile=/etc/gdm/locale.conf Logo=/usr/share/pixmaps/gdmDebianLogo.xpm ConfigAvailable=false DefaultWelcome=true DefaultRemoteWelcome=true BackgroundColor=#00 GraphicalThemedColor=#00 GraphicalTheme=Human GraphicalThemeDir=/usr/share/gdm/themes/ GraphicalThemeRand=false SoundOnLoginFile=/usr/share/sounds/question.wav PreFetchProgram=/usr/lib/gdm/gdmprefetch @/etc/gdm/gdmprefetchlist [chooser] HostImageDir=/usr/share/hosts/ Hosts= Broadcast=true Multicast=false [debug] Enable=true
[SunRay-Users] 26D problems SRSS 5.1
Hi everybody,
we are experiencing serious problems after upgrading our SunRay servers
to SRSS 5.1.
We are running on Ubuntu 10.4 LTS (I know it's unsupported)
DTUs are all SunRay 2FS (~ 50 in total), matching FW that came with SRSS
5.1 installed.
The DTUs are connected via dedicated subnet.
The 2 servers are SuperMicro quad AMD 8-cores with 128GB RAM installed.
An increasing number of DTUs are falling into 26D status after the user
logs off (or pulls his smartcard).
After rebooting the server(s) everything seems to be fine for a while.
Login is possible without problems but after some time more and more
DTUs are falling into 26D after logging off.
utsession -k -t $TOKEN and rebooting the DTU does not help (we used this
with our old installation when this situation rarely occured).
We already changed the Java version SRSS uses from Java6-build-22 back
to build-13.
We are seeing messages like
Failed to connect to server after 15 retries
in /var/opt/SUNWut/log/auth_log
Any suggestions.
thanks
Carsten
#cat /etc/opt/SUNWut/auth.props |grep -v ^$ |grep -v ^#
timeout = 240
quickTimeout = 10
workers = 8
maxStarting = 1000
sessionHost = localhost
sessionPort = 7007
tokenDir = /var/opt/SUNWut/tokens
sessionTypesFile = sessionTypes.props
port = 7009
moduleDir = /opt/SUNWut/lib/modules
policy=utpolicy
allowLANConnections = false
terminateEnable = true
gmSignatureFile = /etc/opt/SUNWut/gmSignature
enableLoadBalancing = true
logFacility = user
logPriClientError = info
logPriDebug = OFF
logPriNotice = info
logPriWarning = info
logPriConfigError = info
logPriUnexpectedError = info
smartcardConfigSource = LDAP probe_order.conf
terminalTokens = MicroPayflex Mondex at88sc1608 Payflex Cyberflex_Access
selectAtLogin=false
remoteSelect=false
this is the log of one DTU after removing the smartcard:
#cat /var/log/messages | grep 00144fd18b60
Jan 19 11:18:36 capella utauthd: Worker2 NOTICE: DISCONNECT
IEEE802.00144fd18b60, Payflex.5011eb6a00130100 token removed:
Payflex.5011eb6a00130100
Jan 19 11:18:36 capella utauthd: Worker2 NOTICE: whichServer
pseudo.00144fd18b60:
Jan 19 11:18:36 capella utauthd: Worker2 NOTICE: CLAIMED by
StartSession.m5 NAME: pseudo.00144fd18b60 PARAMETERS:
{stealProtected=true, terminalIPA=172.19.0.35, type=pseudo,
fw=4.2_77_2009.10.19.17.01,Boot:MfgPkg_4.15_2006.07.20.16.57;
2006.07.20-17:04:56-PDT, state=connected, cause=insert, doamgh=true,
barrierLevel=420, lockaction=disconnect, rawId=00144fd18b60,
terminalCID=IEEE802.00144fd18b60, MTU=1500, tokenSeq=3,
firstServer=ac130002, namespace=IEEE802, keyTypes=dsa-sha1-x1,dsa-sha1,
ddcconfig=1:0, clientRand=w.xywU5dhKjl8f3mTw/H86Y.HVwS.ndIl7BcuthII.u,
id=00144fd18b60, realIP=ac130023, startRes=1280x1024:1280x1024,
useReal=true, event=insert, sn=00144fd18b60, rawType=pseudo,
clientKeyStatus=unconfirmed, hw=SunRayP8-FS, initState=0,
usersession=false, _=1}
Jan 19 11:18:36 capella utauthd: Worker2 NOTICE: CONNECT
IEEE802.00144fd18b60, pseudo.00144fd18b60, all connections allowed
Jan 19 11:18:36 capella utdtsession: Hotdesk
(17,pseudo.00144fd18b60,default)
Jan 19 11:18:36 capella utauthd: Worker7 NOTICE: SESSION_OK
pseudo.00144fd18b60
#utdesktop -lw
Desktop ID Location No-Session (H:M:S)
--
00144fd18b60 0:11:0
1 desktop currently in error state without a session.
#utgstatus
host flagsinterface flagsinterface flags
172.16.0.0/16 172.19.0.0/24
------
capella TN172.16.8.4 U--172.19.0.1 UAM
aldebaran TN172.16.8.5 U--172.19.0.2 UAM
___
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
We've had this happen randomly, but it doesn't sound like it's as bad as you
have it.
When it happens, I just go into the web console and kill the session. The user
has to unplug power from the DTU, but after that, it functions normally
-Original Message-
From: sunray-users-boun...@filibeto.org
[mailto:sunray-users-boun...@filibeto.org] On Behalf Of Carsten John
Sent: Wednesday, January 19, 2011 5:46 AM
To: sunray-users@filibeto.org
Subject: [SunRay-Users] 26D problems SRSS 5.1
Hi everybody,
we are experiencing serious problems after upgrading our SunRay servers to SRSS
5.1.
We are running on Ubuntu 10.4 LTS (I know it's unsupported)
DTUs are all SunRay 2FS (~ 50 in total), matching FW that came with SRSS
5.1 installed.
The DTUs are connected via dedicated subnet.
The 2 servers are SuperMicro quad AMD 8-cores with 128GB RAM installed.
An increasing number of DTUs are falling into 26D status after the user logs
off (or pulls his smartcard).
After rebooting the server(s) everything seems to be fine for a while.
Login is possible without problems but after some time more and more DTUs are
falling into 26D after logging off.
utsession -k -t $TOKEN and rebooting the DTU does not help (we used this with
our old installation when this situation rarely occured).
We already changed the Java version SRSS uses from Java6-build-22 back to
build-13.
We are seeing messages like
Failed to connect to server after 15 retries
in /var/opt/SUNWut/log/auth_log
Any suggestions.
thanks
Carsten
#cat /etc/opt/SUNWut/auth.props |grep -v ^$ |grep -v ^#
timeout = 240
quickTimeout = 10
workers = 8
maxStarting = 1000
sessionHost = localhost
sessionPort = 7007
tokenDir = /var/opt/SUNWut/tokens
sessionTypesFile = sessionTypes.props
port = 7009
moduleDir = /opt/SUNWut/lib/modules
policy=utpolicy
allowLANConnections = false
terminateEnable = true
gmSignatureFile = /etc/opt/SUNWut/gmSignature enableLoadBalancing = true
logFacility = user logPriClientError = info logPriDebug = OFF logPriNotice =
info logPriWarning = info logPriConfigError = info logPriUnexpectedError = info
smartcardConfigSource = LDAP probe_order.conf terminalTokens = MicroPayflex
Mondex at88sc1608 Payflex Cyberflex_Access selectAtLogin=false
remoteSelect=false
this is the log of one DTU after removing the smartcard:
#cat /var/log/messages | grep 00144fd18b60 Jan 19 11:18:36 capella utauthd:
Worker2 NOTICE: DISCONNECT IEEE802.00144fd18b60, Payflex.5011eb6a00130100 token
removed:
Payflex.5011eb6a00130100
Jan 19 11:18:36 capella utauthd: Worker2 NOTICE: whichServer
pseudo.00144fd18b60:
Jan 19 11:18:36 capella utauthd: Worker2 NOTICE: CLAIMED by
StartSession.m5 NAME: pseudo.00144fd18b60 PARAMETERS:
{stealProtected=true, terminalIPA=172.19.0.35, type=pseudo,
fw=4.2_77_2009.10.19.17.01,Boot:MfgPkg_4.15_2006.07.20.16.57;
2006.07.20-17:04:56-PDT, state=connected, cause=insert, doamgh=true,
barrierLevel=420, lockaction=disconnect, rawId=00144fd18b60,
terminalCID=IEEE802.00144fd18b60, MTU=1500, tokenSeq=3, firstServer=ac130002,
namespace=IEEE802, keyTypes=dsa-sha1-x1,dsa-sha1, ddcconfig=1:0,
clientRand=w.xywU5dhKjl8f3mTw/H86Y.HVwS.ndIl7BcuthII.u,
id=00144fd18b60, realIP=ac130023, startRes=1280x1024:1280x1024, useReal=true,
event=insert, sn=00144fd18b60, rawType=pseudo, clientKeyStatus=unconfirmed,
hw=SunRayP8-FS, initState=0, usersession=false, _=1} Jan 19 11:18:36 capella
utauthd: Worker2 NOTICE: CONNECT IEEE802.00144fd18b60, pseudo.00144fd18b60, all
connections allowed Jan 19 11:18:36 capella utdtsession: Hotdesk
(17,pseudo.00144fd18b60,default)
Jan 19 11:18:36 capella utauthd: Worker7 NOTICE: SESSION_OK
pseudo.00144fd18b60
#utdesktop -lw
Desktop ID Location No-Session (H:M:S)
--
00144fd18b60 0:11:0
1 desktop currently in error state without a session.
#utgstatus
host flagsinterface flagsinterface flags
172.16.0.0/16 172.19.0.0/24
------
capella TN172.16.8.4 U--172.19.0.1 UAM
aldebaran TN172.16.8.5 U--172.19.0.2 UAM
___
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
___
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On 01/19/11 15:13, Carl Holzhauer wrote: We've had this happen randomly, but it doesn't sound like it's as bad as you have it. When it happens, I just go into the web console and kill the session. The user has to unplug power from the DTU, but after that, it functions normally This is what we did in the past using the CLI issuing utsession -k -t What I found out in the meantimeis that the problem might be gdm not starting a new session At the moment I'm quite confused: After server reboot everything runs smoothly, gdm shows up on every DTU, login is possible. After some time the number of dead DTUs increases, as no new login launched after logout. The DTU remains broken until the next reboot. thx Carsten ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
Hi everybody, in the meantime I found out, that no new logins are possible even with a newly connected DTU (so there are no hanging sessions involved). The DTU that was never connected after the last reboot also remains in 26D when connected. thx Carsten ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
A few things to check: - Does gdmdynamic -l list the same set of displays as utsession -p? - Do you see an Xnewt process for every display in gdmdynamic -l? -Bob On 01/19/11 10:34, Carsten John wrote: Hi everybody, in the meantime I found out, that no new logins are possible even with a newly connected DTU (so there are no hanging sessions involved). The DTU that was never connected after the last reboot also remains in 26D when connected. thx Carsten ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On 01/19/2011 05:38 PM, Bob Doolittle wrote: A few things to check: - Does gdmdynamic -l list the same set of displays as utsession -p? Not really... Server 1: 23 displays occur in both outputs, 4 are unique to gdmdynamic and 17 to utsession. Server 2: 18 displays occur in both outputs, 5 are unique to gdmdynamic and 1 to utsession. - Do you see an Xnewt process for every display in gdmdynamic -l? Also a no... Server 1: 13 displays listed in gdmdynamic have a xnewt process, 10 don't Server 2: 20 displays have a process, 7 don't Interestingly, if you substract display :0 which is happily running Xorg on the local display, there is a matching number (9 and 6) of gdm processes with exactly one child: [kill] defunct. Elmar ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
On 01/19/11 16:19, Elmar Prüße wrote: On 01/19/2011 05:38 PM, Bob Doolittle wrote: A few things to check: - Does gdmdynamic -l list the same set of displays as utsession -p? Not really... Server 1: 23 displays occur in both outputs, 4 are unique to gdmdynamic and 17 to utsession. Server 2: 18 displays occur in both outputs, 5 are unique to gdmdynamic and 1 to utsession. - Do you see an Xnewt process for every display in gdmdynamic -l? Also a no... Server 1: 13 displays listed in gdmdynamic have a xnewt process, 10 don't Server 2: 20 displays have a process, 7 don't Interestingly, if you substract display :0 which is happily running Xorg on the local display, there is a matching number (9 and 6) of gdm processes with exactly one child: [kill] defunct. There are some session types that won't utilize an Xnewt process (mostly things displaying icons like insert smartcard or a multihead secondary waiting for primary to connect to FOG), so it's possible that the utsession -p count would be higher. Except for display 0, however all of the gdmdynamic sessions should be running an Xnewt. The X server appears to be dying and GDM is not restarting it. Can you locate a core dump? Are your users in the habit of using the Control-Alt-Bksp-Bksp key sequence to abort the X server? GDM has had a history of bugs related to handling that. -Bob ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
Re: [SunRay-Users] 26D problems SRSS 5.1
I think I've found at least one major culprit. There is a line in gdm.conf that configures a backup script to be run if the X Server fails. FailsafeXServer=/etc/gdm/failsafeXServer In order to be able to run an emergency xserver on the failing display without having gdm interfere, it checks whether gdm is the parent and if so sends a SIGSTOP. That's those zombie kill processes I noticed. This might explain the severity of our 26D problems. Elmar ___ SunRay-Users mailing list SunRay-Users@filibeto.org http://www.filibeto.org/mailman/listinfo/sunray-users
