No available desktops after upgrading ESXi

Forums / NoMachine for Linux / No available desktops after upgrading ESXi

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #37233
    EddieA
    Participant

    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.

    #37281
    kroy
    Contributor

    If configuration on that Slackware wasn’t changed, there shouldn’t be a problem with creating the desktop. Are you able to run startx from your virtualization client? If not, that would indicate a problem with image after ESXi upgrade. If desktop started and after sudo /etc/NX/nxserver --restart you’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).

    #37302
    EddieA
    Participant

    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.

    #37304
    EddieA
    Participant

    Also, note that my environment is still configured as per:  https://forums.nomachine.com/topic/still-cannot-find-default-environment-after-tr09n07188-fix

    #37319
    kroy
    Contributor

    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”).

    #37333
    EddieA
    Participant

    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

    Username:eddie

    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'.

    
    Password:
    
    ********

    User authorized.

    eddie@The-Tardis:~$`

     

    Cheers.

     

    #37594
    Britgirl
    Keymaster

    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?

    #37610
    EddieA
    Participant

    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.

    Cheers.

Viewing 8 posts - 1 through 8 (of 8 total)

This topic was marked as solved, you can't post.