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.
Linux – I have servers that keep becoming inactive in RHEL Satellite 5.3
linuxredhatrhel5satellite
Related Topic
- Redhat – Need to Migrate Xen DomU to VMWare ESXi – RHEL 5.3/ESXi 4.1
- Redhat – After applying patches and rebooting, RHEL 5.3 hangs on udev
- Redhat – Is it possible to create a RHEL 5.7 channel based on updated (5.9) RHEL channels in Satellite
- Linux – way to get Satellite 5.3 to list which packages are installed on each system
Best Answer
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 andosa-dipatcher
on the Satellite server.You can install OSAD on the clients by subscribing them to the
rhn-tools
channel and running: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:
Lastly, if a client ever stops checking in, just run
rhn_check
manually for troubleshooting purposes.Hope this helps!