From gnutbeam at gmail.com Mon Oct 7 18:53:10 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Mon, 07 Oct 2013 13:53:10 -0500 Subject: [K12OSN] Physically thin clients crashing when trying to boot Message-ID: <52530316.1080704@gmail.com> I upgraded our ltsp server to CentOS 6.4. I also upgraded the ltsp-server package. Did a ltsp-build-client, after checking the config files, removing the old /opt/ltsp/i386 directory, checking nfs, dhcp config, etc. A new virtual pxeclient is working, although X restarts the very first time you try and log in. The physical clients won't even boot properly. The error varies depending on the client. dhcp is working. They can boot to the network using PXE and retrieve the img to boot linux. The majority of clients crash after the "Booting Linux" message. A long list of messages; hex then a question mark then a message. Another machine that is different hardware, gives this message after "Booting Linux" [drm] nouveau 0000:01:00.0 0x824C: Init table command not found: 0x06 I installed ltsp-server from the repo and I get these versions: ltsp-release-5-9.el6.noarch ltsp-server-5.4.5-22.el6.x86_64 ltspfs-1.1-7.el6.x86_64 Which is odd because according to the web page the stable build is 5.4.5-20.el6 from the k12linux.repo (the s3amazon address I think). Any ideas what is happening? Any help is much appreciated. Thanks. Gary. From sergio.chaves at gmail.com Sun Oct 13 22:39:33 2013 From: sergio.chaves at gmail.com (Sergio Chaves) Date: Sun, 13 Oct 2013 18:39:33 -0400 Subject: [K12OSN] Physically thin clients crashing when trying to boot In-Reply-To: <52530316.1080704@gmail.com> References: <52530316.1080704@gmail.com> Message-ID: Nothing on the server log files? On this particular error,"[drm] nouveau 0000:01:00.0 0x824C: Init table command not found: 0x06", it seems like the system is trying to load the open source nVidia driver but it fails. Do all the other clients have nVidia video cards as well? On Mon, Oct 7, 2013 at 2:53 PM, Gary Nutbeam wrote: > I upgraded our ltsp server to CentOS 6.4. I also upgraded the ltsp-server > package. Did a ltsp-build-client, after checking the config files, removing > the old /opt/ltsp/i386 directory, checking nfs, dhcp config, etc. A new > virtual pxeclient is working, although X restarts the very first time you > try and log in. The physical clients won't even boot properly. The error > varies depending on the client. > > dhcp is working. They can boot to the network using PXE and retrieve the img > to boot linux. > > The majority of clients crash after the "Booting Linux" message. A long list > of messages; hex then a question mark then a message. Another machine that > is different hardware, gives this message after "Booting Linux" > > [drm] nouveau 0000:01:00.0 0x824C: Init table command not found: 0x06 > > I installed ltsp-server from the repo and I get these versions: > > ltsp-release-5-9.el6.noarch > ltsp-server-5.4.5-22.el6.x86_64 > ltspfs-1.1-7.el6.x86_64 > > Which is odd because according to the web page the stable build is > 5.4.5-20.el6 from the k12linux.repo (the s3amazon address I think). > > Any ideas what is happening? Any help is much appreciated. > > Thanks. > > Gary. > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From gnutbeam at gmail.com Mon Oct 14 14:53:27 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Mon, 14 Oct 2013 09:53:27 -0500 Subject: [K12OSN] Physically thin clients crashing when trying to boot In-Reply-To: References: <52530316.1080704@gmail.com> Message-ID: <525C0567.1050106@gmail.com> Nothing in the logs. It seems like my clients were too old, i.e. lacking the resources. Replaced them with the 1700s from disklessworkstations.com. Now they work :-D There was a kernel parameter in the pxelinux.cfg/default file "video=LVDS-1:d" that once removed, got the nvidia system booting. I'm going to open a new thread on the LDM problem I'm having though. Seems unstable, to put it mildly. On 10/13/2013 05:39 PM, Sergio Chaves wrote: > Nothing on the server log files? > On this particular error,"[drm] nouveau 0000:01:00.0 0x824C: Init > table command not found: 0x06", it seems like the system is trying to > load the open source nVidia driver but it fails. Do all the other > clients have nVidia video cards as well? > > On Mon, Oct 7, 2013 at 2:53 PM, Gary Nutbeam wrote: >> I upgraded our ltsp server to CentOS 6.4. I also upgraded the ltsp-server >> package. Did a ltsp-build-client, after checking the config files, removing >> the old /opt/ltsp/i386 directory, checking nfs, dhcp config, etc. A new >> virtual pxeclient is working, although X restarts the very first time you >> try and log in. The physical clients won't even boot properly. The error >> varies depending on the client. >> >> dhcp is working. They can boot to the network using PXE and retrieve the img >> to boot linux. >> >> The majority of clients crash after the "Booting Linux" message. A long list >> of messages; hex then a question mark then a message. Another machine that >> is different hardware, gives this message after "Booting Linux" >> >> [drm] nouveau 0000:01:00.0 0x824C: Init table command not found: 0x06 >> >> I installed ltsp-server from the repo and I get these versions: >> >> ltsp-release-5-9.el6.noarch >> ltsp-server-5.4.5-22.el6.x86_64 >> ltspfs-1.1-7.el6.x86_64 >> >> Which is odd because according to the web page the stable build is >> 5.4.5-20.el6 from the k12linux.repo (the s3amazon address I think). >> >> Any ideas what is happening? Any help is much appreciated. >> >> Thanks. >> >> Gary. >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From gnutbeam at gmail.com Mon Oct 14 15:03:02 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Mon, 14 Oct 2013 10:03:02 -0500 Subject: [K12OSN] LDM crashing on trying to log in. Message-ID: <525C07A6.1050802@gmail.com> I'm having stability problems with LDM. I'm using decent thin clients now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB RAM etc.). I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at ltsprepo.s3.amazonaws.com. When first attempting to log in, after entering the username, LDM seems to crash, and restart. The second attempt to login works fine. If it doesn't crash on the first attempt, the X session crashes very shortly afterwards, usually when trying to launch an application. After the initial weirdness, everything seems to settle down and work. This behavior happens on both the physical thin clients AND a virtual client. Has anyone seen this problem and know what might be causing it? Thanks. Gary. From k12ltsp at infocentrality.co.uk Mon Oct 14 15:42:37 2013 From: k12ltsp at infocentrality.co.uk (k12ltsp) Date: Mon, 14 Oct 2013 16:42:37 +0100 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C07A6.1050802@gmail.com> References: <525C07A6.1050802@gmail.com> Message-ID: <525C10ED.1020609@infocentrality.co.uk> Hi Gary, We have the same problem I'm afraid. Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom processors in the clients with at least 1GByte RAM. Usually work reliably once logged in. Also cannot shutdown or reboot the client. Tried some suggestions from the list, but they didn't help. Things seem to have got worse recently, and I don't have the skills to try and fix it, we do IT support for small businesses and web/database apps. Now trying Debian Wheezy with LTSP - just works, so looks like I shall jump ship. Regards Trevor http://www.infocentrality.co.uk On 14/10/13 16:03, Gary Nutbeam wrote: > I'm having stability problems with LDM. I'm using decent thin clients > now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB > RAM etc.). > > I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at > ltsprepo.s3.amazonaws.com. > > When first attempting to log in, after entering the username, LDM seems > to crash, and restart. The second attempt to login works fine. If it > doesn't crash on the first attempt, the X session crashes very shortly > afterwards, usually when trying to launch an application. After the > initial weirdness, everything seems to settle down and work. > > This behavior happens on both the physical thin clients AND a virtual > client. > > Has anyone seen this problem and know what might be causing it? > > Thanks. > > Gary. > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From gnutbeam at gmail.com Mon Oct 14 16:02:33 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Mon, 14 Oct 2013 11:02:33 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C10ED.1020609@infocentrality.co.uk> References: <525C07A6.1050802@gmail.com> <525C10ED.1020609@infocentrality.co.uk> Message-ID: <525C1599.6070501@gmail.com> It would be a lot of work for me to move to Debian, because of applications to be moved, tested on Debian, etc. Plus everything we do is CentOS and Fedora based. I can't shutdown or reboot the client either. I saw a hack on the list that I haven't tried yet to "fix" the shutdown/reboot problem. On 10/14/2013 10:42 AM, k12ltsp wrote: > Hi Gary, > > We have the same problem I'm afraid. > Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom > processors in the clients with at least 1GByte RAM. > Usually work reliably once logged in. > > Also cannot shutdown or reboot the client. Tried some suggestions from > the list, but they didn't help. > > Things seem to have got worse recently, and I don't have the skills to > try and fix it, we do IT support for small businesses and web/database apps. > > Now trying Debian Wheezy with LTSP - just works, so looks like I shall > jump ship. > > Regards > Trevor > http://www.infocentrality.co.uk > > On 14/10/13 16:03, Gary Nutbeam wrote: >> I'm having stability problems with LDM. I'm using decent thin clients >> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB >> RAM etc.). >> >> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at >> ltsprepo.s3.amazonaws.com. >> >> When first attempting to log in, after entering the username, LDM seems >> to crash, and restart. The second attempt to login works fine. If it >> doesn't crash on the first attempt, the X session crashes very shortly >> afterwards, usually when trying to launch an application. After the >> initial weirdness, everything seems to settle down and work. >> >> This behavior happens on both the physical thin clients AND a virtual >> client. >> >> Has anyone seen this problem and know what might be causing it? >> >> Thanks. >> >> Gary. >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From radek at bursztynowski.waw.pl Mon Oct 14 21:51:42 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Mon, 14 Oct 2013 23:51:42 +0200 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C1599.6070501@gmail.com> References: <525C07A6.1050802@gmail.com> Message-ID: <1381787502.12062.34.camel@alpaga.bursztynowski.waw.pl> Hello, I have the same problems. The problem with first attempting to log in I solved (I believe). This solution concerns i386 and x86_64 thin client image (epel6-i386 and epel-6-x86_64). I added to /opt/ltsp/chroot/etc/sysconfig three files which I couldn't find after ltsp-build-client script execution: (Polish parameters) clock ZONE="Warsaw/Europe" i18n LANG="pl_PL.UTF-8" keyboard KEYTABLE="pl2" MODEL="pc105" LAYOUT="pl" KEYBOARDTYPE="pc" and my /opt/ltsp/i386/etc/ltsp_chroot is not empty but includes LTSP_CHROOT=/opt/ltsp/i386 line and /opt/ltsp/x86_64/etc/ltsp_chroot includes LTSP_CHROOT=/opt/ltsp/x86_64 line. Now LDM doesn't reload and works fine. I am not sure that this the best solution, but it helped me. Thin client still doesn't reboot or shutdown. I tried Debian LTSP too, but I retrieved. Finally I moved Debian thin client image to LTSP on CentOS 6.4 and I can use it, but I prefer epel-6 images. In my opinion the most stable thin client image is Scientific Linux 6.1 (ltsp-server 5.2) and I recommend it. Best regards, Radek --- > It would be a lot of work for me to move to Debian, because of > applications to be moved, tested on Debian, etc. Plus everything we do > is CentOS and Fedora based. > > I can't shutdown or reboot the client either. I saw a hack on the list > that I haven't tried yet to "fix" the shutdown/reboot problem. > > On 10/14/2013 10:42 AM, k12ltsp wrote: > > Hi Gary, > > > > We have the same problem I'm afraid. > > Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom > > processors in the clients with at least 1GByte RAM. > > Usually work reliably once logged in. > > > > Also cannot shutdown or reboot the client. Tried some suggestions from > > the list, but they didn't help. > > > > Things seem to have got worse recently, and I don't have the skills to > > try and fix it, we do IT support for small businesses and web/database apps. > > > > Now trying Debian Wheezy with LTSP - just works, so looks like I shall > > jump ship. > > > > Regards > > Trevor > > http://www.infocentrality.co.uk > > > > On 14/10/13 16:03, Gary Nutbeam wrote: > >> I'm having stability problems with LDM. I'm using decent thin clients > >> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB > >> RAM etc.). > >> > >> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at > >> ltsprepo.s3.amazonaws.com. > >> > >> When first attempting to log in, after entering the username, LDM seems > >> to crash, and restart. The second attempt to login works fine. If it > >> doesn't crash on the first attempt, the X session crashes very shortly > >> afterwards, usually when trying to launch an application. After the > >> initial weirdness, everything seems to settle down and work. > >> > >> This behavior happens on both the physical thin clients AND a virtual > >> client. > >> > >> Has anyone seen this problem and know what might be causing it? > >> > >> Thanks. > >> > >> Gary. > >> > >> _______________________________________________ > >> K12OSN mailing list > >> K12OSN at redhat.com > >> https://www.redhat.com/mailman/listinfo/k12osn > >> For more info see > > > > _______________________________________________ > > K12OSN mailing list > > K12OSN at redhat.com > > https://www.redhat.com/mailman/listinfo/k12osn > > For more info see > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From enslaver at enslaver.com Mon Oct 14 22:03:20 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Mon, 14 Oct 2013 17:03:20 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C1599.6070501@gmail.com> References: <525C07A6.1050802@gmail.com> <525C10ED.1020609@infocentrality.co.uk> <525C1599.6070501@gmail.com> Message-ID: <525C6A28.1020005@enslaver.com> The EPEL repo is the current most stable one, I have had some issues with the server that hosts my development code. It had to do a lost file recovery so i'm thinking a beta version got into the repo. I'll fix when I can, but for now use the rpms from EPEL. On 10/14/13 11:02 AM, Gary Nutbeam wrote: > It would be a lot of work for me to move to Debian, because of > applications to be moved, tested on Debian, etc. Plus everything we do > is CentOS and Fedora based. > > I can't shutdown or reboot the client either. I saw a hack on the list > that I haven't tried yet to "fix" the shutdown/reboot problem. > > On 10/14/2013 10:42 AM, k12ltsp wrote: >> Hi Gary, >> >> We have the same problem I'm afraid. >> Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom >> processors in the clients with at least 1GByte RAM. >> Usually work reliably once logged in. >> >> Also cannot shutdown or reboot the client. Tried some suggestions from >> the list, but they didn't help. >> >> Things seem to have got worse recently, and I don't have the skills to >> try and fix it, we do IT support for small businesses and >> web/database apps. >> >> Now trying Debian Wheezy with LTSP - just works, so looks like I shall >> jump ship. >> >> Regards >> Trevor >> http://www.infocentrality.co.uk >> >> On 14/10/13 16:03, Gary Nutbeam wrote: >>> I'm having stability problems with LDM. I'm using decent thin clients >>> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB >>> RAM etc.). >>> >>> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp >>> repo at >>> ltsprepo.s3.amazonaws.com. >>> >>> When first attempting to log in, after entering the username, LDM seems >>> to crash, and restart. The second attempt to login works fine. If it >>> doesn't crash on the first attempt, the X session crashes very shortly >>> afterwards, usually when trying to launch an application. After the >>> initial weirdness, everything seems to settle down and work. >>> >>> This behavior happens on both the physical thin clients AND a virtual >>> client. >>> >>> Has anyone seen this problem and know what might be causing it? >>> >>> Thanks. >>> >>> Gary. >>> >>> _______________________________________________ >>> K12OSN mailing list >>> K12OSN at redhat.com >>> https://www.redhat.com/mailman/listinfo/k12osn >>> For more info see >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see >> > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From burke at thealmquists.net Tue Oct 15 06:26:02 2013 From: burke at thealmquists.net (Burke Almquist) Date: Tue, 15 Oct 2013 01:26:02 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C6A28.1020005@enslaver.com> References: <525C07A6.1050802@gmail.com> <525C10ED.1020609@infocentrality.co.uk> <525C1599.6070501@gmail.com> <525C6A28.1020005@enslaver.com> Message-ID: <4E0F4D7E-86D7-402E-9574-A1DB0BE5F064@thealmquists.net> On Oct 14, 2013, at 5:03 PM, Joshua Trimm wrote: > The EPEL repo is the current most stable one, I have had some issues with the server that hosts my development code. It had to do a lost file recovery so i'm thinking a beta version got into the repo. I'll fix when I can, but for now use the rpms from EPEL. I've noticed the same thing on Scientific Linux 6.4. I went back to using the "old" install instructions on the wiki, the ones that use the EPEL repos. I think the ones on amazon S3 are maybe only usable on Fedora 18? Why they are mixing them up with the EL install instructions is beyond me. Trying to build using the new instructions a couple months ago it complained about not having the Mock package and a certain version installed. No one seemed to know why the instructions were changed so I just went back to the old ones. Seems to be working for the most part. From gnutbeam at gmail.com Tue Oct 15 15:39:08 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Tue, 15 Oct 2013 10:39:08 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <1381787502.12062.34.camel@alpaga.bursztynowski.waw.pl> References: <525C07A6.1050802@gmail.com> <1381787502.12062.34.camel@alpaga.bursztynowski.waw.pl> Message-ID: <525D619C.2060901@gmail.com> Thanks for the info. Unfortunately I tried this with US information substituted and still have LDM crashing. I was running a Scientific Linux client and it was working better. I'll see if I can rollback to that, or maybe try the version out of the EPEL repo. On 10/14/2013 04:51 PM, Radek Bursztynowski wrote: > Hello, > > I have the same problems. The problem with first attempting to log in I > solved (I believe). This solution concerns i386 and x86_64 thin client > image (epel6-i386 and epel-6-x86_64). > > I added to /opt/ltsp/chroot/etc/sysconfig three files which I couldn't > find after ltsp-build-client script execution: > > > (Polish parameters) > clock > ZONE="Warsaw/Europe" > > i18n > LANG="pl_PL.UTF-8" > > keyboard > KEYTABLE="pl2" > MODEL="pc105" > LAYOUT="pl" > KEYBOARDTYPE="pc" > > and my /opt/ltsp/i386/etc/ltsp_chroot is not empty but includes > > LTSP_CHROOT=/opt/ltsp/i386 line > > and /opt/ltsp/x86_64/etc/ltsp_chroot includes > > LTSP_CHROOT=/opt/ltsp/x86_64 line. > > Now LDM doesn't reload and works fine. > > I am not sure that this the best solution, but it helped me. > > Thin client still doesn't reboot or shutdown. > > I tried Debian LTSP too, but I retrieved. Finally I moved Debian thin > client image to LTSP on CentOS 6.4 and I can use it, but I prefer epel-6 > images. In my opinion the most stable thin client image is Scientific > Linux 6.1 (ltsp-server 5.2) and I recommend it. > > Best regards, > Radek > > --- >> It would be a lot of work for me to move to Debian, because of >> applications to be moved, tested on Debian, etc. Plus everything we do >> is CentOS and Fedora based. >> >> I can't shutdown or reboot the client either. I saw a hack on the list >> that I haven't tried yet to "fix" the shutdown/reboot problem. >> >> On 10/14/2013 10:42 AM, k12ltsp wrote: >>> Hi Gary, >>> >>> We have the same problem I'm afraid. >>> Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom >>> processors in the clients with at least 1GByte RAM. >>> Usually work reliably once logged in. >>> >>> Also cannot shutdown or reboot the client. Tried some suggestions from >>> the list, but they didn't help. >>> >>> Things seem to have got worse recently, and I don't have the skills to >>> try and fix it, we do IT support for small businesses and web/database apps. >>> >>> Now trying Debian Wheezy with LTSP - just works, so looks like I shall >>> jump ship. >>> >>> Regards >>> Trevor >>> http://www.infocentrality.co.uk >>> >>> On 14/10/13 16:03, Gary Nutbeam wrote: >>>> I'm having stability problems with LDM. I'm using decent thin clients >>>> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB >>>> RAM etc.). >>>> >>>> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at >>>> ltsprepo.s3.amazonaws.com. >>>> >>>> When first attempting to log in, after entering the username, LDM seems >>>> to crash, and restart. The second attempt to login works fine. If it >>>> doesn't crash on the first attempt, the X session crashes very shortly >>>> afterwards, usually when trying to launch an application. After the >>>> initial weirdness, everything seems to settle down and work. >>>> >>>> This behavior happens on both the physical thin clients AND a virtual >>>> client. >>>> >>>> Has anyone seen this problem and know what might be causing it? >>>> >>>> Thanks. >>>> >>>> Gary. >>>> >>>> _______________________________________________ >>>> K12OSN mailing list >>>> K12OSN at redhat.com >>>> https://www.redhat.com/mailman/listinfo/k12osn >>>> For more info see >>> >>> _______________________________________________ >>> K12OSN mailing list >>> K12OSN at redhat.com >>> https://www.redhat.com/mailman/listinfo/k12osn >>> For more info see >>> >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From gnutbeam at gmail.com Tue Oct 15 17:35:33 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Tue, 15 Oct 2013 12:35:33 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C6A28.1020005@enslaver.com> References: <525C07A6.1050802@gmail.com> <525C10ED.1020609@infocentrality.co.uk> <525C1599.6070501@gmail.com> <525C6A28.1020005@enslaver.com> Message-ID: <525D7CE5.5060903@gmail.com> I shall do that. Thanks. On 10/14/2013 05:03 PM, Joshua Trimm wrote: > The EPEL repo is the current most stable one, I have had some issues > with the server that hosts my development code. It had to do a lost file > recovery so i'm thinking a beta version got into the repo. I'll fix when > I can, but for now use the rpms from EPEL. > > On 10/14/13 11:02 AM, Gary Nutbeam wrote: >> It would be a lot of work for me to move to Debian, because of >> applications to be moved, tested on Debian, etc. Plus everything we do >> is CentOS and Fedora based. >> >> I can't shutdown or reboot the client either. I saw a hack on the list >> that I haven't tried yet to "fix" the shutdown/reboot problem. >> >> On 10/14/2013 10:42 AM, k12ltsp wrote: >>> Hi Gary, >>> >>> We have the same problem I'm afraid. >>> Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom >>> processors in the clients with at least 1GByte RAM. >>> Usually work reliably once logged in. >>> >>> Also cannot shutdown or reboot the client. Tried some suggestions from >>> the list, but they didn't help. >>> >>> Things seem to have got worse recently, and I don't have the skills to >>> try and fix it, we do IT support for small businesses and >>> web/database apps. >>> >>> Now trying Debian Wheezy with LTSP - just works, so looks like I shall >>> jump ship. >>> >>> Regards >>> Trevor >>> http://www.infocentrality.co.uk >>> >>> On 14/10/13 16:03, Gary Nutbeam wrote: >>>> I'm having stability problems with LDM. I'm using decent thin clients >>>> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB >>>> RAM etc.). >>>> >>>> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp >>>> repo at >>>> ltsprepo.s3.amazonaws.com. >>>> >>>> When first attempting to log in, after entering the username, LDM seems >>>> to crash, and restart. The second attempt to login works fine. If it >>>> doesn't crash on the first attempt, the X session crashes very shortly >>>> afterwards, usually when trying to launch an application. After the >>>> initial weirdness, everything seems to settle down and work. >>>> >>>> This behavior happens on both the physical thin clients AND a virtual >>>> client. >>>> >>>> Has anyone seen this problem and know what might be causing it? >>>> >>>> Thanks. >>>> >>>> Gary. >>>> >>>> _______________________________________________ >>>> K12OSN mailing list >>>> K12OSN at redhat.com >>>> https://www.redhat.com/mailman/listinfo/k12osn >>>> For more info see >>> >>> _______________________________________________ >>> K12OSN mailing list >>> K12OSN at redhat.com >>> https://www.redhat.com/mailman/listinfo/k12osn >>> For more info see >>> >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From Peter.Onion at btinternet.com Fri Oct 18 11:36:50 2013 From: Peter.Onion at btinternet.com (Peter Onion) Date: Fri, 18 Oct 2013 12:36:50 +0100 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525C1599.6070501@gmail.com> References: <525C07A6.1050802@gmail.com> <525C10ED.1020609@infocentrality.co.uk> <525C1599.6070501@gmail.com> Message-ID: <1382096210.2566.3.camel@ponion-VD010AA-ABU-p6126uk> On Mon, 2013-10-14 at 11:02 -0500, Gary Nutbeam wrote: > I can't shutdown or reboot the client either. I saw a hack on the list > that I haven't tried yet to "fix" the shutdown/reboot problem. I found there are issues with some of the scripts in /etc/init.d trying to stop the networking during shutdown, which is NOT a good idea when the root file system is mounted on NFS ! ISTR I added "exit 1" at the top of the "stop" sections in 3 or 4 files but I don't have access to a working example at the moment so I can't give you a list until next week. PeterO From radek at bursztynowski.waw.pl Fri Oct 18 14:23:57 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Fri, 18 Oct 2013 16:23:57 +0200 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <525D619C.2060901@gmail.com> References: <525C07A6.1050802@gmail.com> Message-ID: <1382106237.14548.16.camel@alpaga.bursztynowski.waw.pl> I tested it the once again. I can confirm that trying to log in that epel-6-i386 image installed 2 mounts ago crash on trying to log in. But the image installed few days ago using my parameters works fine. I copied this to another one LTSP server, and I have just finish the test of copied image. Works fine with no crashing on trying to log in. If you want to try my working image you can download it, both i386 and x86_64 versions: http://www.bursztynowski.pl/ftp/linux/LinuxTerminalServerProject/5/5.4/epel-6-thin_client_image/ I renamed chroot directory to epel-6-i386_base and epel-6-x86_64_base. Best regards, Radek --- > Thanks for the info. Unfortunately I tried this with US information > substituted and still have LDM crashing. I was running a Scientific > Linux client and it was working better. I'll see if I can rollback to > that, or maybe try the version out of the EPEL repo. > > On 10/14/2013 04:51 PM, Radek Bursztynowski wrote: > > Hello, > > > > I have the same problems. The problem with first attempting to log in I > > solved (I believe). This solution concerns i386 and x86_64 thin client > > image (epel6-i386 and epel-6-x86_64). > > > > I added to /opt/ltsp/chroot/etc/sysconfig three files which I couldn't > > find after ltsp-build-client script execution: > > > > > > (Polish parameters) > > clock > > ZONE="Warsaw/Europe" > > > > i18n > > LANG="pl_PL.UTF-8" > > > > keyboard > > KEYTABLE="pl2" > > MODEL="pc105" > > LAYOUT="pl" > > KEYBOARDTYPE="pc" > > > > and my /opt/ltsp/i386/etc/ltsp_chroot is not empty but includes > > > > LTSP_CHROOT=/opt/ltsp/i386 line > > > > and /opt/ltsp/x86_64/etc/ltsp_chroot includes > > > > LTSP_CHROOT=/opt/ltsp/x86_64 line. > > > > Now LDM doesn't reload and works fine. > > > > I am not sure that this the best solution, but it helped me. > > > > Thin client still doesn't reboot or shutdown. > > > > I tried Debian LTSP too, but I retrieved. Finally I moved Debian thin > > client image to LTSP on CentOS 6.4 and I can use it, but I prefer epel-6 > > images. In my opinion the most stable thin client image is Scientific > > Linux 6.1 (ltsp-server 5.2) and I recommend it. > > > > Best regards, > > Radek > > > > --- > >> It would be a lot of work for me to move to Debian, because of > >> applications to be moved, tested on Debian, etc. Plus everything we do > >> is CentOS and Fedora based. > >> > >> I can't shutdown or reboot the client either. I saw a hack on the list > >> that I haven't tried yet to "fix" the shutdown/reboot problem. > >> > >> On 10/14/2013 10:42 AM, k12ltsp wrote: > >>> Hi Gary, > >>> > >>> We have the same problem I'm afraid. > >>> Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom > >>> processors in the clients with at least 1GByte RAM. > >>> Usually work reliably once logged in. > >>> > >>> Also cannot shutdown or reboot the client. Tried some suggestions from > >>> the list, but they didn't help. > >>> > >>> Things seem to have got worse recently, and I don't have the skills to > >>> try and fix it, we do IT support for small businesses and web/database apps. > >>> > >>> Now trying Debian Wheezy with LTSP - just works, so looks like I shall > >>> jump ship. > >>> > >>> Regards > >>> Trevor > >>> http://www.infocentrality.co.uk > >>> > >>> On 14/10/13 16:03, Gary Nutbeam wrote: > >>>> I'm having stability problems with LDM. I'm using decent thin clients > >>>> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB > >>>> RAM etc.). > >>>> > >>>> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at > >>>> ltsprepo.s3.amazonaws.com. > >>>> > >>>> When first attempting to log in, after entering the username, LDM seems > >>>> to crash, and restart. The second attempt to login works fine. If it > >>>> doesn't crash on the first attempt, the X session crashes very shortly > >>>> afterwards, usually when trying to launch an application. After the > >>>> initial weirdness, everything seems to settle down and work. > >>>> > >>>> This behavior happens on both the physical thin clients AND a virtual > >>>> client. > >>>> > >>>> Has anyone seen this problem and know what might be causing it? > >>>> > >>>> Thanks. > >>>> > >>>> Gary. > >>>> > >>>> _______________________________________________ > >>>> K12OSN mailing list > >>>> K12OSN at redhat.com > >>>> https://www.redhat.com/mailman/listinfo/k12osn > >>>> For more info see > >>> > >>> _______________________________________________ > >>> K12OSN mailing list > >>> K12OSN at redhat.com > >>> https://www.redhat.com/mailman/listinfo/k12osn > >>> For more info see > >>> > >> > >> _______________________________________________ > >> K12OSN mailing list > >> K12OSN at redhat.com > >> https://www.redhat.com/mailman/listinfo/k12osn > >> For more info see > > > > > > _______________________________________________ > > K12OSN mailing list > > K12OSN at redhat.com > > https://www.redhat.com/mailman/listinfo/k12osn > > For more info see > > From gnutbeam at gmail.com Fri Oct 18 15:57:09 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Fri, 18 Oct 2013 10:57:09 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <1382096210.2566.3.camel@ponion-VD010AA-ABU-p6126uk> References: <525C07A6.1050802@gmail.com> <525C10ED.1020609@infocentrality.co.uk> <525C1599.6070501@gmail.com> <1382096210.2566.3.camel@ponion-VD010AA-ABU-p6126uk> Message-ID: <52615A55.7030407@gmail.com> That would be much appreciated. On 10/18/2013 06:36 AM, Peter Onion wrote: > On Mon, 2013-10-14 at 11:02 -0500, Gary Nutbeam wrote: > >> I can't shutdown or reboot the client either. I saw a hack on the list >> that I haven't tried yet to "fix" the shutdown/reboot problem. > > I found there are issues with some of the scripts in /etc/init.d trying > to stop the networking during shutdown, which is NOT a good idea when > the root file system is mounted on NFS ! > > ISTR I added "exit 1" at the top of the "stop" sections in 3 or 4 files > but I don't have access to a working example at the moment so I can't > give you a list until next week. > > PeterO > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > From gnutbeam at gmail.com Fri Oct 18 15:57:24 2013 From: gnutbeam at gmail.com (Gary Nutbeam) Date: Fri, 18 Oct 2013 10:57:24 -0500 Subject: [K12OSN] LDM crashing on trying to log in. In-Reply-To: <1382106237.14548.16.camel@alpaga.bursztynowski.waw.pl> References: <525C07A6.1050802@gmail.com> <1382106237.14548.16.camel@alpaga.bursztynowski.waw.pl> Message-ID: <52615A64.1000103@gmail.com> Thanks. I'm going to download the image and have a look at it. On 10/18/2013 09:23 AM, Radek Bursztynowski wrote: > I tested it the once again. I can confirm that trying to log in that > epel-6-i386 image installed 2 mounts ago crash on trying to log in. > > But the image installed few days ago using my parameters works fine. I > copied this to another one LTSP server, and I have just finish the test > of copied image. Works fine with no crashing on trying to log in. > > If you want to try my working image you can download it, both i386 and > x86_64 versions: > http://www.bursztynowski.pl/ftp/linux/LinuxTerminalServerProject/5/5.4/epel-6-thin_client_image/ > > I renamed chroot directory to epel-6-i386_base and epel-6-x86_64_base. > > Best regards, > Radek > > --- >> Thanks for the info. Unfortunately I tried this with US information >> substituted and still have LDM crashing. I was running a Scientific >> Linux client and it was working better. I'll see if I can rollback to >> that, or maybe try the version out of the EPEL repo. >> >> On 10/14/2013 04:51 PM, Radek Bursztynowski wrote: >>> Hello, >>> >>> I have the same problems. The problem with first attempting to log in I >>> solved (I believe). This solution concerns i386 and x86_64 thin client >>> image (epel6-i386 and epel-6-x86_64). >>> >>> I added to /opt/ltsp/chroot/etc/sysconfig three files which I couldn't >>> find after ltsp-build-client script execution: >>> >>> >>> (Polish parameters) >>> clock >>> ZONE="Warsaw/Europe" >>> >>> i18n >>> LANG="pl_PL.UTF-8" >>> >>> keyboard >>> KEYTABLE="pl2" >>> MODEL="pc105" >>> LAYOUT="pl" >>> KEYBOARDTYPE="pc" >>> >>> and my /opt/ltsp/i386/etc/ltsp_chroot is not empty but includes >>> >>> LTSP_CHROOT=/opt/ltsp/i386 line >>> >>> and /opt/ltsp/x86_64/etc/ltsp_chroot includes >>> >>> LTSP_CHROOT=/opt/ltsp/x86_64 line. >>> >>> Now LDM doesn't reload and works fine. >>> >>> I am not sure that this the best solution, but it helped me. >>> >>> Thin client still doesn't reboot or shutdown. >>> >>> I tried Debian LTSP too, but I retrieved. Finally I moved Debian thin >>> client image to LTSP on CentOS 6.4 and I can use it, but I prefer epel-6 >>> images. In my opinion the most stable thin client image is Scientific >>> Linux 6.1 (ltsp-server 5.2) and I recommend it. >>> >>> Best regards, >>> Radek >>> >>> --- >>>> It would be a lot of work for me to move to Debian, because of >>>> applications to be moved, tested on Debian, etc. Plus everything we do >>>> is CentOS and Fedora based. >>>> >>>> I can't shutdown or reboot the client either. I saw a hack on the list >>>> that I haven't tried yet to "fix" the shutdown/reboot problem. >>>> >>>> On 10/14/2013 10:42 AM, k12ltsp wrote: >>>>> Hi Gary, >>>>> >>>>> We have the same problem I'm afraid. >>>>> Using ltsp-server-5.4.5-24.elg.x86_64 but with 32 bit clients. Atom >>>>> processors in the clients with at least 1GByte RAM. >>>>> Usually work reliably once logged in. >>>>> >>>>> Also cannot shutdown or reboot the client. Tried some suggestions from >>>>> the list, but they didn't help. >>>>> >>>>> Things seem to have got worse recently, and I don't have the skills to >>>>> try and fix it, we do IT support for small businesses and web/database apps. >>>>> >>>>> Now trying Debian Wheezy with LTSP - just works, so looks like I shall >>>>> jump ship. >>>>> >>>>> Regards >>>>> Trevor >>>>> http://www.infocentrality.co.uk >>>>> >>>>> On 14/10/13 16:03, Gary Nutbeam wrote: >>>>>> I'm having stability problems with LDM. I'm using decent thin clients >>>>>> now (1700 model from disklessworkstations.com, hyperthreading atom, 2GB >>>>>> RAM etc.). >>>>>> >>>>>> I'm using ltsp-server 5.4.5-24 on CentOS 6.4 64bit from the ltsp repo at >>>>>> ltsprepo.s3.amazonaws.com. >>>>>> >>>>>> When first attempting to log in, after entering the username, LDM seems >>>>>> to crash, and restart. The second attempt to login works fine. If it >>>>>> doesn't crash on the first attempt, the X session crashes very shortly >>>>>> afterwards, usually when trying to launch an application. After the >>>>>> initial weirdness, everything seems to settle down and work. >>>>>> >>>>>> This behavior happens on both the physical thin clients AND a virtual >>>>>> client. >>>>>> >>>>>> Has anyone seen this problem and know what might be causing it? >>>>>> >>>>>> Thanks. >>>>>> >>>>>> Gary. >>>>>> >>>>>> _______________________________________________ >>>>>> K12OSN mailing list >>>>>> K12OSN at redhat.com >>>>>> https://www.redhat.com/mailman/listinfo/k12osn >>>>>> For more info see >>>>> >>>>> _______________________________________________ >>>>> K12OSN mailing list >>>>> K12OSN at redhat.com >>>>> https://www.redhat.com/mailman/listinfo/k12osn >>>>> For more info see >>>>> >>>> >>>> _______________________________________________ >>>> K12OSN mailing list >>>> K12OSN at redhat.com >>>> https://www.redhat.com/mailman/listinfo/k12osn >>>> For more info see >>> >>> >>> _______________________________________________ >>> K12OSN mailing list >>> K12OSN at redhat.com >>> https://www.redhat.com/mailman/listinfo/k12osn >>> For more info see >>> > >