Server log contains warning: "Worker Role Monitor received exception during ping"

Owned by Mike Murphy
Last updated: Oct 20, 2015 by Max Pinion (Deactivated)
2 min read

Issue

The Arellia Management Server will ping the Worker application pool every fifteen seconds to ensure that it stays awake to process events from clients and execute schedules. Misconfigurations can cause this ping to fail and the server will log a warning. 

Example 1:

"Worker Role Monitor received exception during ping: There was no endpoint listening at (Address)/WorkerService.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details."

Example 2:

"Worker Role Monitor received exception during ping: Could not establish trust relationship for the SSL/TLS secure channel with authority 'localhost'."

Solution

If you are seeing the second log message example above, then you need to modify the base local address for the worker by doing the following steps:

  1. In the Security Manager Console, click the Configuration tab.
  2. In the file library in the left pane, navigate to Settings > Configuration > Infrastructure > Configuration Settings and selecting the Arellia Management Server from the drop-down menu. 
  3. Change the Base local address to match the certificate that is being used for the HTTPS port. 
  4. Save the settings.
  5. When requiring HTTPS connections, you need to also change the BITS Uploads notification URL. 
    1. Open IIS Manager on the Server and navigating to Default Web Site > Ams > Agent > Uploads and selecting BITS Uploads under the Other section.
    2. Change the Notification URL to "../../Services/BitsUpload.ashx" and Save the settings. 
  6. If you are seeing the "no endpoint listening at ..." messages, then the first thing to check is that you can reach http://localhost/Ams/Worker/WorkerService.svc
    1. If you see a 404, verify that WCF Services HTTP Activation is enabled for .NET.



    2. If you see a 500 error, please contact support with a copy of your server logs and a screenshot of the 500 error you are seeing.