- This topic has 28 replies, 4 voices, and was last updated 6 years, 11 months ago by
.
-
Posts
-
I just upgraded from Fedora 25 workstation to 26 workstation. I also updated to the latest version of NoMachine on both the Fedora machine and the Windows machine I’m trying to connect from. When trying to connect, the screen shows the “Connecting….” message for quite a while then goes to the error of:
“The session negotiation failed.
Error: Cannot create a new display, please contact your system administrator”
When I was in front of the Linux box, I have a desktop session running with no issues. I am working on getting a way to be able to send the server logs if needed, but currently am not able to. I do have the client side logs if needed though. Thanks in advance for any help that can be offered.
What desktop environment do you have on that fedora 26?
Do you try to connect to physical desktop or create new virtual desktop?
Could You provide output of “ps -ef | grep -i -E ‘wayland|xorg'”?The desktop environment is Gnome.
When connecting I initially get this message – “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?” I click on “Yes” and after that the screen shows the connecting message for a while, then goes to the error message
Below is the command and output requested.
ps -ef | grep -i E ‘wayland|xorg’
grep: wayland|xorg: No such file or directory
In case it helps, I also get the following when restarting the nxserver.
sudo /usr/NX/bin/nxserver –restart
NX> 162 Disabled service: nxserver.
NX> 162 Disabled service: nxnode.
NX> 162 Disabled service: nxd.
NX> 161 Enabled service: nxserver.
NX> 162 WARNING: Cannot find X servers running on this machine.
NX> 162 WARNING: A new virtual display will be created on demand.
NX> 161 Enabled service: nxd.
There should be “ps -ef | grep -i –E ‘wayland|xorg‘“.
From yours information’s, I’m expecting problem is that physical session is running on wayland.
According to this https://www.nomachine.com/fr/FR10N03221 you should disable wayland, restart whole system and try again.After disabling Wayland and rebooting, I get the connection and get to the login screen on the remote computer. When I try to log in, the screen starts flickering for a bit, then the connection drops and I get the following.
The connection with the server was lost.
Error is 5: Input/output error.
When you login to system, which desktop environment is set? (settings icon is right next to password field)
There should be option gnome-xorg, which must be used. Do you have access to that machine? Can you login there (with option gnome-xorg) and then try connect with NoMachine?
Output from command from earlier post will be helpful (situation when user is already logged).Sorry for the delay in my response. After logging in locally and selecting the gnome-xorg option, after logging in with NoMachine I get a message of “No available sessions on this server”.
Output of “ps -ef | grep -i E ‘wayland|xorg”
grep: ‘wayland: No such file or directory
bash: xorg’: command not found…
“grep: ‘wayland: No such file or directory
bash: xorg’: command not found…”
it is wrong because command is wrong,
“ps -ef | grep -i E ‘wayland|xorg” you miss dash before “E” . should be “ps -ef | grep -i –E ‘wayland|xorg‘“.Maybe use:
“ps -ef | grep -i -e wayland -e xorg”
or
“ps -ef | grep X”Check also maybe do you have any errors in ~/.xsession-errors or /var/log/Xorg.*.log?
Sorry about that. Here is the output of ‘ps -ef | grep -i -e wayland -e xorg’
gdm 1511 1465 0 14:26 tty1 00:00:00 /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
me 3209 3085 0 14:35 pts/0 00:00:00 grep –color=auto -i -e wayland -e xorg
And the output of ‘ps -ef | grep X’
nx 1168 1 0 14:26 ? 00:00:01 /usr/NX/bin/nxserver.bin –daemon
gdm 1511 1465 0 14:26 tty1 00:00:00 /usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
gdm 2710 1168 0 14:27 ? 00:00:00 /usr/NX/bin/nxexec –node –user gdm –priority realtime –mode 0 –pid 21
nx 2711 1168 0 14:27 ? 00:00:00 /usr/NX/bin/nxd
gdm 2724 2710 0 14:27 ? 00:00:00 /usr/NX/bin/nxnode.bin
me 3273 3085 0 14:36 pts/0 00:00:00 grep –color=auto X
When viewing ‘~/.xsession-errors’ I get the message below.
(process:2320): WARNING **: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: Could not connect: Connection refused
For the ‘/var/log/Xorg.*.log’ I have 4 different ones, is there a specific on I should look at
/var/log/Xorg.0.log /var/log/Xorg.1.log /var/log/Xorg.2.log /var/log/Xorg.9.log
Thank you.
For the ‘/var/log/Xorg.*.log’ I have 4 different ones, is there a specific one I should look at
Look at newest one.
Please check also file /usr/NX/var/log/nxerror.log for errors related with WMRunning, because process list looks ok.
In looking at the Xorg logs, the newest one I have is from Oct 5. I ran the command below and got the results listed to look for issues.
cat /var/log/Xorg.0.log | grep -E ‘(EE)|(WW)’
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 193.172] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
[ 193.244] (WW) Warning, couldn’t open module fbdev
[ 193.244] (EE) Failed to load module “fbdev” (module does not exist, 0)
[ 193.245] (WW) Warning, couldn’t open module vesa
[ 193.245] (EE) Failed to load module “vesa” (module does not exist, 0)
[ 193.898] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
The nxerror log is very long, so I took what looks like the last 2 entries from it.
Info: Handler started with pid 8118 on Tue Oct 24 16:28:53 2017.
Info: Handling connection from xxx.xxx.xxx.xxx port 50466 on Tue Oct 24 16:28:53 2017.
Info: Connection from xxx.xxx.xxx.xxx port 50466 closed on Tue Oct 24 16:29:01 2017.
Info: Handler with pid 8118 terminated on Tue Oct 24 16:29:01 2017.
kill: sending signal to 20617 failed: No such process
Usage: nxnode …
this command is intended to be used only by NX Server
or NX Workstation.
kill: sending signal to 32108 failed: No such process
kill: sending signal to 810 failed: No such process
kill: sending signal to 9474 failed: No such process
Usage: nxnode …
this command is intended to be used only by NX Server
or NX Workstation.
kill: sending signal to 14482 failed: No such process
kill: sending signal to 14487 failed: No such process
kill: sending signal to 21566 failed: No such process
kill: sending signal to 7688 failed: No such process
kill: sending signal to 22835 failed: No such process
kill: sending signal to 23711 failed: No such process
kill: sending signal to 23738 failed: No such process
kill: sending signal to 23780 failed: No such process
kill: sending signal to 28713 failed: No such process
22550 22550 06:01:26 361.446 HostWmRunning: WARNING! Giving up after 500 Ms.
Usage: nxnode …
this command is intended to be used only by NX Server
or NX Workstation.
Usage: nxnode …
this command is intended to be used only by NX Server
or NX Workstation.
Info: Handler started with pid 8887 on Thu Oct 26 11:49:18 2017.
Info: Handling connection from xxx.xxx.xxx.xxx port 34850 on Thu Oct 26 11:49:18 2017.
Info: Connection from xxx.xxx.xxx.xxx port 34850 closed on Thu Oct 26 11:49:25 2017.
Info: Handler with pid 8887 terminated on Thu Oct 26 11:49:25 2017.
Thank you.
I don’t see nothing wrong in that part of nxerror.log.
I will need logs (with debug) and another output of:ps awwxo uid,ppid,pid,sid,etime,comm,args
Please enable debug, restart nxserver (sudo /usr/NX/bin/nxserver –restart) and send server side logs to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098.
I will get the logs collected and sent. Here is the output of ‘ps awwxo uid,ppid,pid,sid,etime,comm,args’
This topic was marked as closed, you can't post.