When the CLN client connects to CLN to see if there are any updates available, or if any actions have been scheduled, it is considered as a checkin. If you see a message indicating that checkins are not happening, it means that the CLN client on your system is not successfully reaching CloudLinux Network for some reason. In this case you should check the following:
- Make sure that your client is configured correctly.
- Make sure that your system can communicate with CLN via SSL (port 443). You may test this by running the following command from a shell prompt: telnet xmlrpc.cln.cloudlinux.com 443.
- Make sure that the rhnsd daemon is activated and running with ‘ps ax | grep rhnsd’
If not – start it:
1/sbin/service rhnsd start
If these settings are correct and your system is still not checking in, the ‘Repairing a corrupt rpm database’ faq at [URL to appropriate CLN FAQ article, see below] , or get in touch with our technical support team.