PAM mount share drive causes “no desktop available on this service”

Forum / NoMachine for Linux / PAM mount share drive causes “no desktop available on this service”

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #48617
    Daniel 000
    Participant

    I have set up Linux Mint Cinnamon 21.3 fresh install with Active Directory and pam_mount connecting 1 share drive at login. This causes NoMachine (free edition) server to fail at being able to make a desktop available. The desktop icon stays greyed out and is not clickable. Guests can make a network connection to the PC but receive the error  “no desktop available on this service”. I have a monitor connected.

    I can confirm if I comment out the volume mount information in pam_mount.conf.xml, nomachine server can be restarted successfully and connected to.  Works great.

    I can manually mount a share drive without affecting the server or connection. It appears when the NoMachine server is starting up its attempting to run pam_mount and execution of the mount command is causing an error that isn’t clearly reported if at all. I see some errors relating to kerberos having preauthentication failure in auth.logs and if I enable debug on pam_mount there is a error reading login count from pmvarrun. I cant tell if they are relevant.

    I captured a nxserver.log at verbose logging level  of a successful start and with a failed start the comparison shows  In the failed log, multiple entries mention Redis communication issues and node status checks indicating unreachable, failed, or stopped. These are absent in the successful log.

    The failed log contains repeated messages like Cannot find node assigned to socket FD#26

    The failed log has several entries showing attempts to read the PID file and subsequently determining that the process is not running, e.g., Service 'nxserver': Read PID from file '/usr/NX/var/run/nxserver.pid': 28927. Process with pid 28927 is not running. These are not present in the successful log.

    I am but a determined novice, the above means nothing to me. As far as i can tell Active Directory and pam are set up correctly according to the tutorials i followed. It all works as intended with the exception of NoMachine.

    What can i do to get NoMachine working with pam_mount ? I am setting up a multi user environment and pam_mount is the only sensible option. Thanks in advance for any help, I would much prefer to use NoMachine over the alternatives if possible.

    #48627
    Britgirl
    Keymaster

    Hi, is it possible for you to send those logs to us so we can take a look? Send them to forum[at]nomachine[dot]com. Thanks.

    #48628
    Daniel 000
    Participant

    Hello Britgirl,
    Thanks for your attention, I have emailed you the log files.
    let me know if you want to see any others.

    #48641
    Britgirl
    Keymaster

    Hi, we have not received any logs yet.

    #48642
    Daniel 000
    Participant

    Hi Britgirl,
    Internet either absorbed the email I guess. Didn’t get a bounce back. in any case see attached.

    #48644
    Britgirl
    Keymaster

    Zip those files and then send to our forum email again.

    #48645
    Daniel 000
    Participant

    Oh, that’s the problem.
    attached.

    #48648
    Britgirl
    Keymaster

    Hi, the logs don’t report any errors. It’s better to send us the entire .nx folder from the server side with debug enabled first, before reproducing the problem again. Please follow the instructions here and re-submit, https://kb.nomachine.com/DT07S00243. Thanks.

    #48706
    Daniel 000
    Participant

    Hi Britgirl,
    Collected the logs according to the link- attached.

    #48781
    Daniel 000
    Participant

    Hello,
    Is anyone still looking into this?
    Surely I can’t be the only one to run into trouble with pam_mount and auto mounting of network shares…
    Thanks!

    #48788
    Britgirl
    Keymaster

    The logs are being analysed. Thanks for your patience.

    #48984
    Britgirl
    Keymaster

    Logs didn’t not reveal any clue as to why it’s happening. Can you update to 8.13 and send us fresh logs?

    Edit 10/10/24 – no logs received so investigation was stopped. Please update to the latest version, 8.14, and open a new topic if you continue to have issues., with logs and system journalctl.

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

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