Page History

...

• As a first step check the Agent's log file agent.log and watchdog.log, see JS7 - Log Files and Locations.
  • Warnings and errors can be found from the output qualifiers WARN and ERROR in a log file.
  • Example
    • 2021-10-10T09:53:04,939 WARN js7.base.session.SessionApi - HttpAgentApi(https://apmacwin:4345): HTTP 401 Unauthorized: POST https://apmacwin:4344/controller/api/session => InvalidLogin: Login: unknown user or invalid password
• Due to log rotation log files of previous days are kept available in a compressed .tar.gz format on a daily basis, see JS7 - Log Rotation.
  • For Unix the zcat command can be used to directly access compressed log files.
  • For Windows compressed files have to be extracted, for example by use of 7-zip.
• Users should consider that an Agent instance can report problems related to other components such as Controller instances and JOC Cockpit. In this situation it is recommended to check the component's log files.
• Should warnings or error messages not be evident then users should do some research: the Product Knowledge Base and the Change Management System offer a search box, browsers offer access to search engines.
• Having completed analysis of a problem and being certain that the problem is related to a product defect and not to resources of the IT environment then
  • customers of a commercial license should use the Support Resources including the SOS ticket system.
  • users of the open source license are invited to use Community Resources.
• Should the agent.log file not provide sufficient information to reproduce a problem then users should consider to increase the log level, see JS7 - Log Levels and Debug Options.

...