15.4.1 Checking log files

If a problem occurs, JP1/IT Desktop Management 2 - Agent acquires log data. Check the logs, and then take action. You can view the log contents for each PC.

JP1/IT Desktop Management 2 - Agent collects the following three types of log data about the distribution function, by using Remote Install Manager:

Agent basic log (USER_CLT.LOG file)
Log data for the entire JP1/IT Desktop Management 2 - Agent system (MAIN.LOG file)
Log data relating to automatic change of connection destinations (USER.LOG file)

Use a text editor to check log files because they are stored in JP1/IT Desktop Management 2 - Agent-installation-directory\log.

The following describes each log file:

Organization of this subsection

(1) Agent basic log
(2) Log data for the entire JP1/IT Desktop Management 2 - Agent
(3) Log data relating to automatic change of connection destinations

(1) Agent basic log

Basic log messages about agent operations are output to the USER_CLT.LOG file for each PC. We recommend that you first view this file to check the agent operation. This file contains simple messages indicating that each process has started or stopped. If a process fails, the cause of the error is also output to this file.

The following operations cause data to be output to the USER_CLT.LOG file:

Starting and stopping products and processes
Logon and logoff
Receiving a job execution request
Polling
Receiving and executing jobs
Downloading packages
Uploading a file
Automated registration of system configuration information
Registration in and unregistration from an ID group
Packaging
Internal error and application exception

For details about the file format and messages, see the manual JP1/IT Desktop Management 2 Messages.

To Page Top

(2) Log data for the entire JP1/IT Desktop Management 2 - Agent

Log data for the entire JP1/IT Desktop Management 2 - Agent system is collected in the MAIN.LOG file.

(a) Checking the MAIN.LOG file

For each PC, JP1/IT Desktop Management 2 - Agent acquires log data also in the MAIN.LOG file. The following shows the file format.

Figure 15‒5: MAIN.LOG file format

The meanings of message type and function type displayed in the MAIN.LOG file are as follows.

Table 15‒4: Message types in the Main.LOG file (for JP1/IT Desktop Management 2 - Agent)
Message type	Meaning
`Informational`	Information message
`Warning`	Warning message
`Error`	Error message

Table 15‒5: Function types in the Main.LOG file (for JP1/IT Desktop Management 2 - Agent)
Function type	Meaning
`Package`	During packaging (error in JP1/IT Desktop Management 2 - Agent)
`Install`	During installation (error in JP1/IT Desktop Management 2 - Agent)
`Setup`	During installation in GUI installation mode (error in JP1/IT Desktop Management 2 - Agent)
`TCP/IP`	Interface with TCP/IP
`System`	Interface with Windows
`User`	User log (output from the `LogFile` function of the installation script)
`Server`	During relay (error in JP1/IT Desktop Management 2 - Agent)

To Page Top

(3) Log data relating to automatic change of connection destinations

If the connection destination of an agent is automatically set or changed based on the file for connection destinations or information file for higher connection destinations, log data for each PC is collected in the USER.LOG file. The following shows the format of the USER.LOG file.

Figure 15‒6: USER.LOG file format

The following shows the meaning of message text displayed in the message is as follows:

Message text	Meaning
`Match [smallest-ID-address]-[largest-ID-address]:Change [old-connection-destination:product-type-of-old-connection-destination]->[new-connection-destination:product-type-of-new-connection-destination]`	The connection destination of the agent was changed normally. If the connection destination is the management server specified in the ITDM section of the file for connection destinations, the displayed product type is `itdm`. If the connection destination is the higher distribution system (using Remote Install Manager) specified in the DM section of the file for connection destinations or information file for higher connection destinations, the displayed product type is `netmdm` or `netmdmw`. If the connection destination is an Internet gateway server specified as an Internet gateway file for connection destinations, "`igw`" is displayed for the product type.
`Match [smallest-ID-address]-[largest-ID-address]:No Changed [existing-connection-destination:type-of-existing-connection-destination]^#`	The connection destination that has already been set matches the definition in the information file for higher connection destinations. The connection destination does not change.
`No Match IP Address List, No Changed [existing-connection-destination:` `product-type-of-existing-connection-destination]`	The IP address of the agent is not found in the range defined in the file for connection destinations or the information file for higher connection destinations. The connection destination does not change. If the connection destination is the management server specified in the ITDM section of the file for connection destinations, the displayed product type is `itdm`. If the connection destination is the higher distribution system (using Remote Install Manager) specified in the DM section of the file for connection destinations or information file for higher connection destinations, the displayed product type is `netmdm` or `netmdmw`.
`No Match IP Address List, No Changed`	The IP address of the agent is not found in the range defined in the Internet gateway file for connection destinations.
`Section is not available:"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the file for connection destinations or the Internet Gateway file for connection destinations, an invalid section is specified. The definition of this line is invalid.
`Not exist No.[order-of-the-item] Value: LineNo[line-number]`	In the line [`line-number`] in the file for connection destinations, the information file for higher connection destinations, or the Internet Gateway file for connection destinations, the `n`th item (`n` is indicated by `order-of-the-item`) is not specified. The definition of this line is invalid.
`IP Address is not available:"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the file for connection destinations, the information file for higher connection destinations, or the Internet Gateway file for connection destinations, an invalid IP address is specified. The definition of this line is invalid.
`Higher manager value is over 64 character:"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the DM section of the file for connection destinations or in the information file for higher connection destinations, more than 64 single-byte characters are specified as the connection destination. The definition of this line is invalid.
`Higher manager value is over 255 character:"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the ITDM section of the file for connection destinations, more than 255 single-byte characters are specified as the connection destination. The definition of this line is invalid.
`Higher manager value is over [maximum -number-of-haracters] character:"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the Internet Gateway file for connection destinations, more than maximum number of characters are specified. The definition of this line is invalid.
`Specified value is invalid:"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the Internet Gateway file for connection destinations, a value outside the valid range is specified. The definition of this line is invalid.
`Connection type value is not "netmdm" or "netmdmw":"[specified-value]" :LineNo[line-number]`	In the line [`line-number`] in the DM section of the file for connection destinations or in the information file for higher connection destinations, a value other than `netmdm` and `netmdmw` is specified as the device type of the connection destination. The definition of this line is invalid.
`Unable to decode encoded line :LineNo[line-number]`	The obfuscated string in the line [`line-number`] in the Internet Gateway file for connection destinations is incorrect and cannot be deciphered. The definition of this line is invalid.
`Match [smallest-ID-address]-[largest-ID-address]:Change Multicast IP Address [old-multicast-address]->[new-multicast-address]`	The multicast address of the agent was changed normally.
`Match [smallest-ID-address]-[largest-ID-address]:No Changed Multicast IP Address [multicast-address]^#`	The multicast address that has already been set matches the definition in the information file for higher connection destinations. The multicast address does not change.
`Multicast IP Address is not available:"[multicast-address]":LineNo[line-number]`	In the line [`line-number`] in the DM section of the file for connection destinations or in the information file for higher connection destinations, an invalid multicast address is specified. The definition of this line is valid, except for the multicast address setting.
`Multicast IP Address is under 224.0.0.0:"[specified-value]":LineNo[line-number]`	In the line [`line-number`] in the DM section of the file for connection destinations or in the information file for higher connection destinations, a multicast address smaller than 224.0.0.0 is specified. The definition of this line is valid, except for the multicast address setting.
`Multicast IP Address is over 239.255.255.255:"[specified-value]":LineNo[line-number]`	In the line [`line-number`] in the DM section of the file for connection destinations or in the information file for higher connection destinations, a multicast address greater than 239.255.255.255 is specified. The definition of this line is valid, except for the multicast address setting
`Use Option "MultiBoard Environment": Not Execution`	Automatic change of connection destinations is disabled because the network adapter has been configured during setup of the agent.
`Match [smallest-ID-address]-[largest-ID-address]:Clear SubHostName [registry-number]^#`	The connection destination that has already been set and that does not match the definition in the information file for higher connection destinations was deleted from the registry.
`Match [smallest-ID-address]-[largest-ID-address]:Clear SubServiceName [registry-number]^#`	For the connection destination that has already been set, the device type that does not match the definition in the information file for higher connection destinations was deleted from the registry.
`Match [smallest-ID-address]-[largest-ID-address]:Changed Multi Server Option [YES\|NO]`	Settings to perform polling for multiple higher systems were changed normally. If polling to multiple higher systems is performed, YES is displayed. If not, NO is displayed.

#: This message is not output for changes made by using the file for connection destinations.

To Page Top