4.1 Troubleshooting Event Monitoring

Changing the severity level for a local log from the Centralized Message Logging setting in Novell Control Center is not taking effect

Severity: ZENworks 7.3 Linux Management; Event Monitoring
Possible Cause: The Debug and Above message severity set using the command line interface takes precedence over the severity defined using the Centralized Message Logging user interface.
Action: Turn off the Debug and Above severity from command line interface using the following command: 
set debug-level off

SMTP mail is not working for the GMail server

Severity: ZENworks 7.3 Linux Management; Event Monitoring
Possible Cause: The Event Monitoring component of ZENworks 7.3 Linux Management does not support SMTP on a Transport Layer Security (TLS) server.
Action: For the GMail server, use only SMTP and Secure SMTP servers.

Unable to send e-mail to the specified e-mail address

Severity: ZENworks 7.3 Linux Management; Event Monitoring
Possible Cause: You might have defined filters or relays on the SMTP server.
Action: Clear the filters or relay that you have defined that block the SMTP packets from the ZENworks 7.3 Linux Management server.
Possible Cause: The authentication information you have provided in the E-mail Notification section of the Centralized Message Logging page is not correct.
Action: Ensure that the username and password you have specified are correct.

I am receiving unknown traps on the trap console

Severity: ZENworks 7.3 Linux Management; Event Monitoring
Possible Cause: The messagelogger.mib file is not compiled on the server.
Action: Compile the messagelogger.mib file located at /opt/novell/zenworks/share/messagelogger.

For example, if you want to compile messagelogger.mib on the Management and Monitoring Services console of ZENworks 7 Server Management, do the following:

  1. Right-click the ConsoleOne Site Serve object, then click Properties.

  2. In Properties of name of the Site Server dialog box, select the MIB Pool page.

  3. Click Modify Pool.

  4. In the Add/Remove MIBs dialog box, click Add, then select the MIB that needs to be compiled.

  5. Click Compile.

Unable to send the traps to the trap console

Severity: ZENworks 7.3 Linux Management; Event Monitoring
Possible Cause: You might have defined filters on the trap console.
Action: Clear the filters you have defined that block the traps generated from ZENworks 7.3 Linux Management server.
Possible Cause: The port number you have specified is not correct.
Action: To specify the correct port number:

  1. In the ZENworks Control Center, click Configuration.

  2. In Management Zone Settings, click Centralized Message Logging.

  3. Specify the correct SNMP port number of the trap console in the SNMP Trap section.

The log-level setting for a managed device is set to the default value info whenever the managed device is refreshed

Source: ZENworks 7.3 Linux Management; Event Monitoring
Action: Do the following:

  1. In ZENworks Control Center, click Configuration

  2. In Management Zone Settings, click Local Device Logging.

  3. Deselect the Log message to a local file if severity is check box.

  4. Click Apply.

After upgrading to ZENworks 7.3 Linux Management with IR2, the Number of backup files per day option does not display the new default value on the Local Device Logging page

Source: ZENworks 7.3 Linux Management; Event Monitoring
Explanation: After upgrading to ZENworks 7.3 Linux Management with IR2 from an earlier version of ZENworks Linux Management, the Number of backup files per day field displays the value that you selected before upgrading to ZENworks 7.3 Linux Management with IR2.
Action: After upgrading to ZENworks 7.3 Linux Management with IR2:

  1. In ZENworks Control Center, click Configuration > Local Device Logging.

  2. Select the Log message to a local file if severity is check box.

  3. (Optional) Change the value of the Number of backup files per day.