swillis0_0

[swillis0_0]

Apparently I’m just not going to get any help with this.

I’m now having the problem on three machines. The work around is to connect to the remote machine using my vpn and afterwards nomachine connects. Before I use the vpn when I try and connect using NoMachine I get the message that:

Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?

I select yes but then just get a black screen for a few seconds followed by disconnection. I suspect it’s a Linux problem but I was working for months and suddenly it just stopped working.

I submitted my logs as requested but then never got any response back.

[swillis0_0]

The situation has gotten worse. My work around no longer works. Now I have to connect to the box using my kvm, then once I do that and disconnect the kvm I can connect using NoMachine.`

[swillis0_0]

First, since I made the post I’ve built another folding rig and it exhibits the same behavior and I implemented the same work around, so now I have two rigs with the issue and one without.

First question, is that machine headless or runlevel 3? If not, which desktop environment
and desktop manager is in use? Also if they are running on Xorg or Wayland.

Not headless. Using the Mate desktop. I assume Xorg since I use the xorg.conf file to enable overclocking on my GPUs. When I connect successfully with nomachine or directly using a kvm I have the desktop.

Second question is: on that problematic machine in

/usr/NX/etc/server.cfg

configuration file, do you have uncommented entry

CreateDisplay 1

steve@fah03 ~ $ grep -i CreateDisplay /usr/NX/etc/server.cfg
#CreateDisplay 0
# When ‘CreateDisplay’ is enabled, specify the display owner and let
# When ‘CreateDisplay’ is enabled, specify the resolution of the new

This may cause a problem if the Xserver on the machine starts slower than NoMachine.
If that’s the case, please check if DefaultDesktopCommand key in

/usr/NX/etc/node.cfg

points to a proper session command or set CreateDisplay key to 0.

Next question is, what changes on that machine during this 30 seconds, do
physical sessions stay in login window, or there is automatic login to user’s desktop
enabled?

The 30 second delay I incorporated was just to make sure everything was started and stable. Automatic login is set up on both the problem rigs and the one that doesn’t have the issue.

Last thing you can try to add a key to server.cfg file:

checkLocalSessionDelay 0

and check if this help.

I tried that but OMG. I was able to connect with NoMachine but the desktop was all but unusable. Everything was huge and I didn’t have access to all the desktop. To make matters worse when I tried my kvm the screen was just blank. I was able to remove the line though. I’m guessing it used the motherboard video instead of the video card I’m set up to use.

I’ll try and get you those logs

[swillis0_0]

Thank you so much. I changed the cfg file and after a reboot all was good again.  Have a GREAT day!

[swillis0_0]

Thanks!  That was very helpful.

[swillis0_0]

Thanks but I already saw that but it didn’t answer my question.  It says nothing about how to connect to a specific machine.

[Author]

Posts