Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Red Hat Enterprise Linux v 2.1, v 3, v 4
Posts: 174
Rep:
Up2date Problems go here
I see a lot of people posting that have problems with up2date. As many of you know Red Hat's SSL certificate expired recently:
SSL Connection Errors
On August 28th, the SSL certificates used by up2date, rhn_register, and the RHN applet expired. Systems attempting to connect to RHN using an older certificate will receive 'certificate verify failed' errors. Please see the following instructions to download the latest versions of up2date and rhn_register.
*** Follow the instructions and you will be OK ***
The easiest thing to do is to download the RPMs you need into one directory, cd to the directory, and run rpm -Fvh *.rpm
Then you can test to make sure that everything works with 'up2date -p'
Common Issues:
1) You run the rpm command and it appears to complete but you still get errors.
1a) Check the file name. If you used IE to download your files sometimes this puts a '[1]' into the files name. Make sure you rename the files without the '[1]'.
2) I ran rpm -F up2date -or- rpm -F up2date-gnome and I get a dependency issue.
2a) If you have both up2date and up2date-gnome installed then you need to freshen then at the same time. The instructions above tell you a short cut, but the full command is:
rpm -Fvh up2date-3.1.23.2-1.i386.rpm up2date-gnome-3.1.23.2-1.i386.rpm
-or-
rpm -Fvh up2date-*.rpm
These are just some of the common things I've seen this week, add on as you like and reference this thread when people are having problems with this.
I have been really struggling with this new up2date thing for a few days now. I have been reading the postings about this, but with no joy. I am fairly new to RH and "rpm's" so I had to delve into the man pages concerning what commands to use. Until now I had tried various commands for instance:
rpm -Fvh up2date-3.1.23.2-1.i386.rpm
warning: up2date-3.1.23.2-1.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
error: Failed dependencies:
python >= 2.2.2 is needed by up2date-3.1.23.2-1
rhpl >= 0.81-2 is needed by up2date-3.1.23.2-1
up2date = 3.0.7.2 is needed by (installed) up2date-gnome-3.0.7.2-1
rpm -U up2date*.rpm....
Still nuffin!
So I tried: rpm -Fvh --nodeps up2date*
warning: up2date-3.0.7.2-1.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Preparing... ############################ [100%]
1:up2date ############################ [ 50%]
2:up2date ############################ [100%]
Success..
If any knows how this worked, or if I have totally "Totalled" my Linux box. Please let me know.. Also will this cause any unwanted future problems..
Lub0
Linux Lewis IS the heavyweight champion of the world.....
Today I finally got the chance to try and update up2date and I get this when I try to install the rpms.
error: cannot get exclusive lock on /var/lib/rpm/Packages
error: cannot open Packages index using db3 - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
Any help that can be offered is greatly appreciated.
1) I had a download problem with mozilla 1.5b. If I use the right mouse button to "save link target as", for example, rhn_register-2.8.27-1.7.3.i386.rpm is 393674 bytes with obviously the wrong checksum, as opposed to 196463 bytes (with the right checksum). A direct click works, with an indication the "the site has suggested that .... be handled as an attachment.
2) I already had rhn_register-2.8.27-1.7.3.i386.rpm installed, so rpm -Fvh did not work. (I still got an SSL error.) I used rpm -Uvh --force *.rpm. It needed to update the certificate. Then all is fine.
3) Thanks for posting this. I was wondering what was going on. Hey, the advantage is I have never had the RHN respond and download files so quickly, I think a lot of other people are in the same boat.. Now might be the time to attempt the up2date 7.3 -> 9.0 extravaganza I've been thinking of. On a duplicate install, of course.
Distribution: Red Hat Enterprise Linux v 2.1, v 3, v 4
Posts: 174
Original Poster
Rep:
Re: RH8 up2date....Success at last
Quote:
Originally posted by lub0
So I tried: rpm -Fvh --nodeps up2date*
warning: up2date-3.0.7.2-1.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Preparing... ############################ [100%]
1:up2date ############################ [ 50%]
2:up2date ############################ [100%]
Success..
I've had to use the --nodeps options a few times with different people. You should be OK. As long as you have python and rhpl installed: rpm -q python rhpl
your gold!
I too struggled with making the Up2date and Up2date-gnome rpms work; failed dependencies.
I noticed the little message at the bottom of the RHN annuncement saying that alternatively (but not recommended), I could just simply download the SSL certificate;
I have done a clean install of RH9 using Server options, but I cannot get the up2date working.
I have followed the instructions on RHN to download latest version of up2date, but it's still not working.
I did install RH9 as Server on this pc some months ago, but couldnt get up2date to work then either, so I wiped the disk and re-installed as Desktop and up2date was ok.
All this was prior to the certificate expiry, so I don't think it has anything to do with that.
If I run Terminal and type "up2date --register" it launches the up2date window, but as soon as I click on Forward to take me to step 1 the Terminal window fills with code, the last line of which is:-
This pc is connected to the internet using ISDN2 via an NT4 server running MS Proxy.
I am desperate to get this machine up and running so I can experiment with using it as a proxy server (squid I believe is the baby), then I can kill of the MS server - yipee!!
Any help would be greatly appreaciated thanks.
Dunx
p.s - I am a real Linux newbie, so simple instructions are very welcome, like "press the big button marked ON, use the keyboard to type in your user name and password, use the mouse to click on the red hat thingy, go up to System Tools, select Terminal, etc, ect - I think you get the drift!!!"
Hi, I am afraid I am a bit of a newbie myself, all I can say on this subject is I tried everthing to get my up2date to work, I kept getting an error like the one you got. I overcame the it with "rpm -Fvh --nodeps up2date*"
warning: up2date-3.0.7.2-1.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Preparing... ############################ [100%]
1:up2date ############################ [ 50%]
2:up2date ############################ [100%]
It installed fine and I was able to download all the updates.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.