Gega

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 43 total)
  • Author
    Posts
  • in reply to: Failed to start NoMachine Server daemon #29892
    AvatarGega
    Participant

    Hello PeteFinerty

    In order to investigate we need you to collect and send logs to us. This article shows how to collect logs: https://www.nomachine.com/DT10O00163

     

    In your case it’s enough to collect server side logs.

     

    Please submit them to forum[at]nomachine[dot]com putting the title of your topic as the subject.

    Also please run /etc/NX/nxserver –list from terminal and show us the output.

    in reply to: NoMachine logs details #29889
    AvatarGega
    Participant

    Hello,

    Mainly nxserver.log is where nxserver/nxnode processes write their logs, and nxerror.log is where stderr of all commands run by nxserver/nxnode is redirected. You can control log level by altering SessionLogLevel in server.cfg/node.cfg or use –debug procedure to enable debug log level of nxserver, nxnode, nxwebplayer and nx display agent process. The debug level prints more verbose logs, while the informational log level (default) prints mainly warnings and errors.  Does this answer your question? If not, please provide more details about what you need to know.

     

    in reply to: NoMachine appears to be disabled #28268
    AvatarGega
    Participant

    Hello Aubert887,

    In order to investigate we need you to collect and send logs to us. This article shows how to collect logs: https://www.nomachine.com/DT10O00163

    In this case it’s enough to collect server side logs.

    Please submit them to forum[at]nomachine[dot]com putting the title of your topic as the subject.

    in reply to: Custom Script: failed with exit code 8 #27278
    AvatarGega
    Participant

    Hello tom5,

    Please check nxerror.log, it might show more detailed error from script. In order for session

    to work correctly it’s necessary for the custom script to finish with 0.

    It’s enough to use UserScriptAfterSessionClose. Do you set it in node.cfg or server.cfg?

    Please take into account that if you use server.cfg than script will be run as user ‘nx’,

    if you use node.cfg than script will be run as desktop owner.

    There’s also EnableLockScreen key in server.cfg, it’s designed to lock screen when

    user disconnects from physical desktop, if it fits your needs.

    AvatarGega
    Participant

    Please take a look at this article and see if it helps: https://www.nomachine.com/AR08N00898

    If not, then we will require new set of logs to continue investigation.

     

    About full screen, you could try enabling “Resize remote screen” and “Fullscreen” from settings>Display.

    AvatarGega
    Participant

    It looks like you’re using NX password database and we see “wrong password or login” error which wasn’t enough for us to understand without the debug (we are going to improve this :-))

    2020-05-05 21:29:20 227.284 31346 NXSERVER ERROR! Authentication with ‘NX-password’ from host ‘192.168.1.15’ failed. Error is ‘Wrong password or login’.

    From server.cfg:

    #

    # Enable or disable NX password DB:

    #

    # 1: Enabled. Use NX password DB to authenticate users.

    #

    # 0: Disabled. Use SSHD + PAM authentication.

    #

    # System administrators can enable a restricted set of users to con-

    # nect to NX Server by setting EnableUserDB to 1 and adding

    # those users to the DB. If user is enabled to connect, his/her pass-

    # word will be verified against the current PAM settings by the SSHD

    # daemon.

    #

    # If both ‘EnableUserDB’ and ‘EnablePasswordDB’ are set to 0, any

    # user being authenticated by SSHD account will be enabled to connect

    # to the system.

    # EnablePasswordDB 0

    If you want to use system authentication, than remove ‘#’ from that last line, it should say:

    EnablePasswordDB 0

    If it’s intended, than you should set password for that user using:

    nxserver --passwd <user>

    AvatarGega
    Participant

    Hello Zenith,

    It looks like server.cfg file contains Windows line endings. This might be inserted by the text editor you have used to modify server.cfg.

    Nxserver isn’t able to parse server.cfg in correct manner. To fix this you should run:

    dos2unix /usr/NX/etc/server.cfg

    dos2unix /usr/NX/etc/node.cfg

    You will have to install dos2unix, if it’s not available out of the box.

    After that run:

    /etc/NX/nxserver --restart

    And if problem still persists, than run:

    /etc/NX/nxserver --debug enable server

    Reproduce problem, collect logs and send it to us. Also please use another text editor for modifying server.cfg node.cfg, to avoid similar problems in the future.

    AvatarGega
    Participant

    Hello agsharath,

    Did you uncomment line with AcceptedAuthenticationMethods? Line should look like this:
    AcceptedAuthenticationMethods NX-private-key
    If it’s already that way, than please show us your log file /usr/NX/var/log/nxserver.log. You can submit it by sending it to forum[at]nomachine[dot]com-

    in reply to: Troubles with EnableLockScreen #25753
    AvatarGega
    Participant

    Hello ednaiul

    We’ve created TR for your case: https://www.nomachine.com/TR02R09553. Use the notify me utility to receive a notification when a fix has been released.

    in reply to: Log files permissions #25623
    AvatarGega
    Participant

    Hello ednaiul

    The reason behind that is that all users write logs to those files.
    We’re working on improvements to correctly manage files and eliminate all-writable files/directories from NX installation:
    https://www.nomachine.com/FR11Q03892.

    It’ll be included in an upcoming release.

    in reply to: Troubles with EnableLockScreen #25591
    AvatarGega
    Participant

    Are you logged into system as user ‘root’? Seems like we do have problem in that case, but it’ll need investigation to find if/how that could be fixed.

    in reply to: Troubles with EnableLockScreen #25584
    AvatarGega
    Participant

    Full logs could shed some light on what’s going on, so please send logs to forum[at]nomachine[dot]com set specify troubles-with-enablelockscreen as Subject.
    It’ll be good to know what are steps to reproduce this issue and how often that happens. I’d like to see also effective user of all nodes, and might be better to see all processes related to NX, so please send output of:
    ps -ef | grep nx
    along with logs.

    in reply to: Fail2ban nxauth vs nxd jail #25559
    AvatarGega
    Participant

    Hello,

    1)Yes by default we match all cases, you can change that if you don’t want to match all cases. More details are listed in nxauth.conf file.
    2)nxd.conf matches connections through NX protocol. So it’s purpose can be to restrict number of connections, by default we do that if there are more than 20 connections in last 5 seconds.
    3)nxd jail’s purpose is to ban remote hosts that are making too much connections in a very little timeframe, so we set it to 5 seconds.

    in reply to: Troubles with EnableLockScreen #25557
    AvatarGega
    Participant

    It’s not clear why we aren’t able to lock with dbus, but problem here is this part: HOME=/var/NX/nx, nxnode is run as desktop owner so home directory should be desktop owner’s home directory, so HOME shouldn’t point to /var/NX/nx, Are you maybe using UserNXDirectoryPath? It could be related to problem described in this TR: https://www.nomachine.com/TR09Q09406

    If that’s the case, then updating could help.

    in reply to: Troubles with EnableLockScreen #25511
    AvatarGega
    Participant

    Hello ednaiul,

    Logs might help to identify your issue, so please enable debug, than reproduce your problem, collect and send logs to us. This article shows how to collect logs: https://www.nomachine.com/DT10O00163

    Please submit them to forum[at]nomachine[dot]com putting the title of your topic as the subject.

Viewing 15 posts - 1 through 15 (of 43 total)