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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

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)

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.

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:-

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 :

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

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.

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.