Fixed YOU error on SuSE 9.3

4/12/2005 marc 15 comments

I recently installed SuSE Professional 9.3 on my workstation in my office at Novell. After installation there was an error when using the Yast Online Update (YOU) tool that caused it to fail getting updates. After researching the issue abit and talking to a few people (Marcus Meissner, Xin Wei Hu and Anders Johansson) I was able to solve the issue.

After selecting a mirror (I had tried several) in Yast2′s YOU I got the following error:

Error
Signature check for patch info files failed.
Cannot load patch information.

The error in YOU was less than informative other than the signature check had failed. I googled for the error message and found that several other people had seen the same message however, the reasons varied. The one that seemed closest to what I was seeing was in the SuSE help database in this entry: http://portal.suse.com/sdb/en/2002/05/swiegra_you-gpg.html. There is an error in the entry though. The line:

wget http://www.novell.com/linux/security/contact.html && gpg --import \

      --homedir /usr/lib/rpm/gnupg build_pgp.html

Should be:

wget http://www.novell.com/linux/security/contact.html && gpg --import \

      --homedir /usr/lib/rpm/gnupg contact.html

This worked for me to import the keys however, I was still getting the error and was unable to get updates. Marcus pointed me to the /var/log/YaST2/y2log where I found out that the homedir that YOU was using was /var/lib/YaST2/gnupg, not /usr/lib/rpm/gnupg. The trustdb.gpg in /var/lib/YaST2/gnupg was corrupt so I coppied the /usr/lib/rpm/gnupg/trustdb.gpg to /var/lib/YaST2/gnupg and re-imported the keys:

# cd /var/lib/YaST2/gnupg

# wget http://www.novell.com/linux/security/contact.html && gpg --import \

      --homedir /usr/lib/rpm/gnupg contact.html

After that, I was able to run YOU and get all the updates. Cool. I don’t know what caused the corrupted trustdb.gpg. I have installed several 9.3 machines and had not had the error before. But it seems that others have seen this error so maybe this account will help someone besides me.

Linux none

Comments

Written by Pedro Zenon about 7 years ago. Reply

Hi, I have a problem on SuSE 9.3 when i tried to login, the error is that i can’t see the kdm login screen I saw a white login screen with an error that tell me

ACPI-0484:*Warning:Error gettimg cpuindex for acpiid 0×1
linux ifup:No configuration found for sit0
Written by Kevin Taylor about 7 years ago. Reply

Man, you are a lifesaver, I ran into this problem as well and couldn’t figure it out from the error either. Thanks a ton for posting this fix up, it saved me a ton of time getting YOU working again. If I could only find someone who knows how to fix the flaky name resolution problems with are related to KDE, I’d be golden on 9.3. But this fix was #1 on my list and I appreciate the tip!

-Kevin
Written by marc about 7 years ago. Reply

Kevin,

I’m glad it helped you out. That’s exacly why I posted it. 8^) !!!
Written by Israel J. Pattison about 7 years ago. Reply

Hi marc,

I’m having a slightly different problem. When I upgraded my IBM Thinkpad from SuSE 9.2 Professional to SuSE 9.3 YaST Online Update still thinks the system is at 9.2. The /etc/SuSE-release file shows 9.3 and all of the system graphics show 9.3 — it’s only YOU that still thinks where running 9.2. I’ve been googling on this problem, and I haven’t found any answers.

Israel J. Pattison
Written by Martin about 7 years ago. Reply

Hi Israel,

try to change all occurences of ’9.2′ in the file /var/adm/YaST/ProdDB/prod_00000002 into ’9.3′.

I found this in another board having run across the same problem.

Cheers.
Written by Nolan Jurgens about 7 years ago. Reply

If the above doesn’t work I would recommend using SuSE’s server instead of one of the other mirrors. (ftp.suse.com/pub/suse) For some reason none of the other mirrors would work for me.
Written by Wayne Monfries about 7 years ago. Reply

I had the same problem as Israel with my thinkpad. Changing just the prod_00000002 file didnt work for me (although I only restarted YOU and not the whole Yast Control Center). I ended up backing up /var/adm/YaST and copying the whole of /var/adm/YaST from a 9.3 machine I had done a fresh install on – and that worked (I did restart the whole Yast Control Center this time though).
Written by Anthony about 7 years ago. Reply

This fixed the YOU 9.3 thinking it’s 9.2 deal for me–
copy /var/adm/YaST/InstSrcManager/ISCACHE0×00000001/DESCRIPTION/description
to
/var/adm/YaST/ProdDB/prod00000001
and then delete
/var/adm/YaST/ProdDB/prod00000002
YOU will now update using 9.3 Patches
Written by J about 6 years ago. Reply

DNS migh be fixed up by disabling ipv6 if your DSL router is brain dead.
I found Konqueror worked, but Firefox and Mozilla and SuSe update did not.
Probably different resolver code in the Konqueror.

# echo “alias net-pf-10 off” >> /etc/modprobe.conf.local

reboot
Written by J about 6 years ago. Reply

I’m also battling with the gpg problem. However, in my case, I think it will be fixed
after the next reboot.

gpg –list-keys

complained a lot about a time-warp (clock problem)

I found the date on my system was Fri Jan 2 15:53:21 EST 1998
and that was obviously a result of a BIOS upgrade just before the install.
During the install – it told me there was a problem with the security key.

I plain forgot or didn’t think to check the BIOS date and time after the
flash upgrade, and launched into a re-install (of existing SuSE) without
checking the time.
Written by -.mag about 6 years ago. Reply

I had this same issue. I was using autoyast and have been installing suse on alot of servers (20+) and was able to correlate that the time setting was too far off on the server. 2000 when it should have been 2005. I changed the date of the server and the issue with the signature check disappeared.
Written by shridhar upadhyaya about 6 years ago. Reply

Hi!
I installed Suse 9.3 on my dekstop and got the same problem with YOU: unable to connect to server. My DSL connection was working fine, so there must be a some other reason.

How can I fix it? In my previous installations with Suse 9.3, this feature worked.

Any ideas?

Thanks,

Shridhar
Written by marc about 6 years ago. Reply

I had the same error as well. Changing the default YOU server worked.
Written by Michael Radziej about 6 years ago. Reply

This problem can be created by using the “system update” icon in the YaST control center. This icon must not be used for updating to a different release, but only for an update within a release, like installing the newest KDE betas from http://ftp.suse.com. You can find some background at:
https://bugzilla.novell.com/show_bug.cgi?id=116339

Beginning with SUSE Linux 10.0, the icon will check this and will refuse to update to a new release. Unfortunately, this is still a possible pitfall for updating from earlier releases.
Written by Dom about 6 years ago. Reply

I had the same problem going from 9.2 to 10.0. Anthony’s method (replacing the prod_000000x) file worked fine for me.

Mecworks

Fixed YOU error on SuSE 9.3

Comments

Leave a Comment

Tags

Recent Comments

Please support this site:

This site

Achives

Friends