NoMachine Support

Your questions answered

Knowledge Base

Searching in: Trouble Reports
Filter the search results
Last update:
Affects:
Product:
Status:
Searching in: Trouble Reports
ID: TR05R09697
Added on: 2020-05-20
Last update: 2020-05-26
Affects: 6
Due to be solved in:  6.x
Platform: All Platforms
Product: NoMachine Server
Severity: Serious
Status: Open
Users cannot connect to the Cloud Server, after that a failover occurred

This problem affects the recovering procedure in a NoMachine HA cluster.
When a failover occurs, if the startup procedure of the secondary server takes too long, NoMachine doesn't broadcast the cluster IP.
As a consequence, the secondary server (which should take the role of the active server) is not reachable and users cannot connect to the multi-server setup.

As a workaround, restart the secondary server manually.

On Linux and macOS, execute in a terminal on that host:
sudo /etc/NX/nxserver --restart 

On Windows, open a CMD console as administrator and execute:
cd C:\Program files (x86)\NoMachine\bin\
nxserver --restart

 

A symptom of this problem can be found in nxserver.log on the secondary server host:

2020-05-14 15:09:53 591.167 10165 NXSERVER WARNING! NXRunCommand: Timeout while waiting for command '/usr/NX/bin/nxexec /usr/NX/bin/nxexec nxrestart.sh' response.
2020-05-14 15:09:54 490.341 10165 NXSERVER WARNING! Process '/usr/NX/bin/nxexec nxrestart.sh' with pid '10197/10197' finished with signal 9 after 30,932 seconds. that problem the cluster did not rebroadcast IP again.

 

 


Notify me when the TR is closed.