Troubleshooting and Error Handling#

After the monthly schedule is run, a check is carried out for the generated report. If the report was generated successfully, no messages are sent and no notifications are generated. If the report was not generated successfully, a number of notification methods are available:

  • CLI login or health check. The message shows on the CLI console when logging in or when typing the health command:

    LICENSE REPORT: FAILED - Please run 'voss export type license_audit'

    The command to execute varies according to the release and license version:

    • Run: voss export type license_audit

    This message will continue to show until the report is generated successfully by running the command shown in the message.

  • Email Notification

    If email notification is configured, a notification is also sent to the configured address after the check fails. Refer to the notify emailrelay and notify add commands in the Platform Guide. (For example, notify add error mailto:sysadmin@mycompany.com)

    The message contains:

    ERROR: License file generation failed
The license audit report scheduled for <month> <year> was not successful.
Please contact your VOSS account manager.

  • SNMP Trap

    If SNMP is configured, a SNMP trap will be sent upon failure. An example SNMP trap that is generated when the report fails to run is show below - <month> <year> are variables in the example:

    May 23 02:01:00 robot-slave snmptrapd[18891]: 2018-05-23 02:01:00 <UNKNOWN>
[UDP: [192.168.100.3]:11814->[192.168.100.25]:162]:
#012iso.3.6.1.2.1.1.3.0 = Timeticks: (207758) 0:34:37.58
#011iso.3.6.1.6.3.1.1.4.1.0 = OID: iso.3.6.1.2.1.88.2.0.1
#011iso.3.6.1.2.1.88.2.1.1.0 = STRING:
"ERROR: License file generation failed"
#011iso.3.6.1.2.1.88.2.1.3.0 = STRING:
"The license audit report scheduled for <month> <year> was not successful.
#012Please contact your VOSS account manager. "
#011iso.3.6.1.2.1.88.2.1.5.0 = INTEGER: 1
#011iso.3.6.1.2.1.1.5.0 = STRING: "VOSS"

  • Action on failure

    In the case of a schedule failure, you should attempt to run the license audit by logging into the VOSS CLI and running the commands as detailed in the section Manual Command Execution above. If it continues to fail, then please raise a VOSS support ticket and contact your VOSS Account Manager or Global Services representative. If left to not run, this can lead to billing issues at reconciliation time, so it is best to ensure that it is running regularly as expected and address issues when it is not.