Re: ltsp-build-client fails on CentOS 6.4
Hi Santiago,
Thanks for your email. How do I make sure that I'm using the EPEL repo?
I made another attempt at a setup from scratch. I'm using Cent OS 6.4, 32 bit version (because of some
restrictions on the software that's going to run on it)
The instructions (http://wiki.ltsp.org/wiki/Category:Fedora) say to do the following:
> 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
> Edit config files in /etc/ltsp/
> ltsp-build-client
when I get to the "yum install ltsp-server" part, yum fails with the following error:
> warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY
> Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ltsp
>
>
> The GPG keys listed for the "LTSP - i386" repository are already installed but they are not correct for this package.
> Check that the correct key URLs are configured for this repository.
I suspect that's because I'm using the 32 bit version and not the 64 bit - the ltsprepo seems to be for 64 bit. I
made a guess that there would be a 32 bit version and tried the following:
> rpm -Uvh http://ltsprepo.s3.amazonaws.com/rpm/el6/i686/ltsp-release-5-9.el6.noarch.rpm
> yum install ltsp-server
But I get the same error.
I was able to get the ltsp-server installed by installing the EPEL repo first:
> rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
> yum install ltsp-server
But then I got the same error as I was getting last time with the ltsp-build-client:
> [root <at> testbox ltsp]# ltsp-build-client
>
> Error encountered running command: setarch i686 /usr/bin/mock -r epel-6-i386 --target=i686
--configdir=/etc/ltsp/mock --arch=i686 --chroot rm /var/lib/rpm/__db.001 /var/lib/rpm/__db.002
/var/lib/rpm/__db.003 /var/lib/rpm/__db.004
> check /opt/ltsp/mock/epel-6-i386/result/root.log for more
> detailed information
> [root <at> testbox ~]# uname -a
> Linux testbox.localdomain 2.6.32-358.6.1.el6.i686 #1 SMP Tue Apr 23 18:13:20 UTC 2013 i686 i686 i386 GNU/Linux
Thanks in advance!
Regards,
Paul.
On 26/04/2013, at 11:05 PM,
ltsp-discuss-request@... wrote:
> Message: 2
> Date: Tue, 23 Apr 2013 13:19:44 -0300 (UYT)
> From: Santiago Mera <santiago.mera@...>
> Subject: Re: [Ltsp-discuss] ltsp-build-client fails on CentOS 6.4
> To: ltsp-discuss@...
> Message-ID: <400621604.11148.1366733984526.JavaMail.root@...>
> Content-Type: text/plain; charset="utf-8"
>
> Hello Paul,
> I am also running LTSP on CentOS 6.4 and had some problems with mock.
>
> It finally came down to the version of mock I was using. For some reason I had mock installed from the
rpmforge repo (v 1.1.11) instead of using the EPEL repo (v 1.1.28).
> After making sure I was using mock from the EPEL repo everything worked ok.
>
> Hope this helps.
>
>> I recently did a software update on our client's LTSP setup, and something in the software update broke
the LTSP configuration. In trying to step through the whole issue, one of the big problems is that the
ltsp-build-client terminates abnormally with an error. It appears that ltsp-build-client uses the
"mock" command, and this uses a configuration file in /etc/ltsp/mock/fedora-18-i386.cfg.cfg, and it
appears to be missing some lines or something and won't parse properly in python.
>>
>> I setup a clean CentOS 6.4 system from scratch and was able to replicate the problem, so I don't think it's a
matter of old config files or whatever.
>>
>> Firstly, who's the best person to report this to?
>>
>> Secondly, has anyone else had this issue that can shed some light on it?
Did you know Adam and Eve had the ideal marriage - he didn’t have to hear about all the other men she could
have married, and she didn’t have to hear about the way his mother cooked!
--
--
Paul W. Mulroney Logical Developments
pmulroney@... 86 Coolgardie Street
www.logicaldevelopments.com.au BENTLEY WA 6102
Ph: +61 8 9458 3889 Fax: +61 8 9458 2169
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
after hours of googling I'm non the wiser where the problem lies. When a
user logs in on a client, the login keyring does not get automatically
unlocked. It works fine when the same user logs in on the LTSP server
itself. I tried different flavours of fat-client-desktop
(ubuntu-desktop, lxde, kde-desktop, etc.) and also a different newly
installed server.
The keyring password is the same as the login password, the login
keyring is set as default in seahorse and libpam-gnome-keyring is
installed by default.
root <at> ltsp:/opt/ltsp/lxde/etc/pam.d# ls -la
total 96
drwxr-xr-x 2 root root 4096 Apr 26 15:10 .
drwxr-xr-x 97 root root 4096 Apr 26 17:04 ..
-rw-rw-
RSS Feed