- May 17, 2019 at 7:01 am #19649Donna ZehlKeymaster
This document 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 xinetd, it will take care of starting the agent on demand.
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/
If xinetd is not available on your operating system (typically a non-linux unix), then the alternative method of creating a systemd managed service is recommended. Creating an HVR listener service for either systemd or xinetd are documented here: https://www.hvr-software.com/docs/Installing_HVR_on_Unix_or_Linux
Additionally, a ‘how to’ with an xinetd example can be found here: https://www.hvr-software.com/support-services/customer-resources/forum/topic/how-to-start-hvr-as-service-using-xinetd-in-linux/
Both the xinetd and the systemd 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 after a reboot see https://www.hvr-software.com/docs/Auto-Starting_HVR_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 link https://www.hvr-software.com/support-services/customer-resources/forum/topic/extra-connections-cause-error-f_jt04ca/
A Maintenance Job can catch that error and alert via Email/Slack/SNMP. See https://www.hvr-software.com/support-services/customer-resources/forum/topic/set-slack-channel-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.
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
- The forum ‘Expert Notes’ is closed to new topics and replies.