Endpoint Administration Guide for Windows › Managing Policy Models › Automatic Rule-based Policy Updates › Update Subscribers › Policy Model Error Log File

Policy Model Error Log File

The Policy Model error log, which is organized chronologically, looks similar to this:

20 Nov 03 11:56:07 (pmdb1): fargo  nu u5  0  Retry
   ERROR: Login procedure failed (10068)
   ERROR: Cannot accept update from a non‑parent PMDB
   (pmdb1@name.company.com) (10104)

20 Nov 03 19:53:17 (pmdb1): fargo  nu u5  0  Retry
   ERROR: Connection failed (10071)
   Host is unreachable (12296)

20 Nov 03 11:57:06 (pmdb1): fargo  nu u5  560  Cont
   ERROR: Failed to create USER u5 (10028)
   Already exists (‑9)
 
20 Nov 03 11:57:06 (pmdb1): fargo  nu u5  1120  Cont
   ERROR: Failed to create USER u5 (10028)
   Already exists (‑9)

The Policy Model error log is in binary format; you can view it only by entering the following command:

ACInstallDir/bin sepmd ‑e pmdname

Note: Do not manually delete an error log (for example, with the UNIX rm command). To delete the log, only use the following command:

ACInstallDir/bin sepmd ‑c pmdname

Important! The error log in CA ControlMinder r5.1 and later versions has a format that is not compatible with the format of earlier versions. sepmd cannot handle error logs from these earlier versions. When you upgrade to a version that has this format, the old error log is copied to ERROR_LOG.bak; a new log file is created when you start sepmdd.

Example: PMDB Update Error Message

The following example shows a typical error message:

• The top line always consists of the date, time, and subscriber. The command that generated the error appears next, followed by the offset (in decimal format), which indicates the location of the failed update inside the updates file. Lastly, the flag indicates whether the PMDB retries the update automatically or continues without it.
• The second line shows an example of a major level message (what type of error occurred) and its return code.
• The third line displays an example of a minor level message (why the error occurred), and its return code.

Example: Error Message

A command may generate and display more than one error. Also, an error may consist of a major level message, a minor level message, or both.

The following error has only one message level:

Fri Dec 29 10:30:43 2003 CIMV_PROD:Release failed. Return code = 9241

This message occurs when sepmd pull attempts to release a subscriber that is already available.