ULM Agent times out when attempting to authenticate to the NS using a Persistent Connection (websockets)

book

Article ID: 172575

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

Customer notices that policies and tasks sent to the ULM agent never get executed.  Restarting the ULM agent doesn't resolve the issue.

Numerous errors will be shown in the '/opt/altiris/notification/nsagent/var/aex-client.log' on the client system.  Errors will be displayed stating that the agent and plugins 'failed to connect', 'cannot connect socket', 'failed to start communicaton' etc.

 

Cause

Two issues:

  1.  The ULM agent isn't failing over to http if websocket isn't authenticated.
  2.  Value set for the authentication is too low

 

Environment

ITMS 8.5

Resolution

Workaround:

  1. Increase the 'persistent connection timeout' in the NS Server communication profile (default is 60)

  1. If a profile update fails remove files from '/opt/altiris/notification/nsagent/var/securedb/nsagent/profiles' from the client system.
  2. Restart ULM agent.

 

 

Issue will be resolved in 8.5 RU1.

 

 

Attachments