7.8. Checking Logs
rhsm.logshows every invocation and result of running the Subscription Manager GUI or CLI
rhsmcertd.logshows every time a new certificate is generated, which happens on a schedule defined by the
certFrequencyparameter in the
rhsm.logfile contains the sequence of every Python call for every operation invoked through the Subscription Manager tools. Each entry has this format:
YYYY-MM-DD HH:MM:SS,process_id [MESSAGE_TYPE] call python_script response
rhsm.logrelates to the Python script or function that was called, there can be multiple log entries for a single operation.
Example 11. rhsm.log Entry
2010-10-01 17:27:57,874 [INFO] _request() @connection.py:97 - status code: 200 2010-10-01 17:27:57,875 [INFO] perform() @certlib.py:132 - updated: Total updates: 0 Found (local) serial#  Expected (UEP) serial#  Added (new) <NONE> Deleted (rogue): <NONE> Expired (not deleted): <NONE> Expired (deleted): <NONE> 2010-10-01 17:27:57,878 [INFO] __init__() @connection.py:193 - Using certificate authentication: key = /etc/pki/consumer/key.pem, cert = /etc/pki/consumer/cert.pem, ca = /etc/pki/CA/candlepin.pem, insecure = True 2010-10-01 17:27:57,878 [INFO] __init__() @connection.py:196 - Connection Established: host: candlepin.example.com, port: 443, handler: /candlepin
rhsmcertd.logfile are much simpler. The log only records when the
rhsmcertddaemon starts or stops and every time a certificate is updated.
Example 12. rhsmcertd.log Entry
Fri Oct 1 13:27:44 2010: started: interval = 240 minutes Fri Oct 1 13:27:50 2010: certificates updated