Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have lots of RHEL 5 servers subscribed to a Satellite 5.3 server (I know it's all old, not my choice). After I register servers, many of them seem to fall out and become inactive and require reregistration. This used to affect almost all our servers until I realized the NTP server we were using was way off (also not my choice) but I was able to rectify that and so now this only affects a few dozen. But I can't find a source and there are practically no log entries giving hints as to the problem.

share|improve this question
2  
If you're using Satellite then it's likely you have a paid Red Hat support subscription, open a case with your regional Red Hat support center and get same value from that... –  HBruijn Jan 31 at 15:27

1 Answer 1

The best way to ensure RHEL clients stay continually connected to an RHN Satellite server is to run the OSAD daemon (osad) on each client and osa-dipatcher on the Satellite server.

You can install OSAD on the clients by subscribing them to the rhn-tools channel and running:

yum install osad`
chkconfig osad on
service osad start

On the RHN Satellite server, just make sure the osa-dipatcher package is installed and that the service is running.

More simply you can create a cron job on the clients to periodically check in with the Satellite server. Something like the following would do great:

#!/bin/sh
# Check for scheduled actions
perl -le 'sleep rand 9000' && rhn_check >& /dev/null
# send latest system info
perl -le 'sleep rand 9000' && rhn-profile-sync >& /dev/null

Lastly, if a client ever stops checking in, just run rhn_check manually for troubleshooting purposes.

Hope this helps!

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.