Red Hat NETWORK SATELLITE 5.1.1 Installation Manual

Also see for NETWORK SATELLITE 5.1.1 - RELEASE NOTES: Release note Reference guide

Contents

Red Hat NETWORK SATELLITE 5.1.1 Installation Manual Manual pdf 51 page image

Chapter 7.47TroubleshootingThis chapter provides tips for determining the cause of and resolving the most common errorsassociated with RHN Satellite Server. If you need additional help, contact Red Hat Network support athttps://rhn.redhat.com/help/contact.pxt. Log in using your Satellite-entitled account to see your full listof options.In addition, you may package configuration information and logs from the Satellite and send them toRed Hat for further diagnosis. Refer to Section 7.6, “Satellite Debugging by Red Hat” for instructions.7.1. Log FilesVirtually every troubleshooting step should start with a look at the associated log file or files. Theseprovide invaluable information about the activity that has taken place on the device or within theapplication that can be used to monitor performance and ensure proper configuration. See Table 7.1,“Log Files” for the paths to all relevant log files:Component/Task Log File LocationApache Web server /var/log/httpd/ directoryRHN Satellite Server /var/log/rhn/ directoryRHN Satellite Server InstallationProgram/var/log/rhn_satellite_install.logDatabase installation - EmbeddedDatabase/var/log/rhn/rhn-database-installation.logDatabase population /var/log/rhn/populate_db.logRHN Satellite SynchronizationTool/var/log/rhn/rhn_server_satellite.logMonitoring infrastructure /home/nocpulse/var/ directoryMonitoring notifications /opt/notification/var/ directoryRHN DB Control - EmbeddedDatabase/var/log/rhn/rhn_database.logRHN Task Engine (taskomatic) /var/log/messagesRed Hat Update Agent /var/log/up2dateXML-RPC transactions /var/log/rhn/rhn_server_xmlrpc.logTable 7.1. Log Files7.2. General ProblemsTo begin troubleshooting general problems, examine the log file or files related to the componentexhibiting failures. A useful exercise is to issue the tail -f command for all log files and then runup2date --list. You should then examine all new log entries for potential clues.A common issue is full disk space. An almost sure sign of this is the appearance of halted writingin the log files. If logging stopped during a write, such as mid-word, you likely have filled disks. Toconfirm this, run this command and check the percentages in the Use% column: