Should be installed now Blackrose1, althoug it seems that it did not uninstall first. That's why you had the file that was saved.


Try it and check the log file.


/var/log/up2date

I have tried everything in this thread about 10 times, but still cant
run the 'up2date --register' command. either from KDE or the console.

Program just hangs, until I kill it. Then get the following message:
There was an SSL error: Possible cause system time is wrong. bla bla bla

The system time is not wrong.... )-;

wget works to get files and Mozilla works half the time, so I have
connectivity. Mozilla loads some pages, but not others. Loads Yahoo.com
but not google.com. Loads the front page here, but not the forums or FAQ.

Can get to about 1/2 of redhat's site....

Have forced install of the up2date-*, db4-*, openSSL* rpms. No help.
Tried with both the 2.4.20-6 and 2.4.20-6smp kernels. Same.

Was half way thru setting up 2.4.20-8smp kernel when I got all fed up
with having to recompile and install the network card drivers for the nth
time and yanked the plug and came here.

Machine is P4 2.4c on Asus P4P800mb. Pretty sure there is no problem
with the hardware or LAN as I am using the Win98 install on the C:
drive to post this. (Linux has the D: drive. grub works fine)

Any ideas ? I am at a loss.

The up2date should have been updated not force installed, I'm not sure what that did if anything with the old one.

The problem where we were force installing the up2date was on a system where it's already been updated.

Anyway it sounds like you have other issues that should be fixed first, then see if the problem with up2date still exists.


The first thing to check is DNS

look at /etc/resolve.conf and run dig with the nameserver ip addresses in the file..

david@zeus david]$ cat /etc/resolv.conf
nameserver 209.63.0.2 #kppp temp entry
nameserver 207.173.86.2 #kppp temp entry


[david@zeus david]$ dig @209.63.0.2 google.com

; <<>> DiG 9.2.1 <<>> @209.63.0.2 google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48212
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 300 IN A 216.239.57.99
google.com. 300 IN A 216.239.37.99

;; AUTHORITY SECTION:
google.com. 290873 IN NS ns1.google.com.
google.com. 290873 IN NS ns2.google.com.
google.com. 290873 IN NS ns3.google.com.
google.com. 290873 IN NS ns4.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 117862 IN A 216.239.32.10
ns2.google.com. 117862 IN A 216.239.34.10
ns3.google.com. 117862 IN A 216.239.36.10
ns4.google.com. 117862 IN A 216.239.38.10

;; Query time: 359 msec
;; SERVER: 209.63.0.2#53(209.63.0.2)
;; WHEN: Sat Nov 15 16:17:59 2003
;; MSG SIZE rcvd: 206


[david@zeus david]$ dig @207.173.86.2 google.com

; <<>> DiG 9.2.1 <<>> @207.173.86.2 google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35349
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 300 IN A 216.239.37.99
google.com. 300 IN A 216.239.57.99

;; AUTHORITY SECTION:
google.com. 308296 IN NS ns1.google.com.
google.com. 308296 IN NS ns2.google.com.
google.com. 308296 IN NS ns3.google.com.
google.com. 308296 IN NS ns4.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 135496 IN A 216.239.32.10
ns2.google.com. 135496 IN A 216.239.34.10
ns3.google.com. 329781 IN A 216.239.36.10
ns4.google.com. 329781 IN A 216.239.38.10

;; Query time: 229 msec
;; SERVER: 207.173.86.2#53(207.173.86.2)
;; WHEN: Sat Nov 15 16:18:42 2003
;; MSG SIZE rcvd: 206


looks like DNS is working.

run ifconfig and look for errors..


[david@zeus david]$ /sbin/ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2855 errors:0 dropped:0 overruns:0 frame:0
TX packets:2855 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:125032 (122.1 Kb) TX bytes:125032 (122.1 Kb)

ppp0 Link encap:Point-to-Point Protocol
inet addr:208.186.45.99 P-t-P:207.173.3.83 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:1291 errors:0 dropped:0 overruns:0 frame:0
TX packets:1405 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:494448 (482.8 Kb) TX bytes:185148 (180.8 Kb)


check to see if you have a firewall and how it's configured.

check /var/log/up2date and /var/log/messages




Do you have a proxy server, router or anything else your going through on your end?

Thanks for the reply Dave, but it is still no go...

DNS looks ok. Same results with iptables on, or firewall disabled.
Pretty sure it isnt a router issue, as one of the 3 other machines I put
RedHat on in the last 2 weeks is on it also, and is running 2 UT servers
and ftp with no problems. All 3 other machines installed and ran
up2date just fine.
(AMD550, P3-800EB & P3-S 1266 systems)

Bit more info. When I attempt the cert update via that wget command, I
got a SSL Connectivity error.
I nuked the partition and reinstalled again, tried with both the smp and
regular kernels. Same on both.

Could this be a problem with the network card drivers ?
The P4 2.4c that is having this problem is in an Asus P4P800 mb.
It has an onboard LAN card. 3Com 3C940

The only thing that goes different with the install on the machine in
question it anaconda doesn't detect the eth0, and I have to install
the cards drivers 3c2000.o Tried 2 different versions of these...

It just seems too bizzare that it does get online, and loads some sites
but not others...

Next I am going to try disabling the onboard lan and throw a DLink or
3com 530tx card in there and see what happens.

If you have any other ideas, I am open to suggestions.
I was hoping to get an OS on that would use my chips HT feature.

Well I'll be. It is a hardware/driver issue. Just stumbled across this:

http://www.linuxquestions.org/questi...ighlight=3C940

Going to try the patched driver mentioned there. Up2date will probably
work once I get that installed and can get to google and rhn. (I hope)

Apt is great. The funny thing is the RH Up2Date Icon still works on the GNOME desktop, so I know exactly when to run Apt. Great stuff.

Just to add my experiences to possibly help others.

I have never been able to get RH9 up2date working on my works network, (uses NT server with MS Proxy server)

I recently built a Linux Server (RH9) at home and got up2date working ok after downloading the latest rpm's. Got all the latest updates no prob, but when I brought it into work and put it on the network here it failed to connect. I could http & https no problem but kept getting SSL errors with up2date. (the error where it suggests the clock is wrong!)

After trying just about everything I hit on the answer this week. I had enabled Proxy authentication and put username and password in, but I hadnt put the port number after the proxy IP.

I have spent a couple of months looking for answers to this on the net without success, so thought I would share this in case anyone else is having this problem. Ok so its a dead simple solution but sometimes the simple things cause the biggest problems.

WHEN SETTING UP UP2DATE ON A NETWORK USING PROXY SERVER THE PROXY ADDRESS SHOULE BE ENTERED AS:-

If your proxy IP is 192.168.1.1

and it uses port 80 for http/https

then in up2date enter the proxy address as:- 192.168.1.1:80

Another common problem that has been found is if your date/time is off by too much! Make sure your date and time are correct.

Right, alot of people run into "problems" with proxy servers. This usually is a misundertanding of how the proxy server handles different request, espeically from the up2date agent.

I recommend trying different settings with the up2date --configure (or rhn_register --configure) settings for proxy servers. There are so many different option. First and foremost, you need to get the IP addressort correct. Then you need to understand if there is uername/password authentication. These are the 2 things that most people get cuaght up on.

As an FYI, the up2date agent mostly connects on TCP on port 443 (some on port 80) but you need to make sure your proxy server allows this connection through.

Ok. I did something really stupid (relative newbie here). I read that I had to delete the contents of the
/etc/sysconfig/rhn/, which I did, then re-register my PC on rhn. This I did and then when to rhn, put in my regi info, downloaded the up2date files, both of them, then tried to install then with rpm -Fvh *.rpm.
I got the following.

1:up2date ########################################### [100%]

and that was it. When I try to run up2date, to get the updates, I get the following :

up2date --register

warning: can't access /etc/sysconfig/rhn/up2date
warning: can't access /etc/sysconfig/rhn/up2date-uuid
No rhnuuid config option found in /etc/sysconfig/rhn/up2date-uuid.

Obviously, I did something BAD. by deleting the files in the rhn dir.

When I click on the rhn button on the bottom of the page, first I get a bubble popping up saying "Unable to connect to rhn, then once I have clicked the button, I get a

Network Error -2: Name or service not known

error. This I don't understand since I am online and have loged onto the rhn. Then another window pops up asking me to register my sytem, which I click then nothing.

I have had a look on rhn, sure enough, my system isn't registered.

This whole thing is driving me wild.

Help someone please.

just download and install the up2date rpm


wget ftp://rpmfind.net/linux/redhat/updat...3.2-1.i386.rpm

rpm -Uv up2date-3.1.23.2-1.i386.rpm

or if install fails, this

rpm -iv --force up2date-3.1.23.2-1.i386.rpm

I have a bash problem.
I reinstalled rh8. three times.
and instead of wrestling w/up2date and all of it's issues, I tried to use apt instead.
I learned that I had an issue w/the rpm database and I went to rpm.org, followed instructions, rebuilt the database (twice) and now when I try to run apt nothing happens. I tested bash in root
w/
"bash test"
and get this back
test :/usr/bin/test: cannot execute binary file

Actually up2date has no problems in my opinion. Just need to download and install the new version.

`bash test` is an invalid command as far as I can tell

There is probably nothing wrong with bash on your system if that's the only issue.

I'm totally lost:

All methods didn't work, RPMs don't install, Manual Certificate Copying didn't work. Ignoring dependencies didn't work. I notice when I run rpm... that the prompt returns quickly without any output as if it did nothing. Same when installing certificates manually using install ...

Also, my computer fails to connect to any thing on the 443 secure http port from the web browser.

Any help is highly appreciated

P.S. I am new to Linux

I removed up2date and up2date-gnome using rpm -e. Then I ran the new packages by mouse double-click. they installed. Now the RHN icon shows red ! instead of the hated gray ? and says 69 updates are available. Fine so far, but when I click Launch up2date, no response. And still, I cant connect to any https from Mozilla.