System

Messages in the System category show errors and warnings which cannot be related to any of the other categories. This could be errors in one of the subsystems on which DME depends (for instance JBoss).

For more details about an error, click the + button in the Message header title. This will expand the message to include details about the error as posted by the DME subsystems.

A special Surveillance type of System messages exists. If enabled in Server configuration > Data, various additional parts of the system will be monitored, and any error messages will be formatted in a uniform and readable way. See Data. Log messages of this type may be directed to a different file than the system.log file - see Log4j setup for more information. The messages are generated in the following way:

Every 10 seconds:

Note that 10 seconds is the default setting - in Server configuration > Data you can change the interval.

1. The availability of the DME database is checked. If no connection to the database can be found, the following message of type FATAL is written to the log: DME database unreachable

   When the database becomes reachable again, a message with type INFO is written: DME database is reachable again

2. The availability of the DME Central Services is checked. If pinging the Central Services server yields no result, the following message of type ERROR is written to the log: Central Services is not responding *)

   When Central Services becomes reachable again, a message with type INFO is written: Central Services is responding again *)

   For both the database and the Central Services notifications, the log message is written once - five minutes after the database or Central Services server becomes unreachable. This is called the Report delay. The connection is tested every 10 seconds (the Run every-interval). The report delay and the run every-interval can be configured in Server configuration > Data. See Data.

   *) Please note that currently the message says, "Central Service is ..." instead of "Central Services is ...". This will be fixed in a future service pack.

Every hour:

1. The license usage is checked every hour. User and device license usage are checked separately.

   If 80% of device or user licenses have been used, a message of type WARN is written to the log: DME device/user license expiration warning. Used %d/%d , where %d/%d is the number of devices or users in use compared to the maximum permitted number of devices or users.

2. If 90% of device or user licenses have been used, a message of type ERROR is written to the log: DME device/user license expiration warning. Used %d/%d , where %d/%d is the number of devices or users in use compared to the maximum permitted number of devices or users.

   When the number of devices or users is once more under threshold (through the deletion of unused devices or the addition of more licenses), a message with type INFO is written: DME device/user licenses are again under the threshold

Every day:

1. The expiration date of the DME license is checked every day. If the license will expire within the next 60 days, a message of type ERROR is written to the log: DME license expiration warning. The license will expire in less than [x no. days] days, on [expiration date]

   When the license is renewed, a message of type INFO is written to the log: DME license expiration fixed.

2. The expiration date of the Apple Push Certificate for Apple MDM is checked every day. If the certificate is set to expire within the next 30 days, a message of type ERROR is written to the log: The Apple Push Certificate is about to expire. Expires on [expiration date]. Subject: [Certificate Subject]

   When the license is renewed, a message of type INFO is written to the log: The Apple Push Certificate has been updated.

For information about setting up log4j, see the next section.