Leaving agent debug logging enabled to capture intermitent issue
search cancel

Leaving agent debug logging enabled to capture intermitent issue

book

Article ID: 410082

calendar_today

Updated On:

Products

Autosys Workload Automation Workload Automation Agent

Issue/Introduction

We have an intermittent issue with an agent.
To debug it, support instructed us to add the below to the agentparm.txt
oscomponent.jvm.x.options=-Djavax.net.debug=all

We need answers to the following questions:

  • What specifically does this setting in the agentparm do (does it mean it will log in more details)?
  • Can the line be added at any time?
  • If the line is added now, could it be left in place for an extended period, for example, one month?
  • Would it be safe to leave it in the agentparm for an extended period, and would it cause any space or performance impact on the server?

Environment

Autosys 12.x
System agent 12.x

Resolution

When setting the following parameter in the agentparm.txt
oscomponent.jvm.x.options=-Djavax.net.debug=all

This will cause the agent to write out large amounts of debug information to the nohup.stderr /  nohup.stdout in a very short period of time, depending on how busy your agent is.
It is not recommended to leave this on, as it can cause the machine to run out of disk space, as these files do not roll over.

When adding this to the agentparm.txt, it will require a restart of the agent in order to take effect.

You can add this to the agentparm.txt  now with a # in front of it to comment it out, and then uncomment it and restart the agent when the issue is present again.

Support will not suggest leaving this enabled when not actively troubleshooting an issue you are experiencing at the moment, as it will have an impact on the agent and system.