September 3, 2021 at 07:39 #350887777777Participant
I connect to a Linux (RHEL 7) server from a Windows 10 desktop.
Here is what happened:
- I added starting an ssh-agent process (and adding a key to it) to my .bashrc on the Linux server.
- The server runs thousands of daily automated data processing jobs and each such job started an ssh-agent as a result of the above change.
- The result was that I exceeded the limit (~4000) on the number of processes, which I can run under my regular user name on the Linux server.
- The NoMachine window with the connection to the server went black and unresponsive.
- I closed the NoMachine window and tried to connect again only to get the following error message: “<No available sessions on this server>” and if I click on the error, I get the following message “The server was unable to make the local display available or access to the local display is disabled.” (I also get a “Logged in as myuser” message and a “Logout” link).
- I increased the maximum number of processes I can run on the Linux server under my regular username by a login to the server as root and disabled starting new ssh-agent processes.
- Now, I am able to ssh to the Linux server as my regular user but I am still not able to connect to the server using NoMachine (I get the same error messages as what I mentioned above). I get no option to start a new NoMachine session or terminate the existing potentially broken session.
Please, help me to understand what I should do now.
Is my only option to kill the nxserver processes and to restart it or there is a better solution?
I would prefer to save my NoMachine session since it has a lot of Windows open with a workflow setup in them.
Thank you very much for your help!September 3, 2021 at 15:19 #351007777777Participant
I have restarted the nxserver (i.e. service nxserver restart). Now, I am able to login to the Linux server again using NoMachine. I did save the /usr/NX/var/log content.September 6, 2021 at 10:51 #35127MthContributor
The restart of nxserver service was a proper solution to this issue. When something goes wrong with access to physical desktop, the nxserver
tries to restart the process responsible for mirroring the display up to 10 times, then it will block the physical access until the issue is resolved.
In this case restart is a proper way to regain access to physical desktop, especially if the issue was an exceeded process limit, it may have left the
NoMachine instance in an unusable or broken state.
You must be logged in to reply to this topic.