January 30, 2022 at 10:28 #37233
Hi. I’m running NoMachine 7.7.4_1 on a Slackware 14.2 system on my ESXi.
Today I upgraded the ESXi from 6.7 to 7.0. Prior to the upgrade I had to move the Slackware system from one datastore to another using the VMWare web interface, because the RAID card for the original datastore isn’t supported on 7.0.
Following this, trying to initiate a connection from Windows 11, I firstly get the “Cannot detect any display running” as per normal. However, when selecting “Yes” to create the new display, I’m greeted with: “No available desktops on this server”.
Other than the underlying ESXi upgrade, there were no changes made to either the virtual Slackware 14.2 or the Windows 11 I connect from, which worked perfectly prior to the upgrade.
Looking in the NoMachine logs, I can’t see anything to indicate an error.February 1, 2022 at 16:19 #37281kroyContributor
If configuration on that Slackware wasn’t changed, there shouldn’t be a problem with creating the desktop. Are you able to run
startxfrom your virtualization client? If not, that would indicate a problem with image after ESXi upgrade. If desktop started and after
sudo /etc/NX/nxserver --restartyou’re still not able to connect, please send logs. First enable them, reproduce the problem and then collect logs (more instructions are there: https://knowledgebase.nomachine.com/DT11R00182).February 2, 2022 at 10:35 #37302
Yes, running startx from the virtual console starts up the KDE session.
Logs attached following an attempt to start a session from Windows.
I’m not trying to connect to an existing session, I’m using the ability for NoMachine to create it’s own.
Attachments:February 2, 2022 at 10:41 #37304
Also, note that my environment is still configured as per: https://forums.nomachine.com/topic/still-cannot-find-default-environment-after-tr09n07188-fixFebruary 3, 2022 at 16:41 #37319kroyContributor
Can you check what shows with
whereis "libpam.so.0"command, and htat are you able to log as local user with:
/usr/NXbin/nxexec --auth(execute that command as local user, do not use “sudo”).February 6, 2022 at 21:57 #37333
Slackware has never used PAM. Well not until 4 days ago when Patrick released 15.0.
After adding the missing /:
eddie@The-Tardis:~$ /usr/NX/bin/nxexec --auth
6620 6620 11:55:16 616 nxexecPAMOpen: ERROR! PAM library not found.
6620 6620 11:55:16 616 nxexecPAMOpen: ERROR! Error: 'libpam.so.0: cannot open shared object file: No such file or directory'.
Cheers.February 17, 2022 at 13:39 #37594BritgirlParticipant
what was the output of
whereis "libpam.so.0"? It’s not clear if you still have version 14.2 or 15 of Slackware installed. Are you still not able to connect?February 17, 2022 at 18:17 #37610
There is no output. There is no, and has never been any, copy of libpam on a standard Slackware release prior to the 15 released this month.
I’m still testing the latest version, so am currently running both 14.2 and 15.
This topic was marked as solved, you can't post.