Forum Replies Created
-
Posts
-
Hello,
We’ve opened trouble report for this case: TR02S10068
Hello rubin,
It seems like nxnode terminates unexpectedly on Windows when SSH_AUTH_SOCK environment is set, we fail to create symlink and fail, this is the issue.
We will create a trouble report for it and we will link it in this thread.
However, SSH_AUTH_SOCK environment variable is used during ssh forwarding, but in your case you authenticate using NX protocol and password authentication, so it’s not quite clear where the SSH_AUTH_SOCK environment comes from.
It looks like SSH_AUTH_SOCK isn’t in the environment of nxnode process when the user is logged out and everything works fine, but the problem appears when ruben is logged in and we create nxnode process run as user “ruben” which for some reason has SSH_AUTH_SOCK in the environment. Could it be that processes run as user “ruben”, has by default SSH_AUTH_SOCK in the environment?
Unsetting SSH_AUTH_SOCK could be a workaround to avoid this issue.Hi jjgalvez,
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/DT10O00163In 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.
Hello,
Last reply didn’t show correct paths, here’s how it should be:
There are also session log files usually it shouldn’t take large space, but if you want to clean themyou can do it by:
rm -rf 'NX installation directory'/var/log/node/T-* rm -rf 'NX installation directory'/var/log/node/F-* rm -rf 'User home directory'/.nx/F-* rm -rf 'User home directory'/.nx/T-*and in case you are using latest release:
rm -rf 'User home directory'/.nx/node/F-* rm -rf 'User home directory'/.nx/node/T-*Hello,
To clear main log files you can simply run:
nxserver –logrotate
This will clean main log files, archive and save old logs under /usr/NX/var/log/logrotate/ directory.
Saved files will be greatly reduced in size, but if you want you can delete them after logrotate
procedure has finished.
It’s also possible to set automatic log rotation https://www.nomachine.com/FR01L02806
There are also session log files usually it shouldn’t take large space, but if you want to clean them
you can do it by:
rm -rf /var/log/node/T-*
rm -rf /var/log/node/F-*
rm -rf /.nx/F-*
rm -rf /.nx/T-*
and in case you are using latest release:
rm -rf /.nx/node/F-*
rm -rf /.nx/node/T-*
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.
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.
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.
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.
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.
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 0If it’s intended, than you should set password for that user using:
nxserver --passwd <user>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.cfgdos2unix /usr/NX/etc/node.cfgYou will have to install dos2unix, if it’s not available out of the box.
After that run:
/etc/NX/nxserver --restartAnd if problem still persists, than run:
/etc/NX/nxserver --debug enable serverReproduce 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.
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-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.