Lost connection to lmgrd, heartbeat timeout expired, exiting. EXITING DUE TO SIGNAL 37 Exit reason 5
Lost connection to lmgrd, heartbeat timeout expired, exiting. EXITING DUE TO SIGNAL 37 Exit reason 5
Summary
Lost connection to lmgrd, heartbeat timeout expired, exiting. EXITING DUE TO SIGNAL 37 Exit reason 5
Symptoms
Occasionally, a vendor daemon may exit and then be restarted by the lmgrd immediately with the following debug log messages shown:
17:46:44 (demo) Lost connection to lmgrd, heartbeat timeout expired, exiting. 17:46:44 (demo) EXITING DUE TO SIGNAL 37 Exit reason 5 17:46:44 (demo) IN: "f1" user1@host1 (SHUTDOWN) 17:46:44 (lmgrd) demo exited with status 37 (Communications error) 17:46:44 (lmgrd) Since this is an unknown status, license server 17:46:44 (lmgrd) manager (lmgrd) will attempt to re-start the vendor daemon. 17:46:44 (lmgrd) REStarted demo (internet tcp_port 33381 pid 8157) 17:46:44 (demo) FLEXnet Licensing version v11.6.1.0 build 66138 amd64_re3 17:46:44 (demo) Server started on host for: f1 17:46:44 (demo) EXTERNAL FILTERS are OFF 17:46:44 (lmgrd) demo using TCP-port 33381
Resolution
If the symptom is observed only in rare occasions, the issue is probably due to the server machine being busy or under heavy workload. This can be true especially when license server is sharing same machine with other server processes (e.g. file server, print server).
Please consider moving the license server to a dedicated machine if the issue repeats frequently and causes considerable interruption of license service.
Other Possibilities
SIGNAL 37 error can be caused by having the localhost name associated with the ::1 IPv6 loopback address in the /etc/hosts file. This can cause communication problems between the license server daemon (lmgrd) and the vendor daemon, resulting in shutdown of the latter. If you have a line like the following in your /etc/hosts file:
::1 localhost ip6-localhost ip6-loopback please change it to ::1 localhost6 ip6-localhost ip6-loopback so that the localhost name is associated only with the IPv4 127.0.0.1 address. Please note that modifying this file requires administrative (root) privileges.
Increasing HEARTBEAT_INTERVAL value set in the license file in the server line might help in resolving the issue in certain scenarios.
Server system lands in hibernate/sleep mode and on revival, these errors will be seen. In case of moving the server time and date (more than the heartbeat duration), with a running server.
During Antivirus upgrades/reinstallation (when the previous mentioned exceptions get deleted for daemon and server PORTS).
