- This topic has 7 replies, 3 voices, and was last updated 5 years, 9 months ago by
.
-
Posts
-
Hi,
I installed the NoMachine Enterprise Desktop-evaluation_6.4.6_9_x86_64.tar.gz on my linux server and NoMachine Enterprise Client_6.4.6_1.exe on my Window10. All the set up options are pretty much default on the server side. I was able to make connections and create virtual desktop session. Everything seems to be working for a couple of hours then I got disconnected. I could not reconnect to the server so I had to shutdown the server and restart. But the server fail to start with the error “No space left on device” Here are my nxserver.log
2019-02-26 23:53:47 203.304 30719 NXSERVER User ‘xxx’ logged in from ‘IP_blahblah’ using authentication method NX-password.
2019-02-27 01:16:11 014.975 27763 NXSERVER WARNING! Cannot check WM on display :0 ENOENT
2019-02-27 01:16:11 083.513 27763 NXSERVER Previous message repeated 2 times
2019-02-27 01:16:11 083.606 27763 NXSERVER WARNING! checkLocalSession: cookie not found for user ‘gdm’ display ‘0’ from file ‘/var/run/gdm/auth-for-gdm-QncxGZ/database’.
2019-02-27 01:16:11 089.210 27763 NXSERVER WARNING! Cannot write to FD#24.
2019-02-27 01:16:11 089.265 27763 NXSERVER WARNING! Error is: 28, ‘No space left on device’.
2019-02-27 01:16:11 090.910 27763 NXSERVER ERROR! Unexpected error while setting server FE8B8785B3E6E1F2EA045DE828C40BBA status to NotActive. cannot write on file ‘/usr/NX/var/db/running/sessionId{FE8B8785B3E6E1F2EA045DE828C40BBA}’: 28, No space left on device.
2019-02-27 01:16:42 043.809 27763 NXSERVER WARNING! Cannot check WM on display :0 ENOENT
2019-02-27 06:46:35 380.348 14185 NXSERVER WARNING! Cannot write to FD#11.
2019-02-27 06:46:35 380.422 14185 NXSERVER WARNING! Error is: 28, ‘No space left on device’.
2019-02-27 07:54:44 284.904 13882 NXSERVER User ‘xxx’ logged in from ‘IP_blahblah’ using authentication method NX-password.
2019-02-27 07:55:03 752.104 30719 NXSERVER WARNING! Cannot write to FD#12.
2019-02-27 07:55:03 752.179 30719 NXSERVER WARNING! Error is: 28, ‘No space left on device’.
2019-02-27 07:55:03 758.406 13882 NXSERVER WARNING! Cannot write to FD#15.
2019-02-27 07:55:03 758.474 13882 NXSERVER WARNING! Error is: 28, ‘No space left on device’.
2019-02-27 07:55:03 760.024 13882 NXSERVER ERROR! Cannot create session 0F2B583689BDD08B69A36357A53FBBDC: cannot write on file ‘/usr/NX/var/db/running/sessionId{0F2B583689BDD08B69A36357A53FBBDC}’: 28, No space left on device..
2019-02-27 07:55:03 760.450 13882 NXSERVER WARNING! Cannot open: /usr/NX/var/db/running/sessionId{0F2B583689BDD08B69A36357A53FBBDC}.
2019-02-27 07:55:03 760.491 13882 NXSERVER WARNING! Error is: 2, ‘No such file or directory’.
2019-02-27 07:55:03 761.078 13882 NXSERVER WARNING! Cannot open file ‘/usr/NX/var/db/running/sessionId{0F2B583689BDD08B69A36357A53FBBDC}’ for reading.
2019-02-27 07:55:03 761.114 13882 NXSERVER WARNING! Error is: 2, No such file or directory.
2019-02-27 07:55:03 761.623 13882 NXSERVER ERROR! Cannot save forward server pid. no key selected for table: running.
2019-02-27 07:55:04 055.097 13882 NXSERVER WARNING! Cannot open: /usr/NX/var/db/running/sessionId{0F2B583689BDD08B69A36357A53FBBDC}.
2019-02-27 07:55:04 055.178 13882 NXSERVER WARNING! Error is: 2, ‘No such file or directory’.
2019-02-27 07:55:04 056.060 13882 NXSERVER WARNING! Cannot open file ‘/usr/NX/var/db/running/sessionId{0F2B583689BDD08B69A36357A53FBBDC}’ for reading.
2019-02-27 07:55:04 056.103 13882 NXSERVER WARNING! Error is: 2, No such file or directory.
2019-02-27 07:55:04 056.760 13882 NXSERVER WARNING! Cannot open: /usr/NX/var/db/running/sessionId{0F2B583689BDD08B69A36357A53FBBDC}.
2019-02-27 07:55:04 056.798 13882 NXSERVER WARNING! Error is: 2, ‘No such file or directory’.
2019-02-27 07:55:04 057.330 13882 NXSERVER WARNING! Cannot open file ‘/usr/NX/var/db/running/ses2019-02-27 08:35:01 058.174 18705 NXSERVER Shutting down NoMachine server and services.
2019-02-27 08:35:01 067.630 26385 NXSERVER WARNING! Cannot write to FD#8.
2019-02-27 08:35:01 067.789 26385 NXSERVER WARNING! Error is: 32, ‘Broken pipe’.
2019-02-27 08:35:01 068.145 26385 NXSERVER ERROR! Authentication with ‘NX-password’ from host ‘IP_blahblah’ failed. Error is ‘Username is not in the expected format’.
2019-02-27 08:35:01 068.730 27763 NXSERVER Previous message repeated 32 times
2019-02-27 08:35:01 068.831 27763 NXSERVER WARNING! FE8B8785B3E6E1F2EA045DE828C40BBA nxnode died with exit code 15.
2019-02-27 08:35:01 073.276 37014 NXSERVER User ‘xxx from ‘IP_blahblah’ logged out.
2019-02-27 08:35:01 074.013 9407 NXNODE WARNING! Process ‘/bin/bash -c exec -a – /bin/tcsh -c ‘/etc/kde/kdm/Xsession startkde” with pid ‘9460/9460’ finished with exit code 1 after 50329,631 seconds.
2019-02-27 08:35:01 074.675 9407 NXNODE ERROR! Application terminated too early.
2019-02-27 08:35:01 077.952 32299 NXNODE WARNING! Process ‘/bin/bash -c exec -a – /bin/tcsh -c ‘/etc/gdm/Xsession gnome-session” with pid ‘32352/32352’ finished with exit code 1 after 71457,227 seconds.
2019-02-27 08:35:01 078.671 32299 NXNODE ERROR! Application terminated too early.
2019-02-27 08:35:01 079.473 9407 NXNODE WARNING! Process ‘/usr/bin/pulseaudio –high-priority=no’ with pid ‘9491/9491’ finished with exit code 1 after 50329,597 seconds.
2019-02-27 08:35:01 079.740 12297 NXNODE WARNING! Process ‘/usr/bin/pulseaudio –high-priority=no’ with pid ‘12380/12380’ finished with exit code 1 after 50124,091 seconds.
2019-02-27 08:35:01 081.191 27853 NXNODE ERROR! Cannot create directory: /usr/NX/var/run/nxdevice/D-1001-FE8B8785B3E6E1F2EA045DE828C40BBA.
2019-02-27 08:35:01 081.274 27853 NXNODE ERROR! Error is: 28, ‘No space left on device’.
2019-02-27 08:35:01 081.314 27853 NXNODE ERROR! setAudioForMaster: Error: Could not create ‘/usr/NX/var/run/nxdevice/D-1001-FE8B8785B3E6E1F2EA045DE828C40BBA’ folder. Error is: No space left on device
2019-02-27 08:35:01 083.375 32299 NXNODE WARNING! Process ‘/usr/bin/pulseaudio –high-priority=no’ with pid ‘32381/32381’ finished with exit code 1 after 71457,197 seconds.
2019-02-27 08:35:01 086.826 12297 NXNODE WARNING! Process ‘/bin/bash -c exec -a – /bin/tcsh -c ‘/etc/gdm/Xsession gnome-session” with pid ‘12350/12350’ finished with exit code 1 after 50124,137 seconds.
2019-02-27 08:35:01 087.182 12297 NXNODE ERROR! Application terminated too early.
2019-02-27 08:35:01 165.930 12297 NXNODE ERROR! Session application terminated abnormally
2019-02-27 08:35:01 219.797 12297 NXNODE WARNING! Cannot write to FD#2.
2019-02-27 08:35:01 219.865 12297 NXNODE WARNING! Error is: 28, ‘No space left on device’.
2019-02-27 08:35:01 295.694 9407 NXNODE WARNING! Process ‘/usr/NX/bin/nxclient –monitor –pid 9460’ with pid ‘9508/9508’ finished with exit code 1 after 50329,754 seconds.
2019-02-27 08:35:01 306.876 9407 NXNODE ERROR! Session application terminated abnormally
2019-02-27 08:35:01 341.660 32299 nNXNODE ERROR! Session application terminated abnormally
2019-02-27 08:35:01 385.341 9407 NXNODE WARNING! Cannot write to FD#2.
2019-02-27 08:35:01 385.419 9407 NXNODE WARNING! Error is: 28, ‘No space left on device’.
2019-02-27 08:35:01 394.285 32299 NXNODE WARNING! Cannot write to FD#2.
2019-02-27 08:35:01 394.355 32299 NXNODE WARNING! Error is: 28, ‘No space left on device’.
Anyone has the same issue? How can I solve this problems? Any hints would be appreciated!
Thanks,
H
2019-02-27 01:16:11 089.265 27763 NXSERVER WARNING! Error is: 28, ‘No space left on device’.
Looks like you don’t have enough room to even run a NoMachine session. What you need to do is have a clean of your server and make some space on your server host.
Hi,
The Linux server is a shared one and all the tools are installed as standard. So when I install NX, I am keeping all default setup. Like I mentioned, my co-workers and I were able to log in and use for a short while then everything stop. How do I check for space required? usages? Should I install NX to a different location so I can get more space?
Thanks,
System requirements necessary for NoMachine software products are provided on the download pages of each product, so for example, Terminal Server, https://www.nomachine.com/download/download&id=55, and also in the relative Installation Guide, “Prequisites” section. For TS we indicate general guidelines of 1 GB RAM and 195 MB free disk space.
NoMachine is installed by default in /usr/NX so you must guarantee that the partition where you have installed it has the amount of space that we indicate. If you can’t clear up space on that partition for whatever reason, you can install NoMachine in a different location (/opt/NX) on a different partition, see the Installation and Configuration Guide paragraph 3 for further details about that https://www.nomachine.com/DT04O00139#2.3. Simply make sure that the new location on the alternative partition has enough space.
This is a good article for how to clean up Linux systems with the help of command line tools.
I have pointed you to the Terminal Server product because you have posted in the Terminal Server category, but you mention that you have installed Enterprise Desktop on the remote host you are connecting to. That product does not have the terminal server functionality (virtual desktops on Linux), just thought I’d clarify that. If you are using that, then please refer to its own guide. All guides are available here: https://www.nomachine.com/all-documents in the Installation section.
Thank Britgirl. I re-install the software to a different partition but I got these errors when I restarted the server:
Attachments:
Hello hule,
Please check permissions to /tmp directory:$ LANG=ENG ls -la / | grep tmp drwxrwxrwt 16 root root 4096 Mar 14 10:56 tmpWe are using ‘/tmp’ directory to exchange descriptors, it should be accessible by every user.
Hi Haven,
Thank you for your help. I am able to make it work after changing permissions of the /tmp folder. However, I ran into some other strange problems:
I installed NoMachine on different servers and all of the virtual desktop work fine when users create GNOME virtual desktop session. However, when users select KDE, only 1 server works while the rest failed. It happenend only with some users. All installation of servers are the same configurations. Could you please take a look at the client log to see you could help?
Thanks,
Hule
Hi,
It looks like KDE is not starting properly. It’s hard to say only from client side logs.
You should check possible error messages in the user’s home directory ‘.xsession-errors’ file and system logs. Also ‘clients’ file in/usr/NX/var/log/node/F-C-<session ID>/could say what is going on with this application.
You could also try to startcustom session: console in virtual desktopand run KDE start command manually to check exact error message.
This topic was marked as solved, you can't post.