Forum / NoMachine for Linux / Server restarts every 5 seconds
- This topic has 8 replies, 4 voices, and was last updated 7 years, 11 months ago by Britgirl.
-
AuthorPosts
-
May 10, 2016 at 11:53 #11264timschwabParticipant
I’m running 5.1.26 on CentOS 7 (1511), 64-bit. NX is stopping/restarting every 5 seconds.
For example, from nxserver.log:
2016-05-09 16:33:43 125.764 5417 NXNODE WARNING! nxclient –monitor with pid 16478 did not exit within 5 seconds. Killing process.
2016-05-09 16:33:43 127.028 5417 NXNODE WARNING! Process ‘/usr/NX/bin/nxclient –monitor –pid 3432’ with pid ‘16478/16478’ finished with signal 9 after 5,219 seconds.
2016-05-09 16:33:43 127.435 5417 NXNODE WARNING! nxclient –monitor exited with code [-1]. Restarting nxclient –monitor.
2016-05-09 16:33:43 478.321 16630 NXSERVER WARNING! Cannot write to FD#1.
2016-05-09 16:33:43 478.397 16630 NXSERVER WARNING! Error is: 32, ‘Broken pipe’.
2016-05-09 16:33:48 357.203 5417 NXNODE WARNING! nxclient –monitor with pid 16642 did not exit within 5 seconds. Killing process.
2016-05-09 16:33:48 358.387 5417 NXNODE WARNING! Process ‘/usr/NX/bin/nxclient –monitor –pid 3432’ with pid ‘16642/16642’ finished with signal 9 after 5,229 seconds.
2016-05-09 16:33:48 358.787 5417 NXNODE WARNING! nxclient –monitor exited with code [-1]. Restarting nxclient –monitor.
2016-05-09 16:33:48 707.618 16793 NXSERVER WARNING! Cannot write to FD#1.
2016-05-09 16:33:48 707.686 16793 NXSERVER WARNING! Error is: 32, ‘Broken pipe’.
2016-05-09 16:33:53 577.135 5417 NXNODE WARNING! nxclient –monitor with pid 16805 did not exit within 5 seconds. Killing process.
2016-05-09 16:33:53 578.621 5417 NXNODE WARNING! Process ‘/usr/NX/bin/nxclient –monitor –pid 3432’ with pid ‘16805/16805’ finished with signal 9 after 5,217 seconds.
2016-05-09 16:33:53 579.027 5417 NXNODE WARNING! nxclient –monitor exited with code [-1]. Restarting nxclient –monitor.
2016-05-09 16:33:53 901.945 16954 NXSERVER WARNING! Cannot write to FD#1.
2016-05-09 16:33:53 902.013 16954 NXSERVER WARNING! Error is: 32, ‘Broken pipe’.
– Tim
May 10, 2016 at 17:27 #11286brotechParticipantWe were not able to reproduce this problem on CentOS 7.2.1511. Could you enable logs in server and node configuration file, restart nxserver, reproduce the problem and then send to us whole /usr/NX/var/log directory to forum[at]nomachine[dot]com or attach them here (size is restricted).
Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.
May 13, 2016 at 15:38 #11305brotechParticipantHello Tim,
we received logs, and seems that problem is related to your network configuration.Could you share with us your /etc/hosts file ? Could be through mail again as in case of logs.
May 16, 2016 at 09:10 #11315timschwabParticipantI have attached the /etc/hosts file.
May 19, 2016 at 08:37 #11379BritgirlKeymasterCan you forward that to forum[at]nomachine[dot]com?
June 9, 2016 at 08:15 #11567timschwabParticipantAny ideas on a fix?
June 22, 2016 at 16:24 #11695fra81ModeratorHi,
we cannot reproduce this issue in our labs and the /etc/hosts file didn’t show anything abnormal.
We are preparing a patched library with debug logs to send to you, if you are willing to test it.
In the meanwhile, are you able to say what the ‘192.168.14.24’ address is? Is it the IP of the server where you are connecting to?
We found it in the following log, that is somehow related to your problem:
Warning: Refusing connection from ‘192.168.14.24’ port 36450.
June 27, 2016 at 13:24 #11718timschwabParticipantThat server is using DHCP. Nothing on that network has .24 now. I think 192.168.14.24 was the server with the problem…the server from which I provided logs.
I’ll be happy to try the patched lib when you have it ready.
December 28, 2016 at 09:31 #13295BritgirlKeymasterWe sent the package a while back and didn’t hear any further news. This topic will be closed. Make sure you update the software to the latest version. Any problems, please open a new topic.
-
AuthorPosts
This topic was marked as solved, you can't post.