Changes disabled

Forums / NoMachine for Linux / Changes disabled

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #14141
    chiamarc
    Participant

    Hello,

    I’m using NoMachine Server v5.2.11 on Fedora 23.  Whenever I click to make changes and enter the Administrator password, the NoMachine Preferences window starts a spinning icon and then tells me that authorization failed.  I am 100% sure that the correct password has been entered.  About 20 seconds later, the file manager pops up the Personal NX directory.  This is very strange behavior.  I’ve checked another forum post that suggests overwriting /etc/pam.d/nx with /etc/pam.d/ssh or /etc/pam.d/su.  I’ve tried this to no avail, even after restarting nxservice.  Here are some entries from /var/log/secure at the time of the authorization:

    Mar 24 12:32:56 mchiarin-z620 sudo: root : TTY=pts/4 ; PWD=/home/mchiarin ; USER=root ; COMMAND=list
    Mar 24 12:33:01 mchiarin-z620 sudo: mchiarin : TTY=pts/5 ; PWD=/home/mchiarin ; USER=root ; COMMAND=/usr/bin/su -l root -c pwd
    Mar 24 12:33:02 mchiarin-z620 sudo: pam_systemd(sudo:session): Cannot create session: Already running in a session
    Mar 24 12:33:02 mchiarin-z620 sudo: pam_unix(sudo:session): session opened for user root by (uid=0)
    Mar 24 12:33:03 mchiarin-z620 su: pam_systemd(su-l:session): Cannot create session: Already running in a session
    Mar 24 12:33:03 mchiarin-z620 su: pam_unix(su-l:session): session opened for user root by (uid=0)
    Mar 24 12:33:23 mchiarin-z620 su: pam_unix(su-l:session): session closed for user root
    Mar 24 12:33:23 mchiarin-z620 sudo: pam_unix(sudo:session): session closed for user root

    Here is output from /usr/NX/var/log/nxerror.log:

    No protocol specified
    83324 85763 12:49:53 463.048 HostWmRunningHelper: WARNING! Failed to open display ‘:1024’.
    No protocol specified
    83324 85800 12:50:24 496.151 HostWmRunningHelper: WARNING! Failed to open display ‘:1024’.

    And here is output from /usr/NX/var/log/nxserver.log:

    2017-03-24 12:51:57 527.090 83324 NXSERVER WARNING! Cannot check WM on display :1024 EAGAIN
    2017-03-24 12:51:57 527.443 83324 NXSERVER WARNING! checkLocalSession: cannot get Xauthority for session on display ‘1024’.
    2017-03-24 12:52:28 564.627 83324 NXSERVER WARNING! Cannot check WM on display :1024 EAGAIN
    2017-03-24 12:52:28 564.932 83324 NXSERVER WARNING! checkLocalSession: cannot get Xauthority for session on display ‘1024’.

    Any help is much appreciated!

    #14174
    Cato
    Contributor

    Hello chiamarc,

    Please gather client side logs after failed authentication attempt, following these instructions:

    https://www.nomachine.com/DT07M00098

    It would also be helpful to see the content of ‘/etc/pam.d’ directory.
    Send logs and tar archive of ‘/etc/pam.d’ to forums[at]nomachine[dot]com.

    #14244
    chiamarc
    Participant

    Hi Cato,

    I’ve sent the server/client logs and /etc/pam.d but my post above is regarding making changes on the server side. I can login via remote clients, I just can’t make changes to server-side options.

    Regards,
    Marc

    #14250
    Britgirl
    Keymaster

    Hi, the address is forum[at]nomachine[dot]com. Apologies for that. Can you send them again? I believe Cato was referring to the client logs on the server side.

    #14423
    chiamarc
    Participant

    Hello?  Any updates?  Any ideas?

    #14441
    Britgirl
    Keymaster

    Apologies for the delay in getting back to you. Developers have been busy with the recent release of 5.2.21. Logs didn’t show anything useful, so we will need to send you a debug package. Can you confirm if it’s 32 or 64bit please. The debug package we send you will be for the latest version assuming the bug is still present.

    #14435
    chiamarc
    Participant

    It’s been three weeks since my original post. I still haven’t figured this out. I need help.

    #14444
    Britgirl
    Keymaster

    As I’ve just mentioned, we’ll need to send you a debug version because 1) the logs didn’t show anything useful and 2) we haven’t been able to reproduce the problem despite our tests since you submitted the logs. I take it that you have updated to our latest release?

    #14468
    chiamarc
    Participant

    Hi Britgirl, yes I can confirm that the behavior still exists in 5.2.21-1 even after nxserver restart. I’m running on Fedora 23 64-bit. Thanks!

    #14542
    Britgirl
    Keymaster

    Check your inbox 🙂

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.