How to recover host if client goes dark

[kabhijit]

Hello Devs,

Just started using NoMachine to see if it could work for me. At first glance its superb – very cool. However, there is one issue – if the client machine dies/disconnects, NoMachine will not allow a local user to login at all.

Steps to reproduce:
Install NoMachine and start server on the remote server (S). Install nomachine on the client (C) and connect – everything working fine. Now, lets assume Client machine dies. I simulated this by pulling the network cord. Now, if I go to the server physically, there is no (clean) way to be able to log in.

Expected Solution: There should be a way to disconnect/terminate the remote connection from a local terminal or non-gui interface OR there should be a timeout to close the connection if client has disappeared for (say) 60 seconds.

[Britgirl]

Hi and welcome 🙂

…there should be a timeout to close the connection if client has disappeared for (say) 60 seconds.

You’re right and there is.

Try setting the following key in node.cfg on the server side:

ProxyExtraOptions timeout=30

Something for the future, the current default timeout is too long and this will change in v9.

[kabhijit]

Perfect! Works exactly as expected. I’m on Ubuntu, and had to set the timeout in /usr/NX/etc/node.cfg

The timeout was set as 30seconds but in practice its more like 60s. Will need and see what balance to use so that I do not get spurious disconnects – especially when I am traveling.

[Britgirl]

It’s a bug on the server side, but this problem will be removed when v9 comes out. The default timeout will be 30 secs in version 9.

[Author]

Posts