2009 Agent Services Logging

When an ActivePDF service or agent is run in Debug Mode, a log file is generated during the next conversion and maintains a log of all subsequent conversions.

When an ActivePDF service or agent is run in Debug Mode, a log file is generated during the next conversion and maintains a log of all subsequent conversions. Once generated, these logs can be reviewed to identify the cause of any errors encountered during the conversion process. This log file, APCore.log, is generated in the C:\WINDOWS\ActivePDF\Logs directory by default. This article serves as a guide for interpreting the log file entries for the 2009 Agent Services.

The following are the available Agent types for 2009:

  • 1 - Server
  • 2 - DocConverter
  • 3 - WebGrabber
  • 99 - Management (First Aid)

Each Agent Service that appears in the log file will be flagged with one of the following statuses:

  • 0 - Available
  • -1 - Stopped/Down
  • -3 - Non-responsive to Roll Call
  • -5 - Error (see log for details)

Upon start-up, the Agent Services flag any agents that are not offline (Stopped or Failed) as No Response. Services that receive no response then broadcast a "roll-call" to all agents on the local subnet, to confirm their availability. Once the agents respond, the Agent Service updates the list of agents with their current status.

Note: In order to support clustering, the Cluster Controller (the APCom, Agent and License Services) must have a Cluster License. For an agent service to become a member of a cluster, it must have a remote agent license.

The beginning of log indicates that inter-process communication has been initialized:

[11/25/2008 11:07:29](2508): Entering Initialize_MSG... [11/25/2008 11:07:29](2508):|AgentStatus [11/25/2008 11:07:29](2508): Leaving Initialize_MSG...

The following lines will indicates that the agent service "roll call" has been started:

[11/25/2008 11:07:29](2508): Entering AgentRollCall...
[11/25/2008 11:07:29](2508): Entering MDBPrePulse...

The next line indicates the number of agents found to be unavailable. In this example, two agents were unresponsive:

[11/25/2008 11:07:29](2508): Leaving MDBPrePulse(2)...

In this example log, no remote agents responded, but if they had, they would be listed after the previous line. Next, the local agents are listed (APFA is the First Aid or Mgmt agent):

[11/25/2008 11:07:29](2508): Reveille: SvrObj
[11/25/2008 11:07:29](2508): Reveille: DCObj
[11/25/2008 11:07:29](2508): Reveille: WGObj
[11/25/2008 11:07:29](2508): Reveille: APFAObj
[11/25/2008 11:07:29](2508): Leaving AgentRollCall...

Now that all agents and their statuses have been identified, the Agent Services can be made available for access. Notice the port number used for the local host is 56565. This is the default port number and can be changed, but the designated port must remain open at all times.

[11/25/2008 11:07:29](2508): APAgentService started.
[11/25/2008 11:07:29](2508): Base Address = net.tcp://localhost:56565/AP_AgentServer

Type 99 is the First Aid Agent, the remote site agent for managing the agents at that site:

[11/25/2008 11:07:29](2508): Entering SetAgentStatus(Type=99,Status=1)...
[11/25/2008 11:07:29](2508): Entering MDBStartAgent
[11/25/2008 11:07:29](2508): Updating Agent
[11/25/2008 11:07:29](2508): Leaving MDBStartAgent
(Type=99,Agent=tcp:// 1
[11/25/2008 11:07:29](2508): Leaving SetAgentStatus(Type=99,Status=1)...

Type 1 is the Server Agent and, in this example, the status has been updated to 1, indicating that the agent is now available.

[11/25/2008 11:07:30](2508): Entering SetAgentStatus(Type=1,Status=0)...
[11/25/2008 11:07:30](2508): Entering MDBStartAgent Type=1,Agent=tcp://
[11/25/2008 11:07:30](2508): Updating Agent Type=1,Agent=tcp://
[11/25/2008 11:07:30](2508): Leaving MDBStartAgent Type=1,Agent=tcp:// 1
[11/25/2008 11:07:30](2508): Leaving SetAgentStatus(Type=1,Status=0)...