Are there best practices for monitoring and managing HVR remote listener processes?
Local Data Processing
Yes. This document's intent is to describe HVR's best practices for how to monitor and manage HVR's remote listener process (or agent as it is referred to) for both Linux and Windows environments.
The best practice for monitoring and managing HVR remote listener processes on Linux is to run the agent under systemd, it will take care of starting the agent on demand.
If systemd is not available on your operating system (typically a non-Linux Unix), then alternatively create an xinetd or inetd managed service.
Xinetd is an open-source daemon that manages the Internet connections on many modern Unix and Unix-like servers. Xinetd is not always installed on all systems see http://unixadminschool.com/blog/2011/07/inetd-vs-xinetd-in-linux/.
Creating an HVR listener service for either systemd or xinetd are documented here: Installing HVR on Unix or Linux
Additionally, a ‘how to’ with systemd, xinetd, inetd examples can be found here:
- How To: start hvr as a service using systemd in linux?
- How To: start hvr as service using xinetd in linux?
- How To: start hvr as a service using inetd in linux?
Both the systemd and the xinetd mechanisms for creating an HVR listener service will ensure the services are started automatically after a system reboot. For how to set up auto-starting HVR on Linux/Unix after a reboot see Auto-Starting HVR Scheduler after Unix or Linux Boot
We have had some reports where initial connections to HVR on remote Linux machine work OK, but after a certain number of simultaneous connections (e.g. 10), the following error occurs and recommend the below, see F_JT04CA Extra Connections Cause Error Starting Remote Child Process Failure
A Maintenance Job can catch that error and alert via Email/Slack/SNMP. See How To set up a slack channel for alert
The best practice for monitoring and managing HVR remote listener processes on Windows is to run the agent as a Windows Service and have it auto-start. In addition, to autostart on Windows we recommend configuring an additional setup that if there is a failure of the process then via the service's Recovery tab have processes also restart. For more information, see Configuring Remote Installation of HVR on Windows.
- Access the Windows services and select the HVR scheduler job. Enable on the General tab, Startup Type: Automatic
- Then on the Recovery tab set to Restart the Service on failure as shown