From brcisna at eazylivin.net Sun Jun 2 23:03:59 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Sun, 02 Jun 2013 18:03:59 -0500 Subject: [K12OSN] client booting linux stalls Message-ID: <1370214239.18420.11.camel@server1.eazylivin.net> Hello All, New install of the latest 5.4.5 ltsp-server (32-bit)setup. >From the last iteration,,about 4 months ago,the install page documentation has changed along with the actual installation routine to a degree. After a little wrangling I am getting the vm_pxeclient to boot to were I see a "Booting Linux" and see a lot of nic activity on the vm nic,,,for about 60-90 seconds,then the nic activity stops. The client never ends up booting to try and start x for example. Very trivial but in the last k12linux install the tc bootup message appeared as "Booting K12Linux". I wonder if I got my client chroot image a half a bubble off?.. I see nothing in the system logs.I have disabled iptables all together. I have not tried an actual TC on this server yet,,ran out of time for the day. Just curious if anyone has done any builds of k12linux/ltsp-5.4.5 in the last 3-4 months? It appears maybe the maintainers for ltsp is actually taking over the k12linux site and upkeep? Take Care, Barry From brcisna at eazylivin.net Mon Jun 3 18:20:36 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Mon, 03 Jun 2013 13:20:36 -0500 Subject: [K12OSN] client booting linux stalls Message-ID: <1370283636.17451.13.camel@localhost> Hello All, Replying to my previous post. For completeness. The fix for the 'stuck' Booting Linux line was I did not have nfs service started at boot on the server and had to manually enter the /opt/ltsp dir in nfs/exports. After this clients will boot fine. Take Care, Barry From jvermeulen at cawdekempen.be Tue Jun 4 10:23:01 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Tue, 04 Jun 2013 12:23:01 +0200 Subject: [K12OSN] client booting linux stalls In-Reply-To: <1370283636.17451.13.camel@localhost> References: <1370283636.17451.13.camel@localhost> Message-ID: <51ADC005.3080702@cawdekempen.be> Dear All, this is my experience with the install : version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. installed with epel-repo. After starting nfs manualy like Barry and starting tftp manualy, I am able to boot a thinclient. But I'm facing these problems : *ltsp-server-tweaks hangs on " about to overwrite your firewall config" either with iptables on or off. Probably because of that, laptops and workstations that are on the lan cannot reach the internet. This is my main concern. Setting up nat manualy did not help. this is /etc/sysconfig/iptables : # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *nat :PREROUTING ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o eth+ -j MASQUERADE -A POSTROUTING -o em2 -j MASQUERADE COMMIT *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i eth+ -j ACCEPT -A INPUT -i em2 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT -A FORWARD -p icmp -j ACCEPT -A FORWARD -i lo -j ACCEPT -A FORWARD -i eth+ -j ACCEPT -A FORWARD -i em2 -j ACCEPT -A FORWARD -o eth+ -j ACCEPT -A FORWARD -o em2 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT *ltsp-server-initialize gives me a lot of EM. But the thinclient boots, so maybe that's not a problem. *when booting the thinclient, I get an EM : unsupported device : processor centaurhauls The thinclient is an HP hstnc-004 that I used on 3 different thinclient systems in the past 3 years. It would be a real problem if it doesn't work with this image. *when booted, I am able to log in, and adapt language and other settings in lts.conf. But I can't get rid of the green glare that is over the screen. Could be the Acer monitor, but it's fine when attached to other devices. Any input on these issues would be greatly appreciated. greetings, J. Op 03-06-13 20:20, Barry Cisna schreef: > Hello All, > > Replying to my previous post. > For completeness. > > The fix for the 'stuck' Booting Linux line was I did not have nfs > service started at boot on the server and had to manually enter > the /opt/ltsp dir in nfs/exports. > After this clients will boot fine. > > Take Care, > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From enslaver at enslaver.com Tue Jun 4 18:46:23 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Tue, 04 Jun 2013 13:46:23 -0500 Subject: [K12OSN] client booting linux stalls In-Reply-To: <51ADC005.3080702@cawdekempen.be> References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> Message-ID: <51AE35FF.3050006@enslaver.com> Johan, I have 5.4.5-21 being pushed to the repo's today which should fix the scripts to accept an interface regardless of its name. The reason NFS needs to be started manually is due to the RPM not knowing which interface you will be using for the LTSP network. This must be defined in /etc/ltsp/ltsp-server.conf before ltsp-server-tweaks and ltsp-server-initialize are run. On 6/4/13 5:23 AM, Johan Vermeulen wrote: > Dear All, > > this is my experience with the install : > > version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. > installed with epel-repo. > > After starting nfs manualy like Barry and starting tftp manualy, I am > able to boot a thinclient. > > But I'm facing these problems : > > *ltsp-server-tweaks hangs on " about to overwrite your firewall > config" either with iptables on or off. > Probably because of that, laptops and workstations that are on the lan > cannot reach the internet. This is my main concern. > Setting up nat manualy did not help. > > this is /etc/sysconfig/iptables : > > # Firewall configuration written by system-config-firewall > # Manual customization of this file is not recommended. > *nat > :PREROUTING ACCEPT [0:0] > :OUTPUT ACCEPT [0:0] > :POSTROUTING ACCEPT [0:0] > -A POSTROUTING -o eth+ -j MASQUERADE > -A POSTROUTING -o em2 -j MASQUERADE > COMMIT > *filter > :INPUT ACCEPT [0:0] > :FORWARD ACCEPT [0:0] > :OUTPUT ACCEPT [0:0] > -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT > -A INPUT -p icmp -j ACCEPT > -A INPUT -i lo -j ACCEPT > -A INPUT -i eth+ -j ACCEPT > -A INPUT -i em2 -j ACCEPT > -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT > -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT > -A FORWARD -p icmp -j ACCEPT > -A FORWARD -i lo -j ACCEPT > -A FORWARD -i eth+ -j ACCEPT > -A FORWARD -i em2 -j ACCEPT > -A FORWARD -o eth+ -j ACCEPT > -A FORWARD -o em2 -j ACCEPT > -A INPUT -j REJECT --reject-with icmp-host-prohibited > -A FORWARD -j REJECT --reject-with icmp-host-prohibited > COMMIT > > *ltsp-server-initialize gives me a lot of EM. But the thinclient > boots, so maybe that's not a problem. > > *when booting the thinclient, I get an EM : unsupported device : > processor centaurhauls > The thinclient is an HP hstnc-004 that I used on 3 different > thinclient systems in the past 3 years. > It would be a real problem if it doesn't work with this image. > > *when booted, I am able to log in, and adapt language and other > settings in lts.conf. But I can't get rid of the green glare that is > over the > screen. > Could be the Acer monitor, but it's fine when attached to other devices. > > Any input on these issues would be greatly appreciated. > > greetings, J. > > > Op 03-06-13 20:20, Barry Cisna schreef: >> Hello All, >> >> Replying to my previous post. >> For completeness. >> >> The fix for the 'stuck' Booting Linux line was I did not have nfs >> service started at boot on the server and had to manually enter >> the /opt/ltsp dir in nfs/exports. >> After this clients will boot fine. >> >> Take Care, >> Barry >> >> >> _______________________________________________ >> 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 jvermeulen at cawdekempen.be Wed Jun 5 07:55:23 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Wed, 05 Jun 2013 09:55:23 +0200 Subject: [K12OSN] client booting linux stalls In-Reply-To: <51AE35FF.3050006@enslaver.com> References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> <51AE35FF.3050006@enslaver.com> Message-ID: <51AEEEEB.9060108@cawdekempen.be> hello Jushua, thanks for letting me know. *the routing problem was solved by editing the iptables manualy. * I did put "em2" in /etc/ltsp/ltsp-server.conf before running the scripts. * my original install was with epel, yesterday evening I updated with the other repo: [root at centoshofkwartier ~]# yum repolist Loaded plugins: fastestmirror, refresh-packagekit, security Loading mirror speeds from cached hostfile * base: distrib-coffee.ipsl.jussieu.fr * extras: mirror.ovh.net * ltsp: ltsprepo.s3.amazonaws.com * updates: distrib-coffee.ipsl.jussieu.fr repo id repo name status base CentOS-6 - Base 6381 extras CentOS-6 - Extras 12 ltsp LTSP - x86_64 60 but something went wrong with the update,because my version is still: [root at centoshofkwartier ~]# rpm -qa | grep ltsp ltsp-server-5.4.5-20.el6.x86_64 ltspfs-1.1-7.el6.x86_64 ltsp-release-5-9.el6.noarch * I then rebuilded with ltsp-build-client but the problem with the green glare stays. Everything 's on the screen, but there's this filter over it...... Maybe this can be solved by editing lts.conf..... greetings, J Op 04-06-13 20:46, Joshua Trimm schreef: > Johan, I have 5.4.5-21 being pushed to the repo's today which should > fix the scripts to accept an interface regardless of its name. > > The reason NFS needs to be started manually is due to the RPM not > knowing which interface you will be using for the LTSP network. This > must be defined in /etc/ltsp/ltsp-server.conf before > ltsp-server-tweaks and ltsp-server-initialize are run. > On 6/4/13 5:23 AM, Johan Vermeulen wrote: >> Dear All, >> >> this is my experience with the install : >> >> version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. >> installed with epel-repo. >> >> After starting nfs manualy like Barry and starting tftp manualy, I am >> able to boot a thinclient. >> >> But I'm facing these problems : >> >> *ltsp-server-tweaks hangs on " about to overwrite your firewall >> config" either with iptables on or off. >> Probably because of that, laptops and workstations that are on the >> lan cannot reach the internet. This is my main concern. >> Setting up nat manualy did not help. >> >> this is /etc/sysconfig/iptables : >> >> # Firewall configuration written by system-config-firewall >> # Manual customization of this file is not recommended. >> *nat >> :PREROUTING ACCEPT [0:0] >> :OUTPUT ACCEPT [0:0] >> :POSTROUTING ACCEPT [0:0] >> -A POSTROUTING -o eth+ -j MASQUERADE >> -A POSTROUTING -o em2 -j MASQUERADE >> COMMIT >> *filter >> :INPUT ACCEPT [0:0] >> :FORWARD ACCEPT [0:0] >> :OUTPUT ACCEPT [0:0] >> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT >> -A INPUT -p icmp -j ACCEPT >> -A INPUT -i lo -j ACCEPT >> -A INPUT -i eth+ -j ACCEPT >> -A INPUT -i em2 -j ACCEPT >> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT >> -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT >> -A FORWARD -p icmp -j ACCEPT >> -A FORWARD -i lo -j ACCEPT >> -A FORWARD -i eth+ -j ACCEPT >> -A FORWARD -i em2 -j ACCEPT >> -A FORWARD -o eth+ -j ACCEPT >> -A FORWARD -o em2 -j ACCEPT >> -A INPUT -j REJECT --reject-with icmp-host-prohibited >> -A FORWARD -j REJECT --reject-with icmp-host-prohibited >> COMMIT >> >> *ltsp-server-initialize gives me a lot of EM. But the thinclient >> boots, so maybe that's not a problem. >> >> *when booting the thinclient, I get an EM : unsupported device : >> processor centaurhauls >> The thinclient is an HP hstnc-004 that I used on 3 different >> thinclient systems in the past 3 years. >> It would be a real problem if it doesn't work with this image. >> >> *when booted, I am able to log in, and adapt language and other >> settings in lts.conf. But I can't get rid of the green glare that is >> over the >> screen. >> Could be the Acer monitor, but it's fine when attached to other devices. >> >> Any input on these issues would be greatly appreciated. >> >> greetings, J. >> >> >> Op 03-06-13 20:20, Barry Cisna schreef: >>> Hello All, >>> >>> Replying to my previous post. >>> For completeness. >>> >>> The fix for the 'stuck' Booting Linux line was I did not have nfs >>> service started at boot on the server and had to manually enter >>> the /opt/ltsp dir in nfs/exports. >>> After this clients will boot fine. >>> >>> Take Care, >>> Barry >>> >>> >>> _______________________________________________ >>> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvermeulen at cawdekempen.be Wed Jun 5 19:43:29 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Wed, 05 Jun 2013 21:43:29 +0200 Subject: [K12OSN] client booting linux stalls In-Reply-To: <51AEEEEB.9060108@cawdekempen.be> References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> <51AE35FF.3050006@enslaver.com> <51AEEEEB.9060108@cawdekempen.be> Message-ID: <51AF94E1.6030104@cawdekempen.be> btw, is the previous version ( on http://mplug.org/~k12linux/rpm ) still accessible somehow? Just in case...... greetings, J. Op 05-06-13 09:55, Johan Vermeulen schreef: > hello Jushua, > > thanks for letting me know. > > *the routing problem was solved by editing the iptables manualy. > > * I did put "em2" in /etc/ltsp/ltsp-server.conf before running the > scripts. > > * my original install was with epel, yesterday evening I updated with > the other repo: > > [root at centoshofkwartier ~]# yum repolist > Loaded plugins: fastestmirror, refresh-packagekit, security > Loading mirror speeds from cached hostfile > * base: distrib-coffee.ipsl.jussieu.fr > * extras: mirror.ovh.net > * ltsp: ltsprepo.s3.amazonaws.com > * updates: distrib-coffee.ipsl.jussieu.fr > repo id repo > name status > base CentOS-6 - > Base 6381 > extras CentOS-6 - > Extras 12 > ltsp LTSP - > x86_64 60 > > > but something went wrong with the update,because my version is still: > > [root at centoshofkwartier ~]# rpm -qa | grep ltsp > ltsp-server-5.4.5-20.el6.x86_64 > ltspfs-1.1-7.el6.x86_64 > ltsp-release-5-9.el6.noarch > > * I then rebuilded with ltsp-build-client > > but the problem with the green glare stays. > Everything 's on the screen, but there's this filter over it...... > > Maybe this can be solved by editing lts.conf..... > > greetings, J > > > > > Op 04-06-13 20:46, Joshua Trimm schreef: >> Johan, I have 5.4.5-21 being pushed to the repo's today which should >> fix the scripts to accept an interface regardless of its name. >> >> The reason NFS needs to be started manually is due to the RPM not >> knowing which interface you will be using for the LTSP network. This >> must be defined in /etc/ltsp/ltsp-server.conf before >> ltsp-server-tweaks and ltsp-server-initialize are run. >> On 6/4/13 5:23 AM, Johan Vermeulen wrote: >>> Dear All, >>> >>> this is my experience with the install : >>> >>> version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. >>> installed with epel-repo. >>> >>> After starting nfs manualy like Barry and starting tftp manualy, I >>> am able to boot a thinclient. >>> >>> But I'm facing these problems : >>> >>> *ltsp-server-tweaks hangs on " about to overwrite your firewall >>> config" either with iptables on or off. >>> Probably because of that, laptops and workstations that are on the >>> lan cannot reach the internet. This is my main concern. >>> Setting up nat manualy did not help. >>> >>> this is /etc/sysconfig/iptables : >>> >>> # Firewall configuration written by system-config-firewall >>> # Manual customization of this file is not recommended. >>> *nat >>> :PREROUTING ACCEPT [0:0] >>> :OUTPUT ACCEPT [0:0] >>> :POSTROUTING ACCEPT [0:0] >>> -A POSTROUTING -o eth+ -j MASQUERADE >>> -A POSTROUTING -o em2 -j MASQUERADE >>> COMMIT >>> *filter >>> :INPUT ACCEPT [0:0] >>> :FORWARD ACCEPT [0:0] >>> :OUTPUT ACCEPT [0:0] >>> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT >>> -A INPUT -p icmp -j ACCEPT >>> -A INPUT -i lo -j ACCEPT >>> -A INPUT -i eth+ -j ACCEPT >>> -A INPUT -i em2 -j ACCEPT >>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT >>> -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT >>> -A FORWARD -p icmp -j ACCEPT >>> -A FORWARD -i lo -j ACCEPT >>> -A FORWARD -i eth+ -j ACCEPT >>> -A FORWARD -i em2 -j ACCEPT >>> -A FORWARD -o eth+ -j ACCEPT >>> -A FORWARD -o em2 -j ACCEPT >>> -A INPUT -j REJECT --reject-with icmp-host-prohibited >>> -A FORWARD -j REJECT --reject-with icmp-host-prohibited >>> COMMIT >>> >>> *ltsp-server-initialize gives me a lot of EM. But the thinclient >>> boots, so maybe that's not a problem. >>> >>> *when booting the thinclient, I get an EM : unsupported device : >>> processor centaurhauls >>> The thinclient is an HP hstnc-004 that I used on 3 different >>> thinclient systems in the past 3 years. >>> It would be a real problem if it doesn't work with this image. >>> >>> *when booted, I am able to log in, and adapt language and other >>> settings in lts.conf. But I can't get rid of the green glare that is >>> over the >>> screen. >>> Could be the Acer monitor, but it's fine when attached to other >>> devices. >>> >>> Any input on these issues would be greatly appreciated. >>> >>> greetings, J. >>> >>> >>> Op 03-06-13 20:20, Barry Cisna schreef: >>>> Hello All, >>>> >>>> Replying to my previous post. >>>> For completeness. >>>> >>>> The fix for the 'stuck' Booting Linux line was I did not have nfs >>>> service started at boot on the server and had to manually enter >>>> the /opt/ltsp dir in nfs/exports. >>>> After this clients will boot fine. >>>> >>>> Take Care, >>>> Barry >>>> >>>> >>>> _______________________________________________ >>>> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From enslaver at enslaver.com Wed Jun 5 22:36:57 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Wed, 05 Jun 2013 17:36:57 -0500 Subject: [K12OSN] client booting linux stalls In-Reply-To: <51AEEEEB.9060108@cawdekempen.be> References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> <51AE35FF.3050006@enslaver.com> <51AEEEEB.9060108@cawdekempen.be> Message-ID: <51AFBD89.9010504@enslaver.com> An HTML attachment was scrubbed... URL: From jvermeulen at cawdekempen.be Fri Jun 7 09:20:14 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Fri, 07 Jun 2013 11:20:14 +0200 Subject: [K12OSN] client booting linux stalls In-Reply-To: <51AFBD89.9010504@enslaver.com> References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> <51AE35FF.3050006@enslaver.com> <51AEEEEB.9060108@cawdekempen.be> <51AFBD89.9010504@enslaver.com> Message-ID: <51B1A5CE.1070102@cawdekempen.be> hallo Joshua, thanks for getting back to me. * I just ran #yum clean all && yum update and that worked; ltsp-server-5.4.5-21.el6.x86_64 ltspfs-1.1-7.el6.x86_64 ltsp-release-5-9.el6.noarch * I then did : #mv /opt/ltsp /opt/ltsp.old #ltsp-build-client # ltsp-update-image Your system seems to be using NFS to serve LTSP chroots. If you're absolutely certain you want to switch to NBD, run: /usr/sbin/ltsp-update-image --config-nbd # ltsp-update-kernels Updating /var/lib/tftpboot directories for chroot: i386 Skipping invalid chroot: mock * I then booted the hp thinclient: same green screen. I will try to send you a screenshot of that. I checked the hardware of this hp thinclient: it has a Via Eden processor 1000Mhz, Googling the " unsupported processor centaurhauls" message I find this : /nybody know the reason RedHat decided not to support the />>>/ VIA Eden Processor?/ / If you take a look on google for "CentaurHauls i686" you will see that />/this CPU/chipset SAYS it fully supports i686 but it really does not. />/All of EL6 is i686 and not i586 (which CentaurHauls really fully supports)./ So this suggests that Centos has an issue with this thinclient There's also this site : https://access.redhat.com/site/solutions/388693 that I don't have full access to. But then I don't understand why so far I had no issues with k12Linux on Centos????? * I then put together a new thinclient, with motherbord Gibabyte GA-c847n, intel Celeron processor. When booting this, i also see some EM, but K12Linux boots fine, and... There's no green screen. It just works So this fully suggests that the issue is the HP t545 thinclient. This is a showstopper for me, because this is our mainline thinclient. Thanks for any advise on this issue. Greetings, J. Op 06-06-13 00:36, Joshua Trimm schreef: > Johan, Try first cleaning your cache by doing a 'yum clean all' then > 'yum update' and let me know if that works for you. > > The green glare issue i'm unfamiliar with, could you take a screenshot > and post a link to it directly to my email? > Thanks, > > On 6/5/13 2:55 AM, Johan Vermeulen wrote: >> hello Jushua, >> >> thanks for letting me know. >> >> *the routing problem was solved by editing the iptables manualy. >> >> * I did put "em2" in /etc/ltsp/ltsp-server.conf before running the >> scripts. >> >> * my original install was with epel, yesterday evening I updated with >> the other repo: >> >> [root at centoshofkwartier ~]# yum repolist >> Loaded plugins: fastestmirror, refresh-packagekit, security >> Loading mirror speeds from cached hostfile >> * base: distrib-coffee.ipsl.jussieu.fr >> * extras: mirror.ovh.net >> * ltsp: ltsprepo.s3.amazonaws.com >> * updates: distrib-coffee.ipsl.jussieu.fr >> repo id repo >> name status >> base CentOS-6 - >> Base 6381 >> extras CentOS-6 - >> Extras 12 >> ltsp LTSP - >> x86_64 60 >> >> >> but something went wrong with the update,because my version is still: >> >> [root at centoshofkwartier ~]# rpm -qa | grep ltsp >> ltsp-server-5.4.5-20.el6.x86_64 >> ltspfs-1.1-7.el6.x86_64 >> ltsp-release-5-9.el6.noarch >> >> * I then rebuilded with ltsp-build-client >> >> but the problem with the green glare stays. >> Everything 's on the screen, but there's this filter over it...... >> >> Maybe this can be solved by editing lts.conf..... >> >> greetings, J >> >> >> >> >> Op 04-06-13 20:46, Joshua Trimm schreef: >>> Johan, I have 5.4.5-21 being pushed to the repo's today which should >>> fix the scripts to accept an interface regardless of its name. >>> >>> The reason NFS needs to be started manually is due to the RPM not >>> knowing which interface you will be using for the LTSP network. This >>> must be defined in /etc/ltsp/ltsp-server.conf before >>> ltsp-server-tweaks and ltsp-server-initialize are run. >>> On 6/4/13 5:23 AM, Johan Vermeulen wrote: >>>> Dear All, >>>> >>>> this is my experience with the install : >>>> >>>> version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. >>>> installed with epel-repo. >>>> >>>> After starting nfs manualy like Barry and starting tftp manualy, I >>>> am able to boot a thinclient. >>>> >>>> But I'm facing these problems : >>>> >>>> *ltsp-server-tweaks hangs on " about to overwrite your firewall >>>> config" either with iptables on or off. >>>> Probably because of that, laptops and workstations that are on the >>>> lan cannot reach the internet. This is my main concern. >>>> Setting up nat manualy did not help. >>>> >>>> this is /etc/sysconfig/iptables : >>>> >>>> # Firewall configuration written by system-config-firewall >>>> # Manual customization of this file is not recommended. >>>> *nat >>>> :PREROUTING ACCEPT [0:0] >>>> :OUTPUT ACCEPT [0:0] >>>> :POSTROUTING ACCEPT [0:0] >>>> -A POSTROUTING -o eth+ -j MASQUERADE >>>> -A POSTROUTING -o em2 -j MASQUERADE >>>> COMMIT >>>> *filter >>>> :INPUT ACCEPT [0:0] >>>> :FORWARD ACCEPT [0:0] >>>> :OUTPUT ACCEPT [0:0] >>>> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT >>>> -A INPUT -p icmp -j ACCEPT >>>> -A INPUT -i lo -j ACCEPT >>>> -A INPUT -i eth+ -j ACCEPT >>>> -A INPUT -i em2 -j ACCEPT >>>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT >>>> -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT >>>> -A FORWARD -p icmp -j ACCEPT >>>> -A FORWARD -i lo -j ACCEPT >>>> -A FORWARD -i eth+ -j ACCEPT >>>> -A FORWARD -i em2 -j ACCEPT >>>> -A FORWARD -o eth+ -j ACCEPT >>>> -A FORWARD -o em2 -j ACCEPT >>>> -A INPUT -j REJECT --reject-with icmp-host-prohibited >>>> -A FORWARD -j REJECT --reject-with icmp-host-prohibited >>>> COMMIT >>>> >>>> *ltsp-server-initialize gives me a lot of EM. But the thinclient >>>> boots, so maybe that's not a problem. >>>> >>>> *when booting the thinclient, I get an EM : unsupported device : >>>> processor centaurhauls >>>> The thinclient is an HP hstnc-004 that I used on 3 different >>>> thinclient systems in the past 3 years. >>>> It would be a real problem if it doesn't work with this image. >>>> >>>> *when booted, I am able to log in, and adapt language and other >>>> settings in lts.conf. But I can't get rid of the green glare that >>>> is over the >>>> screen. >>>> Could be the Acer monitor, but it's fine when attached to other >>>> devices. >>>> >>>> Any input on these issues would be greatly appreciated. >>>> >>>> greetings, J. >>>> >>>> >>>> Op 03-06-13 20:20, Barry Cisna schreef: >>>>> Hello All, >>>>> >>>>> Replying to my previous post. >>>>> For completeness. >>>>> >>>>> The fix for the 'stuck' Booting Linux line was I did not have nfs >>>>> service started at boot on the server and had to manually enter >>>>> the /opt/ltsp dir in nfs/exports. >>>>> After this clients will boot fine. >>>>> >>>>> Take Care, >>>>> Barry >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim.kinney at gmail.com Fri Jun 7 11:52:54 2013 From: jim.kinney at gmail.com (Jim Kinney) Date: Fri, 7 Jun 2013 07:52:54 -0400 Subject: [K12OSN] client booting linux stalls In-Reply-To: <51B1A5CE.1070102@cawdekempen.be> References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> <51AE35FF.3050006@enslaver.com> <51AEEEEB.9060108@cawdekempen.be> <51AFBD89.9010504@enslaver.com> <51B1A5CE.1070102@cawdekempen.be> Message-ID: You'll need to rollback to an older kernel version for the TC or compile your own. RedHat dropped support for CPU styles from 15 years back and many SoC devices that are not ARM are still i586 command sets. On Jun 7, 2013 5:22 AM, "Johan Vermeulen" wrote: > hallo Joshua, > > thanks for getting back to me. > > * I just ran > > #yum clean all && yum update > > and that worked; > > ltsp-server-5.4.5-21.el6.x86_64 > ltspfs-1.1-7.el6.x86_64 > ltsp-release-5-9.el6.noarch > > * I then did : > > #mv /opt/ltsp /opt/ltsp.old > > #ltsp-build-client > > # ltsp-update-image > Your system seems to be using NFS to serve LTSP chroots. > If you're absolutely certain you want to switch to NBD, run: > /usr/sbin/ltsp-update-image --config-nbd > > # ltsp-update-kernels > Updating /var/lib/tftpboot directories for chroot: i386 > Skipping invalid chroot: mock > > * I then booted the hp thinclient: same green screen. > I will try to send you a screenshot of that. > I checked the hardware of this hp thinclient: > it has a Via Eden processor 1000Mhz, > > Googling the " unsupported processor centaurhauls" message I find this : > > *nybody know the reason RedHat decided not to support the*>>>* VIA Eden Processor?* > > * > If you take a look on google for "CentaurHauls i686" you will see that *>*this CPU/chipset SAYS it fully supports i686 but it really does not. > *>* All of EL6 is i686 and not i586 (which CentaurHauls really fully > supports).* > > So this suggests that Centos has an issue with this thinclient > There's also this site : > > https://access.redhat.com/site/solutions/388693 > > that I don't have full access to. > > But then I don't understand why so far I had no issues with k12Linux on > Centos????? > > * I then put together a new thinclient, with motherbord Gibabyte GA-c847n, > intel Celeron processor. > > When booting this, i also see some EM, but K12Linux boots fine, and... > > There's no green screen. It just works > > So this fully suggests that the issue is the HP t545 thinclient. > > This is a showstopper for me, because this is our mainline thinclient. > > Thanks for any advise on this issue. > > Greetings, J. > > > Op 06-06-13 00:36, Joshua Trimm schreef: > > Johan, Try first cleaning your cache by doing a 'yum clean all' then 'yum > update' and let me know if that works for you. > > The green glare issue i'm unfamiliar with, could you take a screenshot and > post a link to it directly to my email? > Thanks, > > On 6/5/13 2:55 AM, Johan Vermeulen wrote: > > hello Jushua, > > thanks for letting me know. > > *the routing problem was solved by editing the iptables manualy. > > * I did put "em2" in /etc/ltsp/ltsp-server.conf before running the scripts. > > * my original install was with epel, yesterday evening I updated with the > other repo: > > [root at centoshofkwartier ~]# yum repolist > Loaded plugins: fastestmirror, refresh-packagekit, security > Loading mirror speeds from cached hostfile > * base: distrib-coffee.ipsl.jussieu.fr > * extras: mirror.ovh.net > * ltsp: ltsprepo.s3.amazonaws.com > * updates: distrib-coffee.ipsl.jussieu.fr > repo id repo name > status > base CentOS-6 - Base > 6381 > extras CentOS-6 - > Extras 12 > ltsp LTSP - > x86_64 60 > > > but something went wrong with the update,because my version is still: > > [root at centoshofkwartier ~]# rpm -qa | grep ltsp > ltsp-server-5.4.5-20.el6.x86_64 > ltspfs-1.1-7.el6.x86_64 > ltsp-release-5-9.el6.noarch > > * I then rebuilded with ltsp-build-client > > but the problem with the green glare stays. > Everything 's on the screen, but there's this filter over it...... > > Maybe this can be solved by editing lts.conf..... > > greetings, J > > > > > Op 04-06-13 20:46, Joshua Trimm schreef: > > Johan, I have 5.4.5-21 being pushed to the repo's today which should fix > the scripts to accept an interface regardless of its name. > > The reason NFS needs to be started manually is due to the RPM not knowing > which interface you will be using for the LTSP network. This must be > defined in /etc/ltsp/ltsp-server.conf before ltsp-server-tweaks and > ltsp-server-initialize are run. > On 6/4/13 5:23 AM, Johan Vermeulen wrote: > > Dear All, > > this is my experience with the install : > > version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. > installed with epel-repo. > > After starting nfs manualy like Barry and starting tftp manualy, I am able > to boot a thinclient. > > But I'm facing these problems : > > *ltsp-server-tweaks hangs on " about to overwrite your firewall config" > either with iptables on or off. > Probably because of that, laptops and workstations that are on the lan > cannot reach the internet. This is my main concern. > Setting up nat manualy did not help. > > this is /etc/sysconfig/iptables : > > # Firewall configuration written by system-config-firewall > # Manual customization of this file is not recommended. > *nat > :PREROUTING ACCEPT [0:0] > :OUTPUT ACCEPT [0:0] > :POSTROUTING ACCEPT [0:0] > -A POSTROUTING -o eth+ -j MASQUERADE > -A POSTROUTING -o em2 -j MASQUERADE > COMMIT > *filter > :INPUT ACCEPT [0:0] > :FORWARD ACCEPT [0:0] > :OUTPUT ACCEPT [0:0] > -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT > -A INPUT -p icmp -j ACCEPT > -A INPUT -i lo -j ACCEPT > -A INPUT -i eth+ -j ACCEPT > -A INPUT -i em2 -j ACCEPT > -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT > -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT > -A FORWARD -p icmp -j ACCEPT > -A FORWARD -i lo -j ACCEPT > -A FORWARD -i eth+ -j ACCEPT > -A FORWARD -i em2 -j ACCEPT > -A FORWARD -o eth+ -j ACCEPT > -A FORWARD -o em2 -j ACCEPT > -A INPUT -j REJECT --reject-with icmp-host-prohibited > -A FORWARD -j REJECT --reject-with icmp-host-prohibited > COMMIT > > *ltsp-server-initialize gives me a lot of EM. But the thinclient boots, so > maybe that's not a problem. > > *when booting the thinclient, I get an EM : unsupported device : processor > centaurhauls > The thinclient is an HP hstnc-004 that I used on 3 different thinclient > systems in the past 3 years. > It would be a real problem if it doesn't work with this image. > > *when booted, I am able to log in, and adapt language and other settings > in lts.conf. But I can't get rid of the green glare that is over the > screen. > Could be the Acer monitor, but it's fine when attached to other devices. > > Any input on these issues would be greatly appreciated. > > greetings, J. > > > Op 03-06-13 20:20, Barry Cisna schreef: > > Hello All, > > Replying to my previous post. > For completeness. > > The fix for the 'stuck' Booting Linux line was I did not have nfs > service started at boot on the server and had to manually enter > the /opt/ltsp dir in nfs/exports. > After this clients will boot fine. > > Take Care, > Barry > > > _______________________________________________ > 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 listK12OSN at redhat.comhttps://www.redhat.com/mailman/listinfo/k12osn > For more info see > > > > > _______________________________________________ > K12OSN mailing listK12OSN at redhat.comhttps://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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvermeulen at cawdekempen.be Fri Jun 7 13:18:14 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Fri, 07 Jun 2013 15:18:14 +0200 Subject: [K12OSN] client booting linux stalls In-Reply-To: References: <1370283636.17451.13.camel@localhost> <51ADC005.3080702@cawdekempen.be> <51AE35FF.3050006@enslaver.com> <51AEEEEB.9060108@cawdekempen.be> <51AFBD89.9010504@enslaver.com> <51B1A5CE.1070102@cawdekempen.be> Message-ID: <51B1DD96.7090702@cawdekempen.be> hallo Jim, thanks for the advise. I just tested this, and by copying some files from a previous install, I can indeed get this to work without green screen. So it seems our thinclients are out of date. greetings, J. Op 07-06-13 13:52, Jim Kinney schreef: > > You'll need to rollback to an older kernel version for the TC or > compile your own. RedHat dropped support for CPU styles from 15 years > back and many SoC devices that are not ARM are still i586 command sets. > > On Jun 7, 2013 5:22 AM, "Johan Vermeulen" > wrote: > > hallo Joshua, > > thanks for getting back to me. > > * I just ran > > #yum clean all && yum update > > and that worked; > > ltsp-server-5.4.5-21.el6.x86_64 > ltspfs-1.1-7.el6.x86_64 > ltsp-release-5-9.el6.noarch > > * I then did : > > #mv /opt/ltsp /opt/ltsp.old > > #ltsp-build-client > > # ltsp-update-image > Your system seems to be using NFS to serve LTSP chroots. > If you're absolutely certain you want to switch to NBD, run: > /usr/sbin/ltsp-update-image --config-nbd > > # ltsp-update-kernels > Updating /var/lib/tftpboot directories for chroot: i386 > Skipping invalid chroot: mock > > * I then booted the hp thinclient: same green screen. > I will try to send you a screenshot of that. > I checked the hardware of this hp thinclient: > it has a Via Eden processor 1000Mhz, > > Googling the " unsupported processor centaurhauls" message I find > this : > > /nybody know the reason RedHat decided not to support the > />>>/ VIA Eden Processor?/ > > / > If you take a look on google for "CentaurHauls i686" you will see > that />/this CPU/chipset SAYS it fully supports i686 but it really > does not. />/All of EL6 is i686 and not i586 (which CentaurHauls > really fully supports)./ > > So this suggests that Centos has an issue with this thinclient > There's also this site : > > https://access.redhat.com/site/solutions/388693 > > that I don't have full access to. > > But then I don't understand why so far I had no issues with > k12Linux on Centos????? > > * I then put together a new thinclient, with motherbord Gibabyte > GA-c847n, intel Celeron processor. > > When booting this, i also see some EM, but K12Linux boots fine, and... > > There's no green screen. It just works > > So this fully suggests that the issue is the HP t545 thinclient. > > This is a showstopper for me, because this is our mainline thinclient. > > Thanks for any advise on this issue. > > Greetings, J. > > > Op 06-06-13 00:36, Joshua Trimm schreef: >> Johan, Try first cleaning your cache by doing a 'yum clean all' >> then 'yum update' and let me know if that works for you. >> >> The green glare issue i'm unfamiliar with, could you take a >> screenshot and post a link to it directly to my email? >> Thanks, >> >> On 6/5/13 2:55 AM, Johan Vermeulen wrote: >>> hello Jushua, >>> >>> thanks for letting me know. >>> >>> *the routing problem was solved by editing the iptables manualy. >>> >>> * I did put "em2" in /etc/ltsp/ltsp-server.conf before running >>> the scripts. >>> >>> * my original install was with epel, yesterday evening I updated >>> with the other repo: >>> >>> [root at centoshofkwartier ~]# yum repolist >>> Loaded plugins: fastestmirror, refresh-packagekit, security >>> Loading mirror speeds from cached hostfile >>> * base: distrib-coffee.ipsl.jussieu.fr >>> >>> * extras: mirror.ovh.net >>> * ltsp: ltsprepo.s3.amazonaws.com >>> >>> * updates: distrib-coffee.ipsl.jussieu.fr >>> >>> repo id repo >>> name status >>> base CentOS-6 - >>> Base 6381 >>> extras CentOS-6 - >>> Extras 12 >>> ltsp LTSP - >>> x86_64 60 >>> >>> >>> but something went wrong with the update,because my version is >>> still: >>> >>> [root at centoshofkwartier ~]# rpm -qa | grep ltsp >>> ltsp-server-5.4.5-20.el6.x86_64 >>> ltspfs-1.1-7.el6.x86_64 >>> ltsp-release-5-9.el6.noarch >>> >>> * I then rebuilded with ltsp-build-client >>> >>> but the problem with the green glare stays. >>> Everything 's on the screen, but there's this filter over it...... >>> >>> Maybe this can be solved by editing lts.conf..... >>> >>> greetings, J >>> >>> >>> >>> >>> Op 04-06-13 20:46, Joshua Trimm schreef: >>>> Johan, I have 5.4.5-21 being pushed to the repo's today which >>>> should fix the scripts to accept an interface regardless of its >>>> name. >>>> >>>> The reason NFS needs to be started manually is due to the RPM >>>> not knowing which interface you will be using for the LTSP >>>> network. This must be defined in /etc/ltsp/ltsp-server.conf >>>> before ltsp-server-tweaks and ltsp-server-initialize are run. >>>> On 6/4/13 5:23 AM, Johan Vermeulen wrote: >>>>> Dear All, >>>>> >>>>> this is my experience with the install : >>>>> >>>>> version is ltsp-server-5.4.5-20.el6.x86_64 on Centos6.4. >>>>> installed with epel-repo. >>>>> >>>>> After starting nfs manualy like Barry and starting tftp >>>>> manualy, I am able to boot a thinclient. >>>>> >>>>> But I'm facing these problems : >>>>> >>>>> *ltsp-server-tweaks hangs on " about to overwrite your >>>>> firewall config" either with iptables on or off. >>>>> Probably because of that, laptops and workstations that are on >>>>> the lan cannot reach the internet. This is my main concern. >>>>> Setting up nat manualy did not help. >>>>> >>>>> this is /etc/sysconfig/iptables : >>>>> >>>>> # Firewall configuration written by system-config-firewall >>>>> # Manual customization of this file is not recommended. >>>>> *nat >>>>> :PREROUTING ACCEPT [0:0] >>>>> :OUTPUT ACCEPT [0:0] >>>>> :POSTROUTING ACCEPT [0:0] >>>>> -A POSTROUTING -o eth+ -j MASQUERADE >>>>> -A POSTROUTING -o em2 -j MASQUERADE >>>>> COMMIT >>>>> *filter >>>>> :INPUT ACCEPT [0:0] >>>>> :FORWARD ACCEPT [0:0] >>>>> :OUTPUT ACCEPT [0:0] >>>>> -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT >>>>> -A INPUT -p icmp -j ACCEPT >>>>> -A INPUT -i lo -j ACCEPT >>>>> -A INPUT -i eth+ -j ACCEPT >>>>> -A INPUT -i em2 -j ACCEPT >>>>> -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT >>>>> -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT >>>>> -A FORWARD -p icmp -j ACCEPT >>>>> -A FORWARD -i lo -j ACCEPT >>>>> -A FORWARD -i eth+ -j ACCEPT >>>>> -A FORWARD -i em2 -j ACCEPT >>>>> -A FORWARD -o eth+ -j ACCEPT >>>>> -A FORWARD -o em2 -j ACCEPT >>>>> -A INPUT -j REJECT --reject-with icmp-host-prohibited >>>>> -A FORWARD -j REJECT --reject-with icmp-host-prohibited >>>>> COMMIT >>>>> >>>>> *ltsp-server-initialize gives me a lot of EM. But the >>>>> thinclient boots, so maybe that's not a problem. >>>>> >>>>> *when booting the thinclient, I get an EM : unsupported device >>>>> : processor centaurhauls >>>>> The thinclient is an HP hstnc-004 that I used on 3 different >>>>> thinclient systems in the past 3 years. >>>>> It would be a real problem if it doesn't work with this image. >>>>> >>>>> *when booted, I am able to log in, and adapt language and >>>>> other settings in lts.conf. But I can't get rid of the green >>>>> glare that is over the >>>>> screen. >>>>> Could be the Acer monitor, but it's fine when attached to >>>>> other devices. >>>>> >>>>> Any input on these issues would be greatly appreciated. >>>>> >>>>> greetings, J. >>>>> >>>>> >>>>> Op 03-06-13 20:20, Barry Cisna schreef: >>>>>> Hello All, >>>>>> >>>>>> Replying to my previous post. >>>>>> For completeness. >>>>>> >>>>>> The fix for the 'stuck' Booting Linux line was I did not have >>>>>> nfs >>>>>> service started at boot on the server and had to manually enter >>>>>> the /opt/ltsp dir in nfs/exports. >>>>>> After this clients will boot fine. >>>>>> >>>>>> Take Care, >>>>>> Barry >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >> >> >> >> _______________________________________________ >> 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From brcisna at eazylivin.net Tue Jun 11 19:45:50 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Tue, 11 Jun 2013 14:45:50 -0500 Subject: [K12OSN] yum repos in chroot Message-ID: <1370979950.13111.18.camel@server1.eazylivin.net> Hello All, ltsp-server-5.4.5 (latest ltsp iteration) Have an odd one. Have added the adobe, repoforge and rpmfusion repos to the client chroot via the usual chrooting process,,and used the rpm install for each. Looking in /opt/ltsp/i386/etc/yum.repos.d they are in fact there. They are both enabled and permissions look correct. When I try and add a package that either of these repos provide i always get "Nothing to do".message. If i try and add a package from the default repos that come with ltsp-server-x.x.x the add works as expected. So it is not a proxy hang up.I even disabled gpgcheck,,and that made no difference. It is as though the new repos are not being read? I tried running with the -v switch with yum and simply says 'not available'. The verbosity when yumming from the client chroot is very minimal ,looks much different than a conventional linux yum process for some reason. Of course have rebooted just to say i did do it. I done a Meld compare on server and client chroot repo.repo files and all are identical for completeness. This seems 'too simple'?...:) Anyone have this happen? Thanks, Barry From enslaver at enslaver.com Tue Jun 11 20:27:35 2013 From: enslaver at enslaver.com (Enslaver) Date: Tue, 11 Jun 2013 15:27:35 -0500 Subject: [K12OSN] yum repos in chroot In-Reply-To: <1370979950.13111.18.camel@server1.eazylivin.net> References: <1370979950.13111.18.camel@server1.eazylivin.net> Message-ID: Hello barry. The way mock sets up the yum.conf doesnt support the repos.d style. To fix this, over write the yum.conf in /etc with the one from /etc/yum inside the chroot On Jun 11, 2013 3:49 PM, "Barry R Cisna" wrote: > Hello All, > > ltsp-server-5.4.5 (latest ltsp iteration) > > Have an odd one. > Have added the adobe, repoforge and rpmfusion repos to the client chroot > via the usual chrooting process,,and used the rpm install for each. > Looking in /opt/ltsp/i386/etc/yum.repos.d they are in fact there. They > are both enabled and permissions look correct. > > When I try and add a package that either of these repos provide i always > get "Nothing to do".message. If i try and add a package from the default > repos that come with ltsp-server-x.x.x the add works as expected. So it > is not a proxy hang up.I even disabled gpgcheck,,and that made no > difference. It is as though the new repos are not being read? > > I tried running with the -v switch with yum and simply says 'not > available'. > The verbosity when yumming from the client chroot is very minimal ,looks > much different than a conventional linux yum process for some reason. > Of course have rebooted just to say i did do it. > I done a Meld compare on server and client chroot repo.repo files and > all are identical for completeness. > This seems 'too simple'?...:) > Anyone have this happen? > > Thanks, > Barry > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cisna-barry at wc235.k12.il.us Wed Jun 12 12:45:09 2013 From: cisna-barry at wc235.k12.il.us (Barry Cisna) Date: Wed, 12 Jun 2013 07:45:09 -0500 Subject: [K12OSN] yum repos in chroot Message-ID: <1371041110.17451.58.camel@localhost> Hello All, Copied yum.conf.rpmnew from chroot/ ,,to /opt/ltsp/i386/etc/yum,,, renamed to yum.conf ,,yum recogonizes added repos now. Thank You, Barry From brcisna at eazylivin.net Wed Jun 12 12:49:50 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Wed, 12 Jun 2013 07:49:50 -0500 Subject: [K12OSN] LocalApps Firefox settings gets erased Message-ID: <1371041390.17451.63.camel@localhost> Hello All, With the latest ltsp-server, ltsp-client (5.4.5-x) install when running Firefox as a localapp after setting homepage and add some bookmarks,,on close the settings are gone the next Firefox launch. This behaviour did not happen in last ltsp setup. Also previously when launching Firefox as a local app bookmarks for each user would be 'auto-imported' from their home dir initially. Barry From brcisna at eazylivin.net Wed Jun 12 12:55:21 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Wed, 12 Jun 2013 07:55:21 -0500 Subject: [K12OSN] client hangs at reboot network card shutdown Message-ID: <1371041721.17451.69.camel@localhost> Hello All, We have about 100 dell optiplex sx280 that runs under the tg3 driver as a TC. With ltsp-server 5.4.5-x when either shutting down or rebooting these TC's from login dialogue box,when 'shutting down eth0" on rebooting dialogue they will go no further to actually reboot. It seems I read some time back this to be a known problem,but I can not remember what the workaround was,and can not find this now. Thank You, Barry From enslaver at enslaver.com Wed Jun 12 21:17:25 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Wed, 12 Jun 2013 16:17:25 -0500 Subject: [K12OSN] client hangs at reboot network card shutdown In-Reply-To: <1371041721.17451.69.camel@localhost> References: <1371041721.17451.69.camel@localhost> Message-ID: <51B8E565.8050302@enslaver.com> Try disabling the 'network' service inside the chroot. The network settings are retrieved by the initram so i cant see why they would need to be shutdown by the operating system, I have not tested this so I'm unsure if this would cause other issues. Send feedback of the results of your findings. On 6/12/13 7:55 AM, Barry Cisna wrote: > Hello All, > > We have about 100 dell optiplex sx280 that runs under the tg3 driver as > a TC. > > With ltsp-server 5.4.5-x when either shutting down or rebooting these > TC's from login dialogue box,when 'shutting down eth0" on rebooting > dialogue they will go no further to actually reboot. > > It seems I read some time back this to be a known problem,but I can not > remember what the workaround was,and can not find this now. > > Thank You, > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From brcisna at eazylivin.net Thu Jun 13 14:17:37 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Thu, 13 Jun 2013 09:17:37 -0500 Subject: [K12OSN] client hangs at reboot network card shutdown Message-ID: <1371133057.17451.77.camel@localhost> Joshua, I disabled the network service from starting in the client / chroot. Rebooted server,,,rebooted client. After this config change the TC just shows the Centos splash screen and shows the "rebooting" in upper left of monitor,,,and no more activity on the ethernet wire. In other words the TC does not get as far as previously in the shutdown/reboot procedure. I tried this on three different TC's from Intel,,and Broadcom nic varieties,,,for completeness. Switched back to chkconfig network on,,in chroot,,and reboot goes all the way to 'shutting down eth0",,,and stops. Barry From cisna-barry at wc235.k12.il.us Thu Jun 13 14:31:12 2013 From: cisna-barry at wc235.k12.il.us (Barry Cisna) Date: Thu, 13 Jun 2013 09:31:12 -0500 Subject: [K12OSN] laptops never get display Message-ID: <1371133872.17451.83.camel@localhost> Hello All, ltsp-server-5.4.5-20.el6.i686 Have tried 5 laptops that does work with K12linux spin,,(about a year & half old install). None of these laptops ever get a display in this version of ltsp. I do not see any failing messages in the syslog in regards to x failing or such. Each laptop does get to "Booting Linux" and lots of nic activity for about two minutes after this and then no further. I can see the image initializing even the built in camera,and hard disk,,on each,,but no display. Barry From radek at bursztynowski.waw.pl Thu Jun 13 18:57:21 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 13 Jun 2013 20:57:21 +0200 Subject: [K12OSN] Problem with ltsp-build-client Message-ID: <1371149841.2721.23.camel@dupa> Hello All, I try to install new LTSP k12Linux but there is no positive result. The first I installed CentOS 6.4 x86_64. Next I followed http://wiki.ltsp.org/wiki/Category:Fedora. yum install ltsp-server finished with no any error. I executed ltsp-build-client. Installation has suspended with 26% gone. I repeated all with another server - the same situation. ltsp-build-client suspends with 26% gone. I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see anything interesting (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). What should I check or do to fix my problem? Best regards, Radek From radek at bursztynowski.waw.pl Thu Jun 13 21:10:55 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 13 Jun 2013 23:10:55 +0200 Subject: [K12OSN] I can't finish client instalation by ltsp-build-client Message-ID: <1371157855.29836.1.camel@alpaga.bursztynowski.waw.pl> Hello All, (I can't see my post on the list, so I repeat it). I try to install new LTSP k12Linux but there is no positive result. The first I installed CentOS 6.4 x86_64. Next I followed http://wiki.ltsp.org/wiki/Category:Fedora. yum install ltsp-server finished with no any error. I executed ltsp-build-client. Installation has suspended with 26% gone. I repeated all with another server - the same situation. ltsp-build-client suspends with 26% gone. I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see anything interesting (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). What should I check or do to fix my problem? Best regards, Radek From brcisna at eazylivin.net Mon Jun 17 17:20:04 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Mon, 17 Jun 2013 12:20:04 -0500 Subject: [K12OSN] FL_Teachertool on latest ltsp5 Message-ID: <1371489604.17451.90.camel@localhost> Hello All, Has anyone had any luck getting FL_TeacherTool-0.71 working on ltsp-server-5.4.5-21 ? Everything "looks right", for fl_teachertool to work although I can not get sshd to start in the client chroot with the server running sshd as well. I don't remember this happening in previous versions. Thank You, Barry From donais at telupton.com Tue Jun 18 03:53:43 2013 From: donais at telupton.com (Michel Donais) Date: Mon, 17 Jun 2013 23:53:43 -0400 Subject: [K12OSN] GUI login References: <1371157855.29836.1.camel@alpaga.bursztynowski.waw.pl> Message-ID: <46B8F2308D7F48EE9D1AEBB7555D1A0B@IBM5864489F0F4> Seekng a solution I have a Centos 5.8 server wich I was able to login in graphically with KDE on the server console. After installing LTSP-4.2 On the server console I'm stucked to login in character mode no more graphic. The thin clients have their login graphically in KDE I google a while and found nothing related. /etc inittab is at init level 5 So I'm looking for a solution. Do somebody experienced this sitation? --- Michel Donais ========== my /etc/inittab ============ id:5:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run gettys in standard runlevels 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 # Run xdm in runlevel 5 x:5:respawn:/etc/X11/prefdm -nodaemon From enslaver at enslaver.com Wed Jun 19 06:38:57 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Wed, 19 Jun 2013 01:38:57 -0500 Subject: [K12OSN] FL_Teachertool on latest ltsp5 In-Reply-To: <1371489604.17451.90.camel@localhost> References: <1371489604.17451.90.camel@localhost> Message-ID: <51C15201.8070906@enslaver.com> I haven't explored much into the realm of FL_teachertool, I have created some RPM's for epoptes which work pretty well, still minor bugs here and there but i'll be working those out soon enough. http://repo.inode0.com/repo/ltsp/rpm/el6/i686/ On 6/17/13 12:20 PM, Barry Cisna wrote: > Hello All, > > Has anyone had any luck getting FL_TeacherTool-0.71 working on > ltsp-server-5.4.5-21 ? > > Everything "looks right", for fl_teachertool to work although I can not > get sshd to start in the client chroot with the server running sshd as > well. I don't remember this happening in previous versions. > > Thank You, > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From radek at bursztynowski.waw.pl Tue Jun 18 14:29:14 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Tue, 18 Jun 2013 16:29:14 +0200 Subject: [K12OSN] I really need help - problem with LTSP installation Message-ID: <1371565754.23463.68.camel@advocat.bursztynowski.waw.pl> Hello, I still trying to install LTSP with no success (CenTO 6.4 x86_64, two NICKs). I use http://wiki.ltsp.org/wiki/Category:Fedora Tree first steps I made with no any problems: rpm --import http://ltsprepo.s3.amazonaws.com/rpm/RPM-GPG-KEY-ltsp rpm -Uvh http://ltsprepo.s3.amazonaws.com/rpm/el6/x86_64/ltsp-release-5-9.el6.noarch.rpm yum install ltsp-server Next step ltsp-build-client still achive 26% only and nothing more. So, I tried with: ltsp ?-release fedora-18-i386 ?-chroot fedora-18-i386 but I can see: mockbuild:x:1001:1001::/home/mockbuild:/bin/bash cat: /etc/mock/epel-5-i386.cfg.cfg: There is no such file or directory. I really don't know what happens. Is somebody could help me? Best reagars, Radek From burke at thealmquists.net Thu Jun 20 07:09:47 2013 From: burke at thealmquists.net (Burke Almquist) Date: Thu, 20 Jun 2013 02:09:47 -0500 Subject: [K12OSN] client hangs at reboot network card shutdown In-Reply-To: <1371133057.17451.77.camel@localhost> References: <1371133057.17451.77.camel@localhost> Message-ID: <2501E64F-4D5E-4D7D-B3F1-0ED32F22B860@thealmquists.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Usually this stems from issues with power management, I don't think the networking is the problem. You might check the power management APM/ACPI in the client's bios. You might need to have reboot=pci or noapci parameters passed to the client when it boots the kernel. On Jun 13, 2013, at 9:17 AM, Barry Cisna wrote: > Joshua, > > I disabled the network service from starting in the client / chroot. > Rebooted server,,,rebooted client. > > After this config change the TC just shows the Centos splash screen and > shows the "rebooting" in upper left of monitor,,,and no more activity on > the ethernet wire. > In other words the TC does not get as far as previously in the > shutdown/reboot procedure. > I tried this on three different TC's from Intel,,and Broadcom nic > varieties,,,for completeness. > Switched back to chkconfig network on,,in chroot,,and reboot goes all > the way to 'shutting down eth0",,,and stops. > > > Barry > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlHCqrsACgkQxWV7OPa/g5F1PQCfZ3SV5QQeN+qIsYochaPU9XpA dygAn1yw+XRaJh31+D7eABQd499kfJ2m =WuMU -----END PGP SIGNATURE----- From burke at thealmquists.net Thu Jun 20 07:16:09 2013 From: burke at thealmquists.net (Burke Almquist) Date: Thu, 20 Jun 2013 02:16:09 -0500 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <1371149841.2721.23.camel@dupa> References: <1371149841.2721.23.camel@dupa> Message-ID: <8F6D7FE8-026F-4FD8-885A-2E58E5E68190@thealmquists.net> You might need to clean up your yum cache. I know someone else here had that problem. On Jun 13, 2013, at 1:57 PM, Radek Bursztynowski wrote: > Hello All, > > I try to install new LTSP k12Linux but there is no positive result. > The first I installed CentOS 6.4 x86_64. Next I followed > http://wiki.ltsp.org/wiki/Category:Fedora. > > yum install ltsp-server finished with no any error. > I executed ltsp-build-client. Installation has suspended with 26% gone. > > I repeated all with another server - the same situation. > ltsp-build-client suspends with 26% gone. > > I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see > anything interesting > (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). > > What should I check or do to fix my problem? > > Best regards, > Radek > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From burke at thealmquists.net Thu Jun 20 07:18:29 2013 From: burke at thealmquists.net (Burke Almquist) Date: Thu, 20 Jun 2013 02:18:29 -0500 Subject: [K12OSN] GUI login In-Reply-To: <46B8F2308D7F48EE9D1AEBB7555D1A0B@IBM5864489F0F4> References: <1371157855.29836.1.camel@alpaga.bursztynowski.waw.pl> <46B8F2308D7F48EE9D1AEBB7555D1A0B@IBM5864489F0F4> Message-ID: <835040F2-69F6-4EC2-A18A-CF74C129DED5@thealmquists.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We really need some boot logs or console messages to know what is going on. On Jun 17, 2013, at 10:53 PM, Michel Donais wrote: > Seekng a solution > > I have a Centos 5.8 server wich I was able to login in graphically with KDE on the server console. > After installing LTSP-4.2 > On the server console I'm stucked to login in character mode no more graphic. > The thin clients have their login graphically in KDE > I google a while and found nothing related. > /etc inittab is at init level 5 > > So I'm looking for a solution. > > Do somebody experienced this sitation? > > --- > Michel Donais > > ========== my /etc/inittab ============ > id:5:initdefault: > > # System initialization. > si::sysinit:/etc/rc.d/rc.sysinit > > l0:0:wait:/etc/rc.d/rc 0 > l1:1:wait:/etc/rc.d/rc 1 > l2:2:wait:/etc/rc.d/rc 2 > l3:3:wait:/etc/rc.d/rc 3 > l4:4:wait:/etc/rc.d/rc 4 > l5:5:wait:/etc/rc.d/rc 5 > l6:6:wait:/etc/rc.d/rc 6 > > # Trap CTRL-ALT-DELETE > ca::ctrlaltdel:/sbin/shutdown -t3 -r now > > # When our UPS tells us power has failed, assume we have a few minutes > # of power left. Schedule a shutdown for 2 minutes from now. > # This does, of course, assume you have powerd installed and your > # UPS connected and working correctly. > pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" > > # If power was restored before the shutdown kicked in, cancel it. > pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" > > > # Run gettys in standard runlevels > 1:2345:respawn:/sbin/mingetty tty1 > 2:2345:respawn:/sbin/mingetty tty2 > 3:2345:respawn:/sbin/mingetty tty3 > 4:2345:respawn:/sbin/mingetty tty4 > 5:2345:respawn:/sbin/mingetty tty5 > 6:2345:respawn:/sbin/mingetty tty6 > > # Run xdm in runlevel 5 > x:5:respawn:/etc/X11/prefdm -nodaemon > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlHCrMUACgkQxWV7OPa/g5Ho7QCdGO2F1RqXcr+eDmKqGHvEQmjl MgYAnilMxrkMB7Xt3u0jjkUIjfw/6qmR =6sw+ -----END PGP SIGNATURE----- From radek at bursztynowski.waw.pl Thu Jun 20 07:52:53 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 09:52:53 +0200 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <8F6D7FE8-026F-4FD8-885A-2E58E5E68190@thealmquists.net> References: <1371149841.2721.23.camel@dupa> Message-ID: <1371714773.12669.34.camel@alpaga.bursztynowski.waw.pl> Thanks for help. It can't be yum cache problem. I repeated all procedure with 3 separated servers (each of them is new installation CentOS and K12) - every time I achieved 26% gone of ltsp-build-client. You mentioned that somebody else had that problem. I search the k12osn archives from March 2013 (new version of K12 was announced in March) and I didn?t find any post related to my problem. Perhaps on another discussion list. Which one? Best regards, Radek --- > You might need to clean up your yum cache. I know someone else here had that problem. > > On Jun 13, 2013, at 1:57 PM, Radek Bursztynowski wrote: > > > Hello All, > > > > I try to install new LTSP k12Linux but there is no positive result. > > The first I installed CentOS 6.4 x86_64. Next I followed > > http://wiki.ltsp.org/wiki/Category:Fedora. > > > > yum install ltsp-server finished with no any error. > > I executed ltsp-build-client. Installation has suspended with 26% gone. > > > > I repeated all with another server - the same situation. > > ltsp-build-client suspends with 26% gone. > > > > I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see > > anything interesting > > (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). > > > > What should I check or do to fix my problem? > > > > Best regards, > > Radek > > > > _______________________________________________ > > 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 Thu Jun 20 08:03:50 2013 From: burke at thealmquists.net (Burke Almquist) Date: Thu, 20 Jun 2013 03:03:50 -0500 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <1371714773.12669.34.camel@alpaga.bursztynowski.waw.pl> References: <1371149841.2721.23.camel@dupa> <1371714773.12669.34.camel@alpaga.bursztynowski.waw.pl> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I might have to try it myself. Se what happens. There were some big changes between LTSP on EL 6.1 or 6.2 and the version that we are currently installing. On Jun 20, 2013, at 2:52 AM, Radek Bursztynowski wrote: > Thanks for help. It can't be yum cache problem. I repeated all procedure > with 3 separated servers (each of them is new installation CentOS and > K12) - every time I achieved 26% gone of ltsp-build-client. > > You mentioned that somebody else had that problem. I search the k12osn > archives from March 2013 (new version of K12 was announced in March) and > I didn?t find any post related to my problem. > > Perhaps on another discussion list. Which one? > > Best regards, > Radek > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlHCt2cACgkQxWV7OPa/g5E4jgCdE3gvAP9haq4avdQ3IReB4uB2 ma0AniIPRdRvawzAw6av/U5WS2DdV+bZ =0NKm -----END PGP SIGNATURE----- From radek at bursztynowski.waw.pl Thu Jun 20 09:28:36 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 11:28:36 +0200 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: References: <1371149841.2721.23.camel@dupa> Message-ID: <1371720516.12669.56.camel@alpaga.bursztynowski.waw.pl> Previously I used CentOS 6.3 x86_64 and K12Linux ltsp-release-5-1, and was very satisfied (excluding mono sound with Windows), and I had no any problems with installation. I can add, that tried to install new K12Linux with CentOS 6.3 x86_64 - the same result like with CentOS 6.4. So at the moment I have no any LTSP. Best regards, Radek > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I might have to try it myself. Se what happens. > There were some big changes between LTSP on EL 6.1 or 6.2 and the version that we are currently installing. > > On Jun 20, 2013, at 2:52 AM, Radek Bursztynowski wrote: > > > Thanks for help. It can't be yum cache problem. I repeated all procedure > > with 3 separated servers (each of them is new installation CentOS and > > K12) - every time I achieved 26% gone of ltsp-build-client. > > > > You mentioned that somebody else had that problem. I search the k12osn > > archives from March 2013 (new version of K12 was announced in March) and > > I didn?t find any post related to my problem. > > > > Perhaps on another discussion list. Which one? > > > > Best regards, > > Radek > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iEYEARECAAYFAlHCt2cACgkQxWV7OPa/g5E4jgCdE3gvAP9haq4avdQ3IReB4uB2 > ma0AniIPRdRvawzAw6av/U5WS2DdV+bZ > =0NKm > -----END PGP SIGNATURE----- > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From jvermeulen at cawdekempen.be Thu Jun 20 09:31:07 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 20 Jun 2013 11:31:07 +0200 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <1371714773.12669.34.camel@alpaga.bursztynowski.waw.pl> References: <1371149841.2721.23.camel@dupa> <1371714773.12669.34.camel@alpaga.bursztynowski.waw.pl> Message-ID: <51C2CBDB.8070408@cawdekempen.be> Thanks for help. It can't be yum cache problem. I repeated all procedure > with 3 separated servers (each of them is new installation CentOS and > K12) - every time I achieved 26% gone of ltsp-build-client. > > You mentioned that somebody else had that problem. I search the k12osn > archives from March 2013 (new version of K12 was announced in March) and > I didn?t find any post related to my problem. > > Perhaps on another discussion list. Which one? > > Best regards, > Radek > > > > --- >> You might need to clean up your yum cache. I know someone else here had that problem. >> >> On Jun 13, 2013, at 1:57 PM, Radek Bursztynowski wrote: >> >>> Hello All, >>> >>> I try to install new LTSP k12Linux but there is no positive result. >>> The first I installed CentOS 6.4 x86_64. Next I followed >>> http://wiki.ltsp.org/wiki/Category:Fedora. >>> >>> yum install ltsp-server finished with no any error. >>> I executed ltsp-build-client. Installation has suspended with 26% gone. >>> >>> I repeated all with another server - the same situation. >>> ltsp-build-client suspends with 26% gone. >>> >>> I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see >>> anything interesting >>> (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). >>> >>> What should I check or do to fix my problem? >>> >>> Best regards, >>> Radek >>> >>> _______________________________________________ >>> 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 radek at bursztynowski.waw.pl Thu Jun 20 11:28:59 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 13:28:59 +0200 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <51C2CBDB.8070408@cawdekempen.be> Message-ID: <33240770.91371727739968.JavaMail.root@poczta.bursztynowski.waw.pl> Johan, I expect that your 36% will be the end. Best regards, Radek --- Thanks for help. It can't be yum cache problem. I repeated all procedure > with 3 separated servers (each of them is new installation CentOS and > K12) - every time I achieved 26% gone of ltsp-build-client. > > You mentioned that somebody else had that problem. I search the k12osn > archives from March 2013 (new version of K12 was announced in March) and > I didn?t find any post related to my problem. > > Perhaps on another discussion list. Which one? > > Best regards, > Radek > > > > --- >> You might need to clean up your yum cache. I know someone else here had that problem. >> >> On Jun 13, 2013, at 1:57 PM, Radek Bursztynowski wrote: >> >>> Hello All, >>> >>> I try to install new LTSP k12Linux but there is no positive result. >>> The first I installed CentOS 6.4 x86_64. Next I followed >>> http://wiki.ltsp.org/wiki/Category:Fedora. >>> >>> yum install ltsp-server finished with no any error. >>> I executed ltsp-build-client. Installation has suspended with 26% gone. >>> >>> I repeated all with another server - the same situation. >>> ltsp-build-client suspends with 26% gone. >>> >>> I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see >>> anything interesting >>> (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). >>> >>> What should I check or do to fix my problem? >>> >>> Best regards, >>> Radek >>> >>> _______________________________________________ >>> 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 jvermeulen at cawdekempen.be Thu Jun 20 11:33:49 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 20 Jun 2013 13:33:49 +0200 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <33240770.91371727739968.JavaMail.root@poczta.bursztynowski.waw.pl> References: <33240770.91371727739968.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <51C2E89D.2030300@cawdekempen.be> it is now at 78 % - and standing there for a while now - greetings, J. Op 20-06-13 13:28, Radek Bursztynowski schreef: > Johan, > > I expect that your 36% will be the end. > > Best regards, > Radek > > --- > > I am testing this, and the ltsp-build-client is now at 36 %. > > greetings, J. > > Op 20-06-13 09:52, Radek Bursztynowski schreef: >> Thanks for help. It can't be yum cache problem. I repeated all procedure >> with 3 separated servers (each of them is new installation CentOS and >> K12) - every time I achieved 26% gone of ltsp-build-client. >> >> You mentioned that somebody else had that problem. I search the k12osn >> archives from March 2013 (new version of K12 was announced in March) and >> I didn?t find any post related to my problem. >> >> Perhaps on another discussion list. Which one? >> >> Best regards, >> Radek >> >> >> >> --- >>> You might need to clean up your yum cache. I know someone else here had that problem. >>> >>> On Jun 13, 2013, at 1:57 PM, Radek Bursztynowski wrote: >>> >>>> Hello All, >>>> >>>> I try to install new LTSP k12Linux but there is no positive result. >>>> The first I installed CentOS 6.4 x86_64. Next I followed >>>> http://wiki.ltsp.org/wiki/Category:Fedora. >>>> >>>> yum install ltsp-server finished with no any error. >>>> I executed ltsp-build-client. Installation has suspended with 26% gone. >>>> >>>> I repeated all with another server - the same situation. >>>> ltsp-build-client suspends with 26% gone. >>>> >>>> I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see >>>> anything interesting >>>> (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). >>>> >>>> What should I check or do to fix my problem? >>>> >>>> Best regards, >>>> Radek >>>> >>>> _______________________________________________ >>>> 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 ; > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From jvermeulen at cawdekempen.be Thu Jun 20 11:36:15 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 20 Jun 2013 13:36:15 +0200 Subject: [K12OSN] Problem with ltsp-build-client In-Reply-To: <51C2E89D.2030300@cawdekempen.be> References: <33240770.91371727739968.JavaMail.root@poczta.bursztynowski.waw.pl> <51C2E89D.2030300@cawdekempen.be> Message-ID: <51C2E92F.5080407@cawdekempen.be> and it's stopped. I see this EM: Error encountered running command: setarch i386 /usr/bin/mock -r epel-6-i386 --target=i386 --configdir=/etc/ltsp/mock --arch=i386 --copyin /etc/sysconfig/firstboot /etc/sysconfig/firstboot check /opt/ltsp/mock/epel-6-i386/result/root.log for more detailed information [root at backupservergoh ~]# yum repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: ftp.ciril.fr * extras: mirror.ovh.net * ltsp: ltsprepo.s3.amazonaws.com * updates: mirror.ate.info repo id repo name status base CentOS-6 - Base 4802 extras CentOS-6 - Extras 12 ltsp LTSP - i386 58 updates CentOS-6 - Updates 601 repolist: 5473 greetings, J. Op 20-06-13 13:33, Johan Vermeulen schreef: > it is now at 78 % - and standing there for a while now - > > greetings, J. > > Op 20-06-13 13:28, Radek Bursztynowski schreef: >> Johan, >> >> I expect that your 36% will be the end. >> >> Best regards, >> Radek >> >> --- >> > >> I am testing this, and the ltsp-build-client is now at 36 %. >> >> greetings, J. >> >> Op 20-06-13 09:52, Radek Bursztynowski schreef: >>> Thanks for help. It can't be yum cache problem. I repeated all >>> procedure >>> with 3 separated servers (each of them is new installation CentOS and >>> K12) - every time I achieved 26% gone of ltsp-build-client. >>> >>> You mentioned that somebody else had that problem. I search the k12osn >>> archives from March 2013 (new version of K12 was announced in March) >>> and >>> I didn?t find any post related to my problem. >>> >>> Perhaps on another discussion list. Which one? >>> >>> Best regards, >>> Radek >>> >>> >>> >>> --- >>>> You might need to clean up your yum cache. I know someone else here >>>> had that problem. >>>> >>>> On Jun 13, 2013, at 1:57 PM, Radek Bursztynowski wrote: >>>> >>>>> Hello All, >>>>> >>>>> I try to install new LTSP k12Linux but there is no positive result. >>>>> The first I installed CentOS 6.4 x86_64. Next I followed >>>>> http://wiki.ltsp.org/wiki/Category:Fedora. >>>>> >>>>> yum install ltsp-server finished with no any error. >>>>> I executed ltsp-build-client. Installation has suspended with 26% >>>>> gone. >>>>> >>>>> I repeated all with another server - the same situation. >>>>> ltsp-build-client suspends with 26% gone. >>>>> >>>>> I checked /opt/ltsp/mock/epel-6-i386/result/root.log but I can't see >>>>> anything interesting >>>>> (https://www.bursztynowski.waw.pl/ftp/linux/LinuxTerminalServerProject/5/K12Linux/root.log). >>>>> >>>>> >>>>> What should I check or do to fix my problem? >>>>> >>>>> Best regards, >>>>> Radek >>>>> >>>>> _______________________________________________ >>>>> 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 ; >> >> _______________________________________________ >> K12OSN mailing list >> K12OSN at redhat.com >> https://www.redhat.com/mailman/listinfo/k12osn >> For more info see > From radek at bursztynowski.waw.pl Thu Jun 20 12:42:16 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 14:42:16 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? Message-ID: <23833340.431371732136885.JavaMail.root@poczta.bursztynowski.waw.pl> Hello again, Thanks to Johan who support me with my troubles. Is there anybody who completed ltsp-build-client with CentOS 6.4 x86_64 and ltsp-release-5-9.el6.noarch? I try with ltsp-build-client --release fedora-18-i386 --chroot fed-18 an after few seconds I can see: Error encountered running command: setarch i386 /usr/bin/mock -r fedora-18-i386 --target=i386 --configdir=/etc/ltsp/mock --arch=i386 --init check /opt/ltsp/mock/fedora-18-i386/result/root.log for more detailed information I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and there is: (...) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. DEBUG util.py:264: Warning: Group Base does not exist. DEBUG util.py:354: Child return code was: 0 (....) When I execute ltsp-build-client (with no options, so I understand like ltsp-build-client --release epel-6-i386 --chroot epel-6-i386), so I can find inside /opt/ltsp/mock/epel-6-i386/result/root.log (..) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. (..) Last rows inside root.log in both examples are: (..) DEBUG util.py:314: Executing command: ['/bin/umount', '-n', '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'} DEBUG util.py:354: Child return code was: 0 DEBUG util.py:116: kill orphans I touch the wall. Has anybody any idea to help me? Best regards, Radek -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvermeulen at cawdekempen.be Thu Jun 20 12:48:47 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 20 Jun 2013 14:48:47 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <23833340.431371732136885.JavaMail.root@poczta.bursztynowski.waw.pl> References: <23833340.431371732136885.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <51C2FA2F.20905@cawdekempen.be> Radek, last week, a ran ltsp-build-client 3t times with success, on Centos 6.4 x86_64 [root at centoshofkwartier network-scripts]# uname -a Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ltsp-server-5.4.5-21.el6.x86_64 ltspfs-1.1-7.el6.x86_64 ltsp-release-5-9.el6.noarch but today it didn't work for me either.... Op 20-06-13 14:42, Radek Bursztynowski schreef: > Hello again, > > Thanks to Johan who support me with my troubles. > > Is there anybody who completed ltsp-build-client with CentOS 6.4 > x86_64 and ltsp-release-5-9.el6.noarch? > > I try with ltsp-build-client --release fedora-18-i386 --chroot fed-18 > an after few seconds I can see: > > Error encountered running command: setarch i386 /usr/bin/mock -r > fedora-18-i386 --target=i386 --configdir=/etc/ltsp/mock > --arch=i386 --init > check /opt/ltsp/mock/fedora-18-i386/result/root.log for more > detailed information > > I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and there is: > > (...) > DEBUG util.py:264: > http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" > DEBUG util.py:264: Trying other mirror. > DEBUG util.py:264: Warning: Group Base does not exist. > DEBUG util.py:354: Child return code was: 0 > (....) > > > When I execute ltsp-build-client (with no options, so I understand > like ltsp-build-client --release epel-6-i386 --chroot epel-6-i386), so > I can find inside /opt/ltsp/mock/epel-6-i386/result/root.log > > (..) > DEBUG util.py:264: > http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" > DEBUG util.py:264: Trying other mirror. > (..) > > Last rows inside root.log in both examples are: > > (..) > DEBUG util.py:314: Executing command: ['/bin/umount', '-n', '-l', > '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': > 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': > 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'} > DEBUG util.py:354: Child return code was: 0 > DEBUG util.py:116: kill orphans > > I touch the wall. Has anybody any idea to help me? > > Best regards, > Radek > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see -------------- next part -------------- An HTML attachment was scrubbed... URL: From enslaver at enslaver.com Thu Jun 20 12:51:57 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Thu, 20 Jun 2013 07:51:57 -0500 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <23833340.431371732136885.JavaMail.root@poczta.bursztynowski.waw.pl> References: <23833340.431371732136885.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <51C2FAED.30503@enslaver.com> An HTML attachment was scrubbed... URL: From enslaver at enslaver.com Thu Jun 20 13:25:12 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Thu, 20 Jun 2013 08:25:12 -0500 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <51C2FA2F.20905@cawdekempen.be> References: <23833340.431371732136885.JavaMail.root@poczta.bursztynowski.waw.pl> <51C2FA2F.20905@cawdekempen.be> Message-ID: <51C302B8.9030706@enslaver.com> An HTML attachment was scrubbed... URL: From radek at bursztynowski.waw.pl Thu Jun 20 13:56:48 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 15:56:48 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? Message-ID: <2285117.731371736608700.JavaMail.root@poczta.bursztynowski.waw.pl> Hello Jashua, Many thanks for all advices. I will try it all by I come back to new K12Linux with new version 5.4.5-23 later. Now I have to prepare old environment with old ltsp-release http://mirror.ancl.hawaii.edu/~k12linux/ltsp-release-5-1.noarch.rpm. On Monday morning I must be ready. Best regards, Radek A good way to debug the ltsp-build-client is by using the debug and noprogress flags, that way you can watch it as it goes: i.e. $ ltsp-build-client --release epel-6-i386 --debug --noprogress I am pushing version 5.4.5-23 out to the servers now, the most common issue people have with the build-client is the cache from yum, to ensure a clean install be sure you run: yum clean all rm -rf /opt/ltsp/mock/epel-* yum update ltsp-server Before you build your chroot environment. On 6/20/13 7:48 AM, Johan Vermeulen wrote: Radek, last week, a ran ltsp-build-client 3t times with success, on Centos 6.4 x86_64 [root at centoshofkwartier network-scripts]# uname -a Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ltsp-server-5.4.5-21.el6.x86_64 ltspfs-1.1-7.el6.x86_64 ltsp-release-5-9.el6.noarch but today it didn't work for me either.... Op 20-06-13 14:42, Radek Bursztynowski schreef: Hello again, Thanks to Johan who support me with my troubles. Is there anybody who completed ltsp-build-client with CentOS 6.4 x86_64 and ltsp-release-5-9.el6.noarch? I try with ltsp-build-client --release fedora-18-i386 --chroot fed-18 an after few seconds I can see: Error encountered running command: setarch i386 /usr/bin/mock -r fedora-18-i386 --target=i386 --configdir=/etc/ltsp/mock --arch=i386 --init check /opt/ltsp/mock/fedora-18-i386/result/root.log for more detailed information I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and there is: (...) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. DEBUG util.py:264: Warning: Group Base does not exist. DEBUG util.py:354: Child return code was: 0 (....) When I execute ltsp-build-client (with no options, so I understand like ltsp-build-client --release epel-6-i386 --chroot epel-6-i386), so I can find inside /opt/ltsp/mock/epel-6-i386/result/root.log (..) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. (..) Last rows inside root.log in both examples are: (..) DEBUG util.py:314: Executing command: ['/bin/umount', '-n', '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'} DEBUG util.py:354: Child return code was: 0 DEBUG util.py:116: kill orphans I touch the wall. Has anybody any idea to help me? Best regards, Radek _______________________________________________ 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 jvermeulen at cawdekempen.be Thu Jun 20 14:00:50 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 20 Jun 2013 16:00:50 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <2285117.731371736608700.JavaMail.root@poczta.bursztynowski.waw.pl> References: <2285117.731371736608700.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <51C30B12.6070706@cawdekempen.be> I think that old hawaii mirror is no longer there. Op 20-06-13 15:56, Radek Bursztynowski schreef: > Hello Jashua, > > Many thanks for all advices. I will try it all by I come back to new K12Linux with new version 5.4.5-23 later. Now I have to prepare old environment with old ltsp-release http://mirror.ancl.hawaii.edu/~k12linux/ltsp-release-5-1.noarch.rpm. On Monday morning I must be ready. > > Best regards, > Radek > > > > > A good way to debug the ltsp-build-client is by using the debug and > noprogress flags, that way you can watch it as it goes: > > > > i.e. > > > > $ ltsp-build-client --release epel-6-i386 --debug --noprogress > > > > I am pushing version 5.4.5-23 out to the servers now, the most > common issue people have with the build-client is the cache from > yum, to ensure a clean install be sure you run: > > > > yum clean all > > rm -rf /opt/ltsp/mock/epel-* > > yum update ltsp-server > > > > Before you build your chroot environment. > > > > > > On 6/20/13 7:48 AM, Johan Vermeulen wrote: > > > > > Radek, > > > > last week, a ran ltsp-build-client 3t times with success, on > Centos 6.4 x86_64 > > > > [root at centoshofkwartier network-scripts]# uname -a > > Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed > Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > ltsp-server-5.4.5-21.el6.x86_64 > > ltspfs-1.1-7.el6.x86_64 > > ltsp-release-5-9.el6.noarch > > > > but today it didn't work for me either.... > > > > Op 20-06-13 14:42, Radek > Bursztynowski schreef: > > > Hello again, > > > > Thanks to Johan who support me with my troubles. > > > > Is there anybody who completed ltsp-build-client with CentOS 6.4 > x86_64 and ltsp-release-5-9.el6.noarch? > > > > I try with ltsp-build-client --release fedora-18-i386 --chroot > fed-18 > > an after few seconds I can see: > > > > Error encountered running command: setarch i386 /usr/bin/mock -r > fedora-18-i386 --target=i386 > --configdir=/etc/ltsp/mock --arch=i386 --init > > check /opt/ltsp/mock/fedora-18-i386/result/root.log for more > > detailed information > > > > I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and > there is: > > > > (...) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > DEBUG util.py:264: Warning: Group Base does not exist. > > DEBUG util.py:354: Child return code was: 0 > > (....) > > > > > > When I execute ltsp-build-client (with no options, so I > understand like ltsp-build-client --release epel-6-i386 --chroot > epel-6-i386), so I can find inside > /opt/ltsp/mock/epel-6-i386/result/root.log > > > > (..) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > (..) > > > > Last rows inside root.log in both examples are: > > > > (..) > > DEBUG util.py:314: Executing command: ['/bin/umount', '-n', > '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': > 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', > 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': > '/usr/bin:/bin:/usr/sbin:/sbin'} > > DEBUG util.py:354: Child return code was: 0 > > DEBUG util.py:116: kill orphans > > > > I touch the wall. Has anybody any idea to help me? > > > > Best regards, > > Radek > > > > > > > > > _______________________________________________ > 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 radek at bursztynowski.waw.pl Thu Jun 20 14:28:37 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 16:28:37 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <51C30B12.6070706@cawdekempen.be> Message-ID: <714000.861371738517575.JavaMail.root@poczta.bursztynowski.waw.pl> You are right. I don't know what to do. Best regards, Radek I think that old hawaii mirror is no longer there. Op 20-06-13 15:56, Radek Bursztynowski schreef: > Hello Jashua, > > Many thanks for all advices. I will try it all by I come back to new K12Linux with new version 5.4.5-23 later. Now I have to prepare old environment with old ltsp-release http://mirror.ancl.hawaii.edu/~k12linux/ltsp-release-5-1.noarch.rpm. On Monday morning I must be ready. > > Best regards, > Radek > > > > > A good way to debug the ltsp-build-client is by using the debug and > noprogress flags, that way you can watch it as it goes: > > > > i.e. > > > > $ ltsp-build-client --release epel-6-i386 --debug --noprogress > > > > I am pushing version 5.4.5-23 out to the servers now, the most > common issue people have with the build-client is the cache from > yum, to ensure a clean install be sure you run: > > > > yum clean all > > rm -rf /opt/ltsp/mock/epel-* > > yum update ltsp-server > > > > Before you build your chroot environment. > > > > > > On 6/20/13 7:48 AM, Johan Vermeulen wrote: > > > > > Radek, > > > > last week, a ran ltsp-build-client 3t times with success, on > Centos 6.4 x86_64 > > > > [root at centoshofkwartier network-scripts]# uname -a > > Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed > Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > ltsp-server-5.4.5-21.el6.x86_64 > > ltspfs-1.1-7.el6.x86_64 > > ltsp-release-5-9.el6.noarch > > > > but today it didn't work for me either.... > > > > Op 20-06-13 14:42, Radek > Bursztynowski schreef: > > > Hello again, > > > > Thanks to Johan who support me with my troubles. > > > > Is there anybody who completed ltsp-build-client with CentOS 6.4 > x86_64 and ltsp-release-5-9.el6.noarch? > > > > I try with ltsp-build-client --release fedora-18-i386 --chroot > fed-18 > > an after few seconds I can see: > > > > Error encountered running command: setarch i386 /usr/bin/mock -r > fedora-18-i386 --target=i386 > --configdir=/etc/ltsp/mock --arch=i386 --init > > check /opt/ltsp/mock/fedora-18-i386/result/root.log for more > > detailed information > > > > I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and > there is: > > > > (...) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > DEBUG util.py:264: Warning: Group Base does not exist. > > DEBUG util.py:354: Child return code was: 0 > > (....) > > > > > > When I execute ltsp-build-client (with no options, so I > understand like ltsp-build-client --release epel-6-i386 --chroot > epel-6-i386), so I can find inside > /opt/ltsp/mock/epel-6-i386/result/root.log > > > > (..) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > (..) > > > > Last rows inside root.log in both examples are: > > > > (..) > > DEBUG util.py:314: Executing command: ['/bin/umount', '-n', > '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': > 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', > 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': > '/usr/bin:/bin:/usr/sbin:/sbin'} > > DEBUG util.py:354: Child return code was: 0 > > DEBUG util.py:116: kill orphans > > > > I touch the wall. Has anybody any idea to help me? > > > > Best regards, > > Radek > > > > > > > > > _______________________________________________ > 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 ; _______________________________________________ K12OSN mailing list K12OSN at redhat.com https://www.redhat.com/mailman/listinfo/k12osn For more info see ; From radek at bursztynowski.waw.pl Thu Jun 20 14:29:55 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 16:29:55 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <51C2FAED.30503@enslaver.com> Message-ID: <27720241.881371738595893.JavaMail.root@poczta.bursztynowski.waw.pl> Hello Jashua, What about Fedora 17? Best regards, Radek Hello Radek, Fedora 18 is not yet fully supported as a chroot environment. On 6/20/13 7:42 AM, Radek Bursztynowski wrote: Hello again, Thanks to Johan who support me with my troubles. Is there anybody who completed ltsp-build-client with CentOS 6.4 x86_64 and ltsp-release-5-9.el6.noarch? I try with ltsp-build-client --release fedora-18-i386 --chroot fed-18 an after few seconds I can see: Error encountered running command: setarch i386 /usr/bin/mock -r fedora-18-i386 --target=i386 --configdir=/etc/ltsp/mock --arch=i386 --init check /opt/ltsp/mock/fedora-18-i386/result/root.log for more detailed information I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and there is: (...) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. DEBUG util.py:264: Warning: Group Base does not exist. DEBUG util.py:354: Child return code was: 0 (....) When I execute ltsp-build-client (with no options, so I understand like ltsp-build-client --release epel-6-i386 --chroot epel-6-i386), so I can find inside /opt/ltsp/mock/epel-6-i386/result/root.log (..) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. (..) Last rows inside root.log in both examples are: (..) DEBUG util.py:314: Executing command: ['/bin/umount', '-n', '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'} DEBUG util.py:354: Child return code was: 0 DEBUG util.py:116: kill orphans I touch the wall. Has anybody any idea to help me? Best regards, Radek _______________________________________________ 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 Thu Jun 20 15:17:41 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 17:17:41 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? Message-ID: <28185536.1071371741461542.JavaMail.root@poczta.bursztynowski.waw.pl> Jashua, I used your advice, all steps (yum clean all, rm -rf /opt/ltsp/mock/epel-*, yum update, ltsp-serverltsp-build-client --release epel-6-i386 --debug --noprogress). I installed version 5.4.5-23. Still the same. I enclose debug recordnig below. Best regards, Radek [root at passoa install]# ltsp-build-client --release epel-6-i386 --debug --noprogress DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file DEBUG: Loading configuration file '/etc/ltsp/ltsp-build-client.conf'. DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot mockbuild:x:1005:1005::/home/mockbuild:/bin/bash DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end DEBUG: Loading plugins in MODE=before-install: DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end DEBUG: Loading plugins in MODE=install: DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn A good way to debug the ltsp-build-client is by using the debug and noprogress flags, that way you can watch it as it goes: i.e. $ ltsp-build-client --release epel-6-i386 --debug --noprogress I am pushing version 5.4.5-23 out to the servers now, the most common issue people have with the build-client is the cache from yum, to ensure a clean install be sure you run: yum clean all rm -rf /opt/ltsp/mock/epel-* yum update ltsp-server Before you build your chroot environment. On 6/20/13 7:48 AM, Johan Vermeulen wrote: Radek, last week, a ran ltsp-build-client 3t times with success, on Centos 6.4 x86_64 [root at centoshofkwartier network-scripts]# uname -a Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ltsp-server-5.4.5-21.el6.x86_64 ltspfs-1.1-7.el6.x86_64 ltsp-release-5-9.el6.noarch but today it didn't work for me either.... Op 20-06-13 14:42, Radek Bursztynowski schreef: Hello again, Thanks to Johan who support me with my troubles. Is there anybody who completed ltsp-build-client with CentOS 6.4 x86_64 and ltsp-release-5-9.el6.noarch? I try with ltsp-build-client --release fedora-18-i386 --chroot fed-18 an after few seconds I can see: Error encountered running command: setarch i386 /usr/bin/mock -r fedora-18-i386 --target=i386 --configdir=/etc/ltsp/mock --arch=i386 --init check /opt/ltsp/mock/fedora-18-i386/result/root.log for more detailed information I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and there is: (...) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. DEBUG util.py:264: Warning: Group Base does not exist. DEBUG util.py:354: Child return code was: 0 (....) When I execute ltsp-build-client (with no options, so I understand like ltsp-build-client --release epel-6-i386 --chroot epel-6-i386), so I can find inside /opt/ltsp/mock/epel-6-i386/result/root.log (..) DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404" DEBUG util.py:264: Trying other mirror. (..) Last rows inside root.log in both examples are: (..) DEBUG util.py:314: Executing command: ['/bin/umount', '-n', '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'} DEBUG util.py:354: Child return code was: 0 DEBUG util.py:116: kill orphans I touch the wall. Has anybody any idea to help me? Best regards, Radek _______________________________________________ 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 Thu Jun 20 15:25:10 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Thu, 20 Jun 2013 10:25:10 -0500 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <28185536.1071371741461542.JavaMail.root@poczta.bursztynowski.waw.pl> References: <28185536.1071371741461542.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <51C31ED6.9090907@enslaver.com> Send me over the logs you have to my email, run this command and attach the /tmp/results.tar.gz file: # tar -czvf /tmp/results.tar.gz /opt/ltsp/mock/*/result On 6/20/13 10:17 AM, Radek Bursztynowski wrote: > Jashua, > > I used your advice, all steps (yum clean all, rm -rf /opt/ltsp/mock/epel-*, yum update, ltsp-serverltsp-build-client --release epel-6-i386 --debug --noprogress). > I installed version 5.4.5-23. Still the same. > > I enclose debug recordnig below. > > Best regards, > Radek > > [root at passoa install]# ltsp-build-client --release epel-6-i386 --debug --noprogress > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading configuration file '/etc/ltsp/ltsp-build-client.conf'. > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot > mockbuild:x:1005:1005::/home/mockbuild:/bin/bash > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end > DEBUG: Loading plugins in MODE=before-install: > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end > DEBUG: Loading plugins in MODE=install: > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > > > > > > A good way to debug the ltsp-build-client is by using the debug and > noprogress flags, that way you can watch it as it goes: > > > > i.e. > > > > $ ltsp-build-client --release epel-6-i386 --debug --noprogress > > > > I am pushing version 5.4.5-23 out to the servers now, the most > common issue people have with the build-client is the cache from > yum, to ensure a clean install be sure you run: > > > > yum clean all > > rm -rf /opt/ltsp/mock/epel-* > > yum update ltsp-server > > > > Before you build your chroot environment. > > > > > > On 6/20/13 7:48 AM, Johan Vermeulen wrote: > > > > > Radek, > > > > last week, a ran ltsp-build-client 3t times with success, on > Centos 6.4 x86_64 > > > > [root at centoshofkwartier network-scripts]# uname -a > > Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed > Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > ltsp-server-5.4.5-21.el6.x86_64 > > ltspfs-1.1-7.el6.x86_64 > > ltsp-release-5-9.el6.noarch > > > > but today it didn't work for me either.... > > > > Op 20-06-13 14:42, Radek > Bursztynowski schreef: > > > Hello again, > > > > Thanks to Johan who support me with my troubles. > > > > Is there anybody who completed ltsp-build-client with CentOS 6.4 > x86_64 and ltsp-release-5-9.el6.noarch? > > > > I try with ltsp-build-client --release fedora-18-i386 --chroot > fed-18 > > an after few seconds I can see: > > > > Error encountered running command: setarch i386 /usr/bin/mock -r > fedora-18-i386 --target=i386 > --configdir=/etc/ltsp/mock --arch=i386 --init > > check /opt/ltsp/mock/fedora-18-i386/result/root.log for more > > detailed information > > > > I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and > there is: > > > > (...) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > DEBUG util.py:264: Warning: Group Base does not exist. > > DEBUG util.py:354: Child return code was: 0 > > (....) > > > > > > When I execute ltsp-build-client (with no options, so I > understand like ltsp-build-client --release epel-6-i386 --chroot > epel-6-i386), so I can find inside > /opt/ltsp/mock/epel-6-i386/result/root.log > > > > (..) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > (..) > > > > Last rows inside root.log in both examples are: > > > > (..) > > DEBUG util.py:314: Executing command: ['/bin/umount', '-n', > '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': > 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', > 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': > '/usr/bin:/bin:/usr/sbin:/sbin'} > > DEBUG util.py:354: Child return code was: 0 > > DEBUG util.py:116: kill orphans > > > > I touch the wall. Has anybody any idea to help me? > > > > Best regards, > > Radek > > > > > > > > > _______________________________________________ > 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 radek at bursztynowski.waw.pl Thu Jun 20 15:43:07 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Thu, 20 Jun 2013 17:43:07 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? Message-ID: <30910387.1101371742987869.JavaMail.root@poczta.bursztynowski.waw.pl> It isn't possible, because /opt/ltsp/mock directory is empty! I suspected /opt/ltsp/mock/epel-6-i386 directory but there is no any directory or files. Regards, Radek Send me over the logs you have to my email, run this command and attach the /tmp/results.tar.gz file: # tar -czvf /tmp/results.tar.gz /opt/ltsp/mock/*/result On 6/20/13 10:17 AM, Radek Bursztynowski wrote: > Jashua, > > I used your advice, all steps (yum clean all, rm -rf /opt/ltsp/mock/epel-*, yum update, ltsp-serverltsp-build-client --release epel-6-i386 --debug --noprogress). > I installed version 5.4.5-23. Still the same. > > I enclose debug recordnig below. > > Best regards, > Radek > > [root at passoa install]# ltsp-build-client --release epel-6-i386 --debug --noprogress > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading configuration file '/etc/ltsp/ltsp-build-client.conf'. > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot > mockbuild:x:1005:1005::/home/mockbuild:/bin/bash > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end > DEBUG: Loading plugins in MODE=before-install: > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end > DEBUG: Loading plugins in MODE=install: > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > > > > > > A good way to debug the ltsp-build-client is by using the debug and > noprogress flags, that way you can watch it as it goes: > > > > i.e. > > > > $ ltsp-build-client --release epel-6-i386 --debug --noprogress > > > > I am pushing version 5.4.5-23 out to the servers now, the most > common issue people have with the build-client is the cache from > yum, to ensure a clean install be sure you run: > > > > yum clean all > > rm -rf /opt/ltsp/mock/epel-* > > yum update ltsp-server > > > > Before you build your chroot environment. > > > > > > On 6/20/13 7:48 AM, Johan Vermeulen wrote: > > > > > Radek, > > > > last week, a ran ltsp-build-client 3t times with success, on > Centos 6.4 x86_64 > > > > [root at centoshofkwartier network-scripts]# uname -a > > Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed > Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > ltsp-server-5.4.5-21.el6.x86_64 > > ltspfs-1.1-7.el6.x86_64 > > ltsp-release-5-9.el6.noarch > > > > but today it didn't work for me either.... > > > > Op 20-06-13 14:42, Radek > Bursztynowski schreef: > > > Hello again, > > > > Thanks to Johan who support me with my troubles. > > > > Is there anybody who completed ltsp-build-client with CentOS 6.4 > x86_64 and ltsp-release-5-9.el6.noarch? > > > > I try with ltsp-build-client --release fedora-18-i386 --chroot > fed-18 > > an after few seconds I can see: > > > > Error encountered running command: setarch i386 /usr/bin/mock -r > fedora-18-i386 --target=i386 > --configdir=/etc/ltsp/mock --arch=i386 --init > > check /opt/ltsp/mock/fedora-18-i386/result/root.log for more > > detailed information > > > > I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and > there is: > > > > (...) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > DEBUG util.py:264: Warning: Group Base does not exist. > > DEBUG util.py:354: Child return code was: 0 > > (....) > > > > > > When I execute ltsp-build-client (with no options, so I > understand like ltsp-build-client --release epel-6-i386 --chroot > epel-6-i386), so I can find inside > /opt/ltsp/mock/epel-6-i386/result/root.log > > > > (..) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > (..) > > > > Last rows inside root.log in both examples are: > > > > (..) > > DEBUG util.py:314: Executing command: ['/bin/umount', '-n', > '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': > 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', > 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': > '/usr/bin:/bin:/usr/sbin:/sbin'} > > DEBUG util.py:354: Child return code was: 0 > > DEBUG util.py:116: kill orphans > > > > I touch the wall. Has anybody any idea to help me? > > > > Best regards, > > Radek > > > > > > > > > _______________________________________________ > 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 ; _______________________________________________ K12OSN mailing list K12OSN at redhat.com https://www.redhat.com/mailman/listinfo/k12osn For more info see ; From radek at bursztynowski.waw.pl Fri Jun 21 09:42:30 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Fri, 21 Jun 2013 11:42:30 +0200 Subject: [K12OSN] Who completed ltsp-build-client with ltsp-release-5-9.el6.noarch? In-Reply-To: <30910387.1101371742987869.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <26484724.1331371807750742.JavaMail.root@poczta.bursztynowski.waw.pl> Jashua, Thanks a lot for you help, but I am still in the same place. Do you have any other idea? Best regards, Radek --- It isn't possible, because /opt/ltsp/mock directory is empty! I suspected /opt/ltsp/mock/epel-6-i386 directory but there is no any directory or files. Regards, Radek Send me over the logs you have to my email, run this command and attach the /tmp/results.tar.gz file: # tar -czvf /tmp/results.tar.gz /opt/ltsp/mock/*/result On 6/20/13 10:17 AM, Radek Bursztynowski wrote: > Jashua, > > I used your advice, all steps (yum clean all, rm -rf /opt/ltsp/mock/epel-*, yum update, ltsp-serverltsp-build-client --release epel-6-i386 --debug --noprogress). > I installed version 5.4.5-23. Still the same. > > I enclose debug recordnig below. > > Best regards, > Radek > > [root at passoa install]# ltsp-build-client --release epel-6-i386 --debug --noprogress > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading configuration file '/etc/ltsp/ltsp-build-client.conf'. > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot > mockbuild:x:1005:1005::/home/mockbuild:/bin/bash > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass > DEBUG: Loading plugin: configure: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end > DEBUG: Loading plugins in MODE=before-install: > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/007-dialog > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/009-mock-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-hosts > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-etc-mtab > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-mount-proc > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-base > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/010-set-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/010-set-resolver > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-cleanup-chroot > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/020-rootpath > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/030-fat-client > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/030-update-sshkeys > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/032-chroot-setup > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/035-update-kernels > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/common/091-unmount-dirs > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/095-rootpass > DEBUG: Loading plugin: before-install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/999-end > DEBUG: Loading plugins in MODE=install: > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-check-paths > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/000-enable-debug > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-load-configuration-file > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-arch > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/common/001-set-exclude > DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-build-client/RHEL/005-warn > > > > > > A good way to debug the ltsp-build-client is by using the debug and > noprogress flags, that way you can watch it as it goes: > > > > i.e. > > > > $ ltsp-build-client --release epel-6-i386 --debug --noprogress > > > > I am pushing version 5.4.5-23 out to the servers now, the most > common issue people have with the build-client is the cache from > yum, to ensure a clean install be sure you run: > > > > yum clean all > > rm -rf /opt/ltsp/mock/epel-* > > yum update ltsp-server > > > > Before you build your chroot environment. > > > > > > On 6/20/13 7:48 AM, Johan Vermeulen wrote: > > > > > Radek, > > > > last week, a ran ltsp-build-client 3t times with success, on > Centos 6.4 x86_64 > > > > [root at centoshofkwartier network-scripts]# uname -a > > Linux centoshofkwartier 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed > Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > > > > ltsp-server-5.4.5-21.el6.x86_64 > > ltspfs-1.1-7.el6.x86_64 > > ltsp-release-5-9.el6.noarch > > > > but today it didn't work for me either.... > > > > Op 20-06-13 14:42, Radek > Bursztynowski schreef: > > > Hello again, > > > > Thanks to Johan who support me with my troubles. > > > > Is there anybody who completed ltsp-build-client with CentOS 6.4 > x86_64 and ltsp-release-5-9.el6.noarch? > > > > I try with ltsp-build-client --release fedora-18-i386 --chroot > fed-18 > > an after few seconds I can see: > > > > Error encountered running command: setarch i386 /usr/bin/mock -r > fedora-18-i386 --target=i386 > --configdir=/etc/ltsp/mock --arch=i386 --init > > check /opt/ltsp/mock/fedora-18-i386/result/root.log for more > > detailed information > > > > I checked /opt/ltsp/mock/fedora-18-i386/result/root.log and > there is: > > > > (...) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/fc18/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > DEBUG util.py:264: Warning: Group Base does not exist. > > DEBUG util.py:354: Child return code was: 0 > > (....) > > > > > > When I execute ltsp-build-client (with no options, so I > understand like ltsp-build-client --release epel-6-i386 --chroot > epel-6-i386), so I can find inside > /opt/ltsp/mock/epel-6-i386/result/root.log > > > > (..) > > DEBUG util.py:264: http://ltsprepo.s3.amazonaws.com/rpm/el6/i386/repodata/repomd.xml: > [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: > 404" > > DEBUG util.py:264: Trying other mirror. > > (..) > > > > Last rows inside root.log in both examples are: > > > > (..) > > DEBUG util.py:314: Executing command: ['/bin/umount', '-n', > '-l', '/opt/ltsp/mock/epel-6-i386/root/proc'] with env {'LANG': > 'pl_PL.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', > 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': > '/usr/bin:/bin:/usr/sbin:/sbin'} > > DEBUG util.py:354: Child return code was: 0 > > DEBUG util.py:116: kill orphans > > > > I touch the wall. Has anybody any idea to help me? > > > > Best regards, > > Radek > > > > > > > > > _______________________________________________ > 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 ;; _______________________________________________ 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 brcisna at eazylivin.net Fri Jun 21 17:39:12 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Fri, 21 Jun 2013 12:39:12 -0500 Subject: [K12OSN] FL_Teachertool on latest ltsp5 Message-ID: <1371836352.17451.137.camel@localhost> Joshua, I pulled down the epoptes packages via yum,and when terminal launching epoptes i get an error about python-twisted wants python-zope-interface needs to be version 3.6.0 minimum. Centos 6 only provides python-zope-interface-3.5.3 I even tried editing the python site package for twisted to 3.5.0 ,, no joy. Can you when you have time change the requires for epoptes/twisted/python-zope-interface some time? Thank You, Barry From brcisna at eazylivin.net Fri Jun 21 18:25:06 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Fri, 21 Jun 2013 13:25:06 -0500 Subject: [K12OSN] FL_Teachertool on latest ltsp5 Message-ID: <1371839106.17451.143.camel@localhost> Joshua, #Update I was able to run epoptes without startup errors on server by manually installing the python-zope-interface-3.6.1 source package. On the client chroot i can not get epoptes-client to run as a service at boot.On the client i have to run epoptes-client manually then the client is seen in the epoptes gui,,and looks like most functions do work. I'll mess with the chroot epoptes-client more in a day,,and get it running as a service at boot hopefully. Thank You, Barry From enslaver at enslaver.com Sat Jun 22 16:25:15 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Sat, 22 Jun 2013 11:25:15 -0500 Subject: [K12OSN] FL_Teachertool on latest ltsp5 In-Reply-To: <1371839106.17451.143.camel@localhost> References: <1371839106.17451.143.camel@localhost> Message-ID: <51C5CFEB.7040300@enslaver.com> Barry - I had missed grabbing the i386 rpm for the zope interface, that might be where the issue occurred, nice catch. I have updated the repo's and pushed that rpm out. Also a note, the developer of epoptes recommends you install both client and server inside the chroot. On 6/21/13 1:25 PM, Barry Cisna wrote: > Joshua, > > #Update > > I was able to run epoptes without startup errors on server by manually > installing the python-zope-interface-3.6.1 source package. > > On the client chroot i can not get epoptes-client to run as a service at > boot.On the client i have to run epoptes-client manually then the client > is seen in the epoptes gui,,and looks like most functions do work. > I'll mess with the chroot epoptes-client more in a day,,and get it > running as a service at boot hopefully. > > Thank You, > Barry > > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From radek at bursztynowski.waw.pl Sun Jun 23 11:19:49 2013 From: radek at bursztynowski.waw.pl (=?UTF-8?Q?Rados=C5=82aw_Bursztynowski?=) Date: Sun, 23 Jun 2013 13:19:49 +0200 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository Message-ID: <6825a18aca6506c10ad9f101248d527a@192.168.0.199> Hi, Owing to help Joshua (many thanks again) I installed new LTSP K12 on my server, and I have few observation with it. I will try to do with this something later, but today my fresh views are as follow. Let me explain that my old thin clients are very old (the first one: Pentium III 1000 MHz, 512 MB of memory, GeForce 7300; the second one: notebook Compaq nc 8230, 2,4 GHz processor, 2 GB of memory, ATI graphic card), ltsp-server 5.9 and LTSP client epel-6-i386. Both my old clients cooperated with LTSP 5.1 very good. Views: 1. Notebook Compacq nc8230 starts booting, but after starting loading image from TFTP service (I can see information on my screen) I can see black screen only. 2. Pentium III - boots, I can work with the client, but: - maximum resolution which I cant reach on my monitor (Samsung SyncMaster T260HD) is 1680x1050, while with LTSP 5.1 I reached 1900x1200; - is very slow and watching movies is not acceptable. I can add, that one my thin client with AMD K6 III 400 MHz, 256 MB of memory, and GeFforce 5xxx graphic card with ltsp-server 5.1 worked fine, including movies. I tested LTSP 5.1 with thnin client Pentium 200 MMX, 128 MB of memory, and GeForce 440 and I can say, that this thin client works with LTSP 5.1 comparable to thin client Pentium III with LTSP 5.9 - not acceptable. Thin client Pentium 200 MMX was fine with LTSP 4.2. I will check later LTSP 5.9 with another thin client with Pentium 4 and 1 GB of memory. But I have old thin clients, which I would like to use now too. So my question is: Does anywhere LTSP 5.1 repository exist, which I can use to use my old think client (let's forget about Pentium 200 MMX, but Pentium III as a thin client - why not?)? Best regards, Radek From brcisna at eazylivin.net Mon Jun 24 11:25:15 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Mon, 24 Jun 2013 06:25:15 -0500 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository Message-ID: <1372073115.17451.153.camel@localhost> Radoslaw, I believe all of the "old" K12Linux repos mirrors are out of commission. I still have a couple servers that are running the 5.1 ltsp server myself. Something to consider in your situation/problem. Are you running a gigE lan with a gigE lan nic in your server? This is pretty much a must at this stage of ltsp. We used to run only 100mb lan/switches back in the day of 2.4 kernel ltsp and worked fine.For whatever behind the scenes stuff thrown into the kernel these days,a gigE backbone is a must. For kicks i run one client in a test bed on an old 10 base-t HUB. You wouldn't believe how long it took the one client to boot up! If you do not have a gigE switched lan you should at least get this up,and quite possibly your pentium machines will have enough "feed speed" to work reliably. BTW. The first versions of k12ltsp we used several 'dumpster' 486 machines and they did work quite well for that day and age :) Take Care, Barry From enslaver at enslaver.com Mon Jun 24 13:50:30 2013 From: enslaver at enslaver.com (Joshua Trimm) Date: Mon, 24 Jun 2013 08:50:30 -0500 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository In-Reply-To: <1372073115.17451.153.camel@localhost> References: <1372073115.17451.153.camel@localhost> Message-ID: <51C84EA6.1030109@enslaver.com> In terms of bandwith issues I have included a x2go client as one of the usable screen's in the ltsp-5.4.4+ rpm's. I apologize for the lack of documentation on it, I haven't had time to write up proper instructions. But if you are brave and know bash, have a look at /opt/ltsp/i386/usr/share/ltsp/x2gothinclient_start (assuming an i386 chroot). X2go uses the same technology that NX uses to do X11 compression. It basically is as simple as using SCREEN_03=x2goclient in your lts.conf. It's still being developed so customization is purely in your hands. VirtualGL support is also on my list to deliver 3D desktop support to thin clients without the need for any 3d graphics cards on the thin clients themselves. -Joshua On 6/24/13 6:25 AM, Barry Cisna wrote: > Radoslaw, > > I believe all of the "old" K12Linux repos mirrors are out of commission. > I still have a couple servers that are running the 5.1 ltsp server > myself. > > Something to consider in your situation/problem. Are you running a gigE > lan with a gigE lan nic in your server? This is pretty much a must at > this stage of ltsp. We used to run only 100mb lan/switches back in the > day of 2.4 kernel ltsp and worked fine.For whatever behind the scenes > stuff thrown into the kernel these days,a gigE backbone is a must. > > For kicks i run one client in a test bed on an old 10 base-t HUB. You > wouldn't believe how long it took the one client to boot up! > > If you do not have a gigE switched lan you should at least get this > up,and quite possibly your pentium machines will have enough "feed > speed" to work reliably. > > BTW. The first versions of k12ltsp we used several 'dumpster' 486 > machines and they did work quite well for that day and age :) > > Take Care, > Barry > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From burke at thealmquists.net Mon Jun 24 19:16:07 2013 From: burke at thealmquists.net (Burke Almquist) Date: Mon, 24 Jun 2013 14:16:07 -0500 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository In-Reply-To: <1372073115.17451.153.camel@localhost> References: <1372073115.17451.153.camel@localhost> Message-ID: <71F883D1-8A58-4477-BA42-D166525334FF@thealmquists.net> On Jun 24, 2013, at 6:25 AM, Barry Cisna wrote: > > > If you do not have a gigE switched lan you should at least get this > up,and quite possibly your pentium machines will have enough "feed > speed" to work reliably. To be clear, the clients can be fast (100mbit) ethernet, but the server NIC and the port on the switch that the server is hooked to should be gigE. As long as we are on the subject ... Radoslaw, (or anyone else that is interested for that matter) I do have a spare 26 port switch sitting around. It's an AMER SR24G2 (2 gigE ports and 24 10/100 ports). Perfect for hooking a server or two up to a lab full of clients. It's free to anyone that wants it. All I ask is that you pay for shipping. From radek at bursztynowski.waw.pl Tue Jun 25 09:00:24 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Tue, 25 Jun 2013 11:00:24 +0200 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository Message-ID: <30089434.171372150824546.JavaMail.root@poczta.bursztynowski.waw.pl> Baryy, Thanks a lot for you answer. All my computers in the network have 1 Gb/s NICs. I tested (LTSP 5.1) old machines (Pentium III, AMD K 6 III) equipped with 100 Mb/s too. My feeling with 100 Mb/s NICs (still LTSP 5.1) are quite fine. If one or two machines (thin clients with 100 Mb/s NIcs) runs and plays movies, movies are acceptable. If several thin client with NIC 100 Mb/s runs and don't play movies - everything is OK. More thins clients with 100 Mb/s I didn't test. I forgot to say that all my network is equipped with 1 Gb/s switches. I didn't have any problems with my LTSP clients and network (still LTSP 5.1), including old thin client (AMD K6 III 400 MHz and 256 MB of memory, Pentium III 1000 MHz and 512 MB of memory and 1 Gb/s NICs). My view about theses old thin clients is that movies (1 Gb/s NIC) in Linux environment play movies fine. Worse is with Windows 7 environment (rdesktop or xfreerd). Then movies play little slowly, but the same situation is with more modern thin client. The same situation with Windows 7 is when I use rdesktop or xfreerdp with no LTSP environment - so it is no LTSP problem. Trucking this way I replaced LTSP 5.1 with latest LTSP K12 and my view I mentioned in previous may post. Let me add that my server is quite loaded by different services. This machine is 2core Pentium and one NIC 1Gb/s (bridge) and supports 3 virtual machines (KVM) not high loaded. I know that I have few memory (8 GB of memory), but with LTSP 5.1 everything was OK. I monitor usage of two cores and their average utilization - is between 10 - 20% (standard), with very rare picks. This server is my test environment. Next week I will return to my standard environment (modern processors, more memory, two NICs 1 Gb/s in every server) but today I fight with test environment. Today night I reinstalled my test environment equipped with two NICs. So I am going to return with new post and with new view. Thanks again for any answer - I will be satisfied with every. Best regards, Radek ---- Radoslaw, I believe all of the "old" K12Linux repos mirrors are out of commission. I still have a couple servers that are running the 5.1 ltsp server myself. Something to consider in your situation/problem. Are you running a gigE lan with a gigE lan nic in your server? This is pretty much a must at this stage of ltsp. We used to run only 100mb lan/switches back in the day of 2.4 kernel ltsp and worked fine.For whatever behind the scenes stuff thrown into the kernel these days,a gigE backbone is a must. For kicks i run one client in a test bed on an old 10 base-t HUB. You wouldn't believe how long it took the one client to boot up! If you do not have a gigE switched lan you should at least get this up,and quite possibly your pentium machines will have enough "feed speed" to work reliably. BTW. The first versions of k12ltsp we used several 'dumpster' 486 machines and they did work quite well for that day and age :) Take Care, Barry _______________________________________________ K12OSN mailing list K12OSN at redhat.com https://www.redhat.com/mailman/listinfo/k12osn For more info see ; From radek at bursztynowski.waw.pl Tue Jun 25 10:23:03 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Tue, 25 Jun 2013 12:23:03 +0200 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository Message-ID: <31702353.341372155783867.JavaMail.root@poczta.bursztynowski.waw.pl> Burke, I know network limitation. My problem is, that on the same environment with LTSP 5.1 thin clients worked fine. With new LTSP - no. I asked myself - what happened (there is no any changes in switches, cables, server (and NIC), and thin clients (and NICs); I updated CentOS 6.3 to 6.4 and LTSP 5.1 with to newest)? Best regards, Radek On Jun 24, 2013, at 6:25 AM, Barry Cisna wrote: > > > If you do not have a gigE switched lan you should at least get this > up,and quite possibly your pentium machines will have enough "feed > speed" to work reliably. To be clear, the clients can be fast (100mbit) ethernet, but the server NIC and the port on the switch that the server is hooked to should be gigE. As long as we are on the subject ... Radoslaw, (or anyone else that is interested for that matter) I do have a spare 26 port switch sitting around. It's an AMER SR24G2 (2 gigE ports and 24 10/100 ports). Perfect for hooking a server or two up to a lab full of clients. It's free to anyone that wants it. All I ask is that you pay for shipping. _______________________________________________ K12OSN mailing list K12OSN at redhat.com https://www.redhat.com/mailman/listinfo/k12osn For more info see ; From william at fragakis.com Tue Jun 25 16:22:22 2013 From: william at fragakis.com (William Fragakis) Date: Tue, 25 Jun 2013 12:22:22 -0400 Subject: [K12OSN] K Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository In-Reply-To: References: Message-ID: <1372177342.1555.5.camel@server.ltsp> Radek, Sorry for the obvious question but are your lts.conf files reasonably identical going from 5.1 to 5.9? In other words, you aren't using anything that slows things down like compression, etc. in the new version? btw, thanks for sharing your experiences for those of us about to follow your footsteps. thanks, William Fragakis On Sun, 2013-06-23 at 12:00 -0400, k12osn-request at redhat.com wrote: > Message: 2 > Date: Sun, 23 Jun 2013 13:19:49 +0200 > From: Rados?aw Bursztynowski > To: > Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can > find old ltsp-server 5.1 repository > Message-ID: <6825a18aca6506c10ad9f101248d527a at 192.168.0.199> > Content-Type: text/plain; charset="US-ASCII" > > Hi, > > Owing to help Joshua (many thanks again) I installed new LTSP K12 on > my > server, and I have few observation with it. I will try to do with this > something later, but today my fresh views are as follow. > > Let me explain that my old thin clients are very old (the first one: > Pentium III 1000 MHz, 512 MB of memory, GeForce 7300; the second one: > notebook Compaq nc 8230, 2,4 GHz processor, 2 GB of memory, ATI > graphic > card), ltsp-server 5.9 and LTSP client epel-6-i386. Both my old > clients > cooperated with LTSP 5.1 very good. > > Views: > > 1. Notebook Compacq nc8230 starts booting, but after starting loading > image from TFTP service (I can see information on my screen) I can see > black screen only. > > 2. Pentium III - boots, I can work with the client, but: > - maximum resolution which I cant reach on my monitor (Samsung > SyncMaster T260HD) is 1680x1050, while with LTSP 5.1 I reached > 1900x1200; > - is very slow and watching movies is not acceptable. > > I can add, that one my thin client with AMD K6 III 400 MHz, 256 MB of > memory, and GeFforce 5xxx graphic card with ltsp-server 5.1 worked > fine, > including movies. I tested LTSP 5.1 with thnin client Pentium 200 MMX, > 128 > MB of memory, and GeForce 440 and I can say, that this thin client > works > with LTSP 5.1 comparable to thin client Pentium III with LTSP 5.9 - > not > acceptable. Thin client Pentium 200 MMX was fine with LTSP 4.2. > > I will check later LTSP 5.9 with another thin client with Pentium 4 > and 1 > GB of memory. > > But I have old thin clients, which I would like to use now too. > > So my question is: > > Does anywhere LTSP 5.1 repository exist, which I can use to use my old > think client (let's forget about Pentium 200 MMX, but Pentium III as a > thin > client - why not?)? > > > Best regards, > Radek From radek at bursztynowski.waw.pl Tue Jun 25 16:40:20 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Tue, 25 Jun 2013 18:40:20 +0200 Subject: [K12OSN] K Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository In-Reply-To: <1372177342.1555.5.camel@server.ltsp> References: Message-ID: <1372178420.3487.11.camel@advocat.bursztynowski.waw.pl> William, I didn't change anything. All config files including lts.conf I got from my archive, and I use all the same services using the same config files. My firewall is stopped. I will see soon what will be after new system installation (I added the second NIC card i HDD dedicated to LTSP. Best regards, Radek ---- > Radek, > Sorry for the obvious question but are your lts.conf files reasonably > identical going from 5.1 to 5.9? In other words, you aren't using > anything that slows things down like compression, etc. in the new > version? > > btw, thanks for sharing your experiences for those of us about to follow > your footsteps. > > thanks, > William Fragakis > > On Sun, 2013-06-23 at 12:00 -0400, k12osn-request at redhat.com wrote: > > Message: 2 > > Date: Sun, 23 Jun 2013 13:19:49 +0200 > > From: Rados?aw Bursztynowski > > To: > > Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can > > find old ltsp-server 5.1 repository > > Message-ID: <6825a18aca6506c10ad9f101248d527a at 192.168.0.199> > > Content-Type: text/plain; charset="US-ASCII" > > > > Hi, > > > > Owing to help Joshua (many thanks again) I installed new LTSP K12 on > > my > > server, and I have few observation with it. I will try to do with this > > something later, but today my fresh views are as follow. > > > > Let me explain that my old thin clients are very old (the first one: > > Pentium III 1000 MHz, 512 MB of memory, GeForce 7300; the second one: > > notebook Compaq nc 8230, 2,4 GHz processor, 2 GB of memory, ATI > > graphic > > card), ltsp-server 5.9 and LTSP client epel-6-i386. Both my old > > clients > > cooperated with LTSP 5.1 very good. > > > > Views: > > > > 1. Notebook Compacq nc8230 starts booting, but after starting loading > > image from TFTP service (I can see information on my screen) I can see > > black screen only. > > > > 2. Pentium III - boots, I can work with the client, but: > > - maximum resolution which I cant reach on my monitor (Samsung > > SyncMaster T260HD) is 1680x1050, while with LTSP 5.1 I reached > > 1900x1200; > > - is very slow and watching movies is not acceptable. > > > > I can add, that one my thin client with AMD K6 III 400 MHz, 256 MB of > > memory, and GeFforce 5xxx graphic card with ltsp-server 5.1 worked > > fine, > > including movies. I tested LTSP 5.1 with thnin client Pentium 200 MMX, > > 128 > > MB of memory, and GeForce 440 and I can say, that this thin client > > works > > with LTSP 5.1 comparable to thin client Pentium III with LTSP 5.9 - > > not > > acceptable. Thin client Pentium 200 MMX was fine with LTSP 4.2. > > > > I will check later LTSP 5.9 with another thin client with Pentium 4 > > and 1 > > GB of memory. > > > > But I have old thin clients, which I would like to use now too. > > > > So my question is: > > > > Does anywhere LTSP 5.1 repository exist, which I can use to use my old > > think client (let's forget about Pentium 200 MMX, but Pentium III as a > > thin > > client - why not?)? > > > > > > Best regards, > > Radek > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From jvermeulen at cawdekempen.be Tue Jun 25 17:23:17 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Tue, 25 Jun 2013 19:23:17 +0200 Subject: [K12OSN] K Few observations with ltsp-server 5.9 | Where I canfind old ltsp-server 5.1 repository Message-ID: Radek, As I mentioned before, I faced the same 2 weeks ago. The older k12 does not support my new intel-chipset thinclient, screen goes black. The newer system does not properly support my older via-chipset thinclients. In order to save the day i copied all files under /opt ltsp and /var/lib/tftpboot from an older system to a new install. Grts j. Radek Bursztynowski schreef: >William, > >I didn't change anything. All config files including lts.conf I got from >my archive, and I use all the same services using the same config files. >My firewall is stopped. I will see soon what will be after new system >installation (I added the second NIC card i HDD dedicated to LTSP. > >Best regards, >Radek > > >---- >> Radek, >> Sorry for the obvious question but are your lts.conf files reasonably >> identical going from 5.1 to 5.9? In other words, you aren't using >> anything that slows things down like compression, etc. in the new >> version? >> >> btw, thanks for sharing your experiences for those of us about to follow >> your footsteps. >> >> thanks, >> William Fragakis >> >> On Sun, 2013-06-23 at 12:00 -0400, k12osn-request at redhat.com wrote: >> > Message: 2 >> > Date: Sun, 23 Jun 2013 13:19:49 +0200 >> > From: Rados?aw Bursztynowski >> > To: >> > Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can >> > find old ltsp-server 5.1 repository >> > Message-ID: <6825a18aca6506c10ad9f101248d527a at 192.168.0.199> >> > Content-Type: text/plain; charset="US-ASCII" >> > >> > Hi, >> > >> > Owing to help Joshua (many thanks again) I installed new LTSP K12 on >> > my >> > server, and I have few observation with it. I will try to do with this >> > something later, but today my fresh views are as follow. >> > >> > Let me explain that my old thin clients are very old (the first one: >> > Pentium III 1000 MHz, 512 MB of memory, GeForce 7300; the second one: >> > notebook Compaq nc 8230, 2,4 GHz processor, 2 GB of memory, ATI >> > graphic >> > card), ltsp-server 5.9 and LTSP client epel-6-i386. Both my old >> > clients >> > cooperated with LTSP 5.1 very good. >> > >> > Views: >> > >> > 1. Notebook Compacq nc8230 starts booting, but after starting loading >> > image from TFTP service (I can see information on my screen) I can see >> > black screen only. >> > >> > 2. Pentium III - boots, I can work with the client, but: >> > - maximum resolution which I cant reach on my monitor (Samsung >> > SyncMaster T260HD) is 1680x1050, while with LTSP 5.1 I reached >> > 1900x1200; >> > - is very slow and watching movies is not acceptable. >> > >> > I can add, that one my thin client with AMD K6 III 400 MHz, 256 MB of >> > memory, and GeFforce 5xxx graphic card with ltsp-server 5.1 worked >> > fine, >> > including movies. I tested LTSP 5.1 with thnin client Pentium 200 MMX, >> > 128 >> > MB of memory, and GeForce 440 and I can say, that this thin client >> > works >> > with LTSP 5.1 comparable to thin client Pentium III with LTSP 5.9 - >> > not >> > acceptable. Thin client Pentium 200 MMX was fine with LTSP 4.2. >> > >> > I will check later LTSP 5.9 with another thin client with Pentium 4 >> > and 1 >> > GB of memory. >> > >> > But I have old thin clients, which I would like to use now too. >> > >> > So my question is: >> > >> > Does anywhere LTSP 5.1 repository exist, which I can use to use my old >> > think client (let's forget about Pentium 200 MMX, but Pentium III as a >> > thin >> > client - why not?)? >> > >> > >> > Best regards, >> > Radek >> >> _______________________________________________ >> 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 Jun 25 18:04:13 2013 From: burke at thealmquists.net (Burke Almquist) Date: Tue, 25 Jun 2013 13:04:13 -0500 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository In-Reply-To: <31702353.341372155783867.JavaMail.root@poczta.bursztynowski.waw.pl> References: <31702353.341372155783867.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: It looks to me as if there have been a number of changes in the setup for LTSP on EL/Fedora under the new version. I think the network setup and the build process have changed significantly. Thus we are having significant issues. Some of the fedorahosted wiki information, particularly the setup information that is specific to how Fedora/EL chose to integrate LTSP, may not apply now. I think that is part of the reason for our recent troubles. We really need to get the wiki updated with good information. On Jun 25, 2013, at 5:23 AM, Radek Bursztynowski wrote: > Burke, > > I know network limitation. My problem is, that on the same environment with LTSP 5.1 thin clients worked fine. With new LTSP - no. I asked myself - what happened (there is no any changes in switches, cables, server (and NIC), and thin clients (and NICs); I updated CentOS 6.3 to 6.4 and LTSP 5.1 with to newest)? > > Best regards, > Radek From brcisna at eazylivin.net Tue Jun 25 22:26:40 2013 From: brcisna at eazylivin.net (Barry R Cisna) Date: Tue, 25 Jun 2013 17:26:40 -0500 Subject: [K12OSN] Italc ltsp5 Message-ID: <1372199200.14625.42.camel@server1.eazylivin.net> Hello All, Wanted to let anyone that may be interested in using Italc along with CentOS 6.x LTSP5. I have made up server and client rpm installs. I wanted to do this to try and achieve remote monitoring for both Linux and Windows machines, bottom line. After getting this to work smoothly on the TC's and Linux fat clients,running Italc on Windows machines was proving to be a tough row to hoe, on these machines both XP and 7 32 & 64 bit. Just a few days ago,I found out there is a new release of Italc for Windows.These have proven to be reliable now. There are both x86 and x86_64 server builds and an x86 client build. Also the latest Win32 and Win64 installers are here for convenience. Please have a look at the INSTALL file (on ftp server) for post install steps. This is pretty simple. You simply generate the new key pairs, copy them to client chroot, and have to make some changes in the Italc Console Manager. All functions of Italc do work on the TC's ftp://eazylivin.net/pub/italc-ltsp5/ Take Care, Barry From radek at bursztynowski.waw.pl Tue Jun 25 22:49:23 2013 From: radek at bursztynowski.waw.pl (Radek Bursztynowski) Date: Wed, 26 Jun 2013 00:49:23 +0200 Subject: [K12OSN] Few observations with ltsp-server 5.9 | Where I can find old ltsp-server 5.1 repository In-Reply-To: References: <31702353.341372155783867.JavaMail.root@poczta.bursztynowski.waw.pl> Message-ID: <1372200563.6813.46.camel@alpaga.bursztynowski.waw.pl> I begin to think that my trouble can be joined with 2 NICs. It is my first experience with 2 NICs configuration. The true is that my server had two NICs, but one of them I didn't configure - was switched off. Perhaps LTSP 5.1 recognized two of NICs, but I used only one, and LTSP 5.1 didn't force me to interesting of one downed NIC. Now we can read in LTSP doc that the second NIC receives 192.168.67.1 IP address by default. So LTSP 5.9 something do with second NIC (perhaps something different like LTSP 5.1). Finally I could use LTSP 5.9 with my main NIC, but network worked slowly. This is my surmise only. I confirm myself with this think because after my new server installation (server with two configured NICs), I was forced to reconfigure Samba service, because Samba saw eht1 NIC as default interface instead of br0, like in the past. When I described in smb.conf br0 as a Samba NIC - Samba works fine. But Firefox works to slow. We can inform Samba in smb.conf which NIC should be use, but Firefox use system configuration. I think that I should tell system which NIC is the first. But I don't know how. I repeat that it is my surmise only. Perhaps tomorrow I will be more clever. Best regards, Radek --- > It looks to me as if there have been a number of changes in the setup for LTSP on EL/Fedora under the new version. I think the network setup and the build process have changed significantly. Thus we are having significant issues. Some of the fedorahosted wiki information, particularly the setup information that is specific to how Fedora/EL chose to integrate LTSP, may not apply now. I think that is part of the reason for our recent troubles. We really need to get the wiki updated with good information. > > > On Jun 25, 2013, at 5:23 AM, Radek Bursztynowski wrote: > > > Burke, > > > > I know network limitation. My problem is, that on the same environment with LTSP 5.1 thin clients worked fine. With new LTSP - no. I asked myself - what happened (there is no any changes in switches, cables, server (and NIC), and thin clients (and NICs); I updated CentOS 6.3 to 6.4 and LTSP 5.1 with to newest)? > > > > Best regards, > > Radek > > > _______________________________________________ > K12OSN mailing list > K12OSN at redhat.com > https://www.redhat.com/mailman/listinfo/k12osn > For more info see From jvermeulen at cawdekempen.be Thu Jun 27 12:23:46 2013 From: jvermeulen at cawdekempen.be (Johan Vermeulen) Date: Thu, 27 Jun 2013 14:23:46 +0200 Subject: [K12OSN] searching voor ideal thinclient Message-ID: <51CC2ED2.4030802@cawdekempen.be> Dear All, for the " old " K12 Linux rpm -qa | grep ltsp ltsp-server-5.2.17-1.el6.x86_64 ltspfs-0.8-2.el6.x86_64 Can anyone recommend an affordable thinclient ( 200 - 300 Euro ) that works easy with K12Linux? By easy I mean: * press f12 or f10 on booting *change boot order to network first * the thing just boots. Many thanks for any advice. greetings, J. -- Johan Vermeulen IT-medewerker Caw De Kempen Opensource Software is the future. From brcisna at eazylivin.net Thu Jun 27 12:57:43 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Thu, 27 Jun 2013 07:57:43 -0500 Subject: [K12OSN] searching voor ideal thinclient Message-ID: <1372337863.10305.24.camel@localhost> Johan, There are many usable thin clients available that will work great with a current (or old) ltsp installation, A very cheap and good working unit that can be easily be found on Ebay (and there are several) if you were wanting to setup,,say a 25 seat lab is the HP 5730. These come pre-installed with Windows Xp embedded .All you need to do is change to PXE in the system bios to boot to your ltsp setup. These units can be had for $50- 55 USD shipped here in the states. I am not sure how shipping would be to Belgium? Could get pricey I am sure...for 25 units for example. Make sure you get the wall adapter with each unit. You would have to get the Euro converter if you Ebayed these keep in mind. Something to look at anyway. Take Care, Barry From brcisna at eazylivin.net Fri Jun 28 12:27:29 2013 From: brcisna at eazylivin.net (Barry Cisna) Date: Fri, 28 Jun 2013 07:27:29 -0500 Subject: [K12OSN] Laptop display problems Message-ID: <1372422449.10305.35.camel@localhost> Hello All, Has anyone on list had any luck getting any laptop displays to work with the last couple iterations of LTSP - 5? I have 5 test laptops that are about 2-5 year old units,that none will get a display. In syslog each machine does end up with a couple of ldminfod lines as though 'behind the scene" they are getting a login dialog. The display ends up at Booting Linux",,I never see the 'switch root lines. Would a different pxe.0 file make any difference?It seems many moons ago a different pxe.0 file fixed some TC nic problems? Thanks, Barry