Only local users can connect to Fedora 28

Forum / NoMachine for Linux / Only local users can connect to Fedora 28

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #18503
    MarkG
    Participant

    I have a Linux machine running NoMachine server under Fedora 28.

    Users defined locally can connect and use the remote desktop. Users that are defined only in our AD cannot get a session. The same setup works with Fedora 26 where local and AD users can connect..

    NoMachine is version 6.1.6-9 on both client and server side.

    Client is a Fedora 26 host, server is a Fedora 28 host. (Using the same software under a Fedora 26 server works fine.)

    This happens with a virtual and physical desktop.

    “getent passwd <username>” and “id <username>” work in returning the user details.

    Is this a known problem? Is there any specific logs or command outputs I can supply?

     

    #18524
    Britgirl
    Keymaster

    Thanks for reporting. Are you able to enable debug and submit logs? From the client side, send us the client logs (~/.nx) and from the server side enable debug, reproduce the problem and gather the logs – instructions are available here: https://www.nomachine.com/DT10O00163#1

    You can either attach them within this topic or send direct to forum[at]nomachine[dot]com.

     

    #18561
    MarkG
    Participant

    Here are the requested log files.

    #18572
    Cato
    Participant

    Hello MarkG,

    Nxserver.log contains entries from nxnode process only. Did you increase log level in server.cfg too? Is nxserver process running? If it’s missing, run ‘<NoMachine_installation_dir>/bin/nxserver –restart’ command in terminal, as root user. Please check if you can connect as AD user using terminal SSH client or using NoMachine with SSH protocol. If it works, the problem is most likely related to PAM configuration.

    To reuse SSH PAM configuration with NX protocol:

    1. Start the terminal on server machine and su to root.

    2. Create the backup of NX pam configuration:

    cp /etc/pam.d/nx /etc/pam.d/nx.bak

    3. Overwrite current configuration with sshd settings:

    cp /etc/pam.d/sshd /etc/pam.d/nx

    4. Check if problem is still present.

    #18613
    MarkG
    Participant

    I tried with the pam file from ssh, but I get the same result. It looks as if the user is logged in by NoMachine, but NoMachine can’t actually start a session.

    I’ll try to get the full debug info.

    #18621
    MarkG
    Participant

    I have re-run with double checking that the log level is set to 7 on node.cfg and server.cfg.

    I have also tested using a local and a non-local user.

    With the non-local user nxnode throws an error in nxerror.log:

    nxnode.bin: malloc.c:4023: _int_malloc: Assertion `(unsigned long) (size) >= (unsigned long) (nb)’ failed.
    Error: Invalid user .
    and nxserver.log has a suspicious gap in timing and what looks like a restart. Local user:

    2018-06-07 14:27:18 257.097 32524 NXNODE   Service is [startsession], parameters is [user=mslocal&userip=10.210.52.41&uniqueid=BBCC63B5BF32A2A75338CD2886FCF962&display=1002&node_number=&server_name=loowmstitso2.intra.gsacapital.com&initiate=0&multinode_host=10.210.52.11&encryption_mode=3&udpPort=4011&connection=local&reconnect=1&rtremoteport=4413&rtremotehost=10.210.52.41&audio=enabled&microphone=enabled&server-printer-sharing=enabled&client-printer-sharing=enabled&server-usb-sharing=enabled&client-usb-sharing=enabled&server-disk-sharing=enabled&client-disk-sharing=enabled&server-network-sharing=enabled&client-network-sharing=enabled&client-smartcard-sharing=enabled&server-file-transfer=enabled&client-file-transfer=enabled&session-recording=enabled&local-recording=enabled&sessionName=Connection%%2bto%%2bloowmstitso2.intra.gsacapital.com%%2b%%25282%%2529&composite=1&agentUid=978&clipboard=client&mode=1&virtualdesktop=1&multipass=1&networkadaptive=1&node_attach_port=4000&backingstore=1&save=0&deblock=1&silence=0&session=Connection%%2bto%%2bloowmstitso2.intra.gsacapital.com%%2b%%25282%%2529&media=0&shadowtype=share&shadow_display=0&slave=1&geometry=N%%2fA&id=4ED20B4E6024AA5BEAC3A8CD6914A4C6&load=0&render=1&attach_session_type=physicalDesktop&agentm_display=1001&images=64M&attach_session_id=4ED20B4E6024AA5BEAC3A8CD6914A4C6&shmem=1&rtremoteport=4413&name=Local+display&security_extension=unknown&initiate=0&audioin=5%%3a5%%3aopus%%3a%%3a1&shpix=1&type=physicalAttachDesktop&tracking=0&rtiv=A11D17DA91C983E891D6C2A207723FC5&shadow_mode=2&local_cookie=******]
    2018-06-07 14:27:18 257.183 32524 NXNODE   Left in buffer is:
    2018-06-07 14:27:18 258.147 32524 NXNODE   libnxh::NXGetRandomString start.
    2018-06-07 14:27:18 258.286 32524 NXNODE   libnxh::NXGetRandomString stop.
    2018-06-07 14:27:18 292.519 32524 NXNODE   Chosen language en_US.
    2018-06-07 14:27:18 292.673 32524 NXNODE   NXOpen FD#8 – file /usr/NX/lib/perl/nxnode/NXScripts.pm with mode 0 and permissions 0 from main::nxrequire.
    2018-06-07 14:27:18 293.917 32524 NXNODE   NXClose FD#8 from main::nxrequire.
    2018-06-07 14:27:18 294.470 32524 NXNODE   Add cookie for local display: 0, 50b67370cce5e8dcb493d356b675928e
    2018-06-07 14:27:18 294.530 32524 NXNODE   Add cookie for kbd display: 3002, 13052D828764ECD374354EBAD1DF9ACA
    2018-06-07 14:27:18 294.572 32524 NXNODE   Add cookie for master display: 1001, E650E7C93E70F4178CF5AA14B06A498D

    For a non-local user:

    2018-06-07 14:01:15 376.282 29987 NXNODE   Service is [startsession], parameters is [user=mstitso&userip=10.210.52.41&uniqueid=A504C1F29D10451B09FB2A85CDC44A10&display=1002&node_number=&server_name=loowmstitso2.intra.gsacapital.com&initiate=0&multinode_host=10.210.52.11&encryption_mode=3&udpPort=4011&connection=local&reconnect=1&rtremoteport=4413&rtremotehost=10.210.52.41&audio=enabled&microphone=enabled&server-printer-sharing=enabled&client-printer-sharing=enabled&server-usb-sharing=enabled&client-usb-sharing=enabled&server-disk-sharing=enabled&client-disk-sharing=enabled&server-network-sharing=enabled&client-network-sharing=enabled&client-smartcard-sharing=enabled&server-file-transfer=enabled&client-file-transfer=enabled&session-recording=enabled&local-recording=enabled&sessionName=Connection%%2bto%%2bloowmstitso2.intra.gsacapital.com%%2b%%25282%%2529&composite=1&agentUid=978&clipboard=client&mode=1&virtualdesktop=1&multipass=1&networkadaptive=1&node_attach_port=4000&backingstore=1&save=0&deblock=1&silence=0&session=Connection%%2bto%%2bloowmstitso2.intra.gsacapital.com%%2b%%25282%%2529&media=0&shadowtype=share&shadow_display=0&slave=1&geometry=N%%2fA&id=151F81D90375C1C387D51C8B82098AC0&load=0&render=1&attach_session_type=physicalDesktop&agentm_display=1001&images=64M&attach_session_id=151F81D90375C1C387D51C8B82098AC0&shmem=1&rtremoteport=4413&name=Local+display&security_extension=unknown&initiate=0&audioin=5%%3a5%%3aopus%%3a%%3a1&shpix=1&type=physicalAttachDesktop&tracking=0&rtiv=937E74E73C44C7F149F05C523314397A&shadow_mode=2&local_cookie=******]
    2018-06-07 14:01:15 376.377 29987 NXNODE   Left in buffer is:
    2018-06-07 14:01:15 377.594 29987 NXNODE   libnxh::NXGetRandomString start.
    2018-06-07 14:01:15 377.728 29987 NXNODE   libnxh::NXGetRandomString stop.
    2018-06-07 14:01:15 418.653 29987 NXNODE   Chosen language en_US.
    2018-06-07 14:01:15 418.842 29987 NXNODE   NXOpen FD#9 – file /usr/NX/lib/perl/nxnode/NXScripts.pm with mode 0 and permissions 0 from main::nxrequire.
    2018-06-07 14:01:15 420.305 29987 NXNODE   NXClose FD#9 from main::nxrequire.
    2018-06-07 14:01:16 513.361 30011 NXNODE   Process initialized with arguments ”.
    2018-06-07 14:01:16 513.673 30011 NXNODE   Fedora 22 detected.

    #18960
    Britgirl
    Keymaster

    Hi, we are still unable to reproduce the problem, and the logs you submitted didn’t reveal the reason behind the issue. So, we have to ask you to submit some further information if you’re able to:

    – Using Valgrind to detect possible memory leaks in the nxnode program
    https://www.nomachine.com/AR09L00809

Viewing 7 posts - 1 through 7 (of 7 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.