1. The system on which up2date -l shows send mail is pointing at the satellite
server, correct?
2. What version of rhnproc are you running?
rpm -q rhnproc
Also, can you see the errata at the following url:
https://your.satellite.server.com/network/errata/errata_details.pxt?adv=RHSA-2003:073
If you can see the information about the errata, the information is being synced
correctly. Most likely, a needed background process is not being run.

That's ok. For now I'm going to close this bug, but please keep an eye on the
rhnproc process... if you see continued problems with it, please either reopen
this bug or file a new one, and we'll see what's affecting it.

We have the same effect again. After today's sync of our channels we're unable
to see the latest sendmail-Errata's although they have been synced.
Channel 7.2
Tue Apr 1 10:04:14 2003 - 149/152 Fetch successful:
sendmail-8.11.6-25.72.i386.rpm (304190 bytes)
See also satellite log attached.

Christian, can you tell me the name of the Red Hat technical contact that helped
install this Satellite? There appears to be a missing table in the db that is
causing the errata import process to fail.
It would also help if you can provide your Satellite DBA's contact information
as well.

Greg DeKoenigsberg was the Red Hat technical contact as far as I know. None of
our DBA's are involved with the DB on that Satellite Server.
The last person who got in contact with the DB on our side was me. I modified
the tables as instructed by your collegues while applying the last update.

Problem solved with the following actions:
apache stopped
rhnproc stopped
apache started
rhnproc started
satellite-sync run
After this we could see the updates again.
A fix that avoids this problem would be nice.

Christian, if you could send the log of that last sync that worked, I'd
appreciate it. It seemed as if you are missing a table in the db that should
have caused you problems. I want to verify that everything is working properly.

This seems to be an old legacy bug. I am closing this bugzilla out. If you are still encountering issues with this issue on your Satellite, please file a support ticket for continued assistance.
Regards,
Clifford.

Note

You need to
log in
before you can comment on or make changes to this bug.