Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
installed !M NxServer 3.3.0-15 LFE, but i cant connect to it.
I can ssh to my linux box from the client machine (Windows).
when I do (as root) nxserver --useradd adminos
I get:
[root@libox keys]# nxserver --useradd adminos
NX> 801 User: adminos uses SSHD authentication.
NX> 900 Adding public key for user: adminos to the authorized keys file.
NX> 900 Verifying public key authentication for NX user: adminos.
NXSERVER - Version 3.3.0-15 - LFE
Sat Feb 28 21:11:51 2009 running as user: 'root' (uid: 0, pid: 5591) on 'libox'
Info: selected user 'adminos' is authenticated (NXNodeExec)
Info: password for selected user is in 'unknown' mode (NXNodeExec)
Info: preferred auth method is '' (NXNodeExec)
Info: selected NX Node with host name '127.0.0.1', port '22' (NXNodeExec)
Info: selected su to access NX Node (NXNodeExec)
Info: nxssh command line is 'su adminos -c /usr/NX/bin/nxnode' (NXNodeExec)
Info: nxssh child pid is: 5624 (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 1000 NXNODE - Version 3.3.0-12
' (NXNodeExec)
Info: received message 'CONNECTED' from NX Node (NXNodeExec)
Info: sent request for service 'setkey' to NX Node (NXNodeExec)
Info: no parameter to send to NX Node (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 716 Public key is already present in: /home/adminos/.ssh/authorized_keys2.
' (NXNodeExec)
Info: received data in out channel from NX Node: 'NX> 1001 Bye.
' (NXNodeExec)
Info: received message 'BYE' from NX Node (NXNodeExec)
Info: closing nxssh's in, out, err FDs (flagfinished is: 1) (NXNodeExec)
Info: connection to NX Node finished correctly (NXNodeExec)
Info: selected user 'adminos' is not authenticated no password available (NXNodeExec)
Info: preferred auth method is 'publickey' (NXNodeExec)
Info: selected NX Node with host name '127.0.0.1', port '22' (NXNodeExec)
Info: selected publickey method to login NX Node (NXNodeExec)
Info: nxssh command line is '/usr/NX/bin/nxssh -nxservermode -l adminos 127.0.0.1 -p 22 -x -2 -i /usr/NX/etc/keys/node.localhost.id_dsa -o 'PubkeyAuthentication yes' -o 'RSAAuthentication yes' -o 'RhostsAuthentication no' -o 'PasswordAuthentication no' -o 'RhostsRSAAuthentication no' -o 'StrictHostKeyChecking no' /usr/NX/bin/nxnode' (NXNodeExec)
Info: nxssh child pid is: 5651 (NXNodeExec)
Info: received data in err channel from NX Node: 'ssh: connect to host 127.0.0.1 port 22: Connection refused
' (NXNodeExec)
Info: NX Node out channel was closed (NXNodeExec)
Info: NX Node err channel was closed (NXNodeExec)
Info: closing nxssh's in, out, err FDs (flagfinished is: 0) (NXNodeExec)
Error: no 'CONNECTED' message from NX Node (NXNodeExec)
NX> 595 ERROR: A fatal error occurred in NX Server.
NX> 595 ERROR: The exception id is: F7D4C5A0. To get detailed information about
NX> 595 ERROR: the error search for the string F7D4C5A0 in the system log
NX> 595 ERROR: file (usually '/var/log/messages').
NX> 500 ERROR: Last operation failed.
system log entries:
[root@libox keys]# tail -1000 /var/log/messages | grep F7D4C5A0
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) Error: no 'CONNECTED' message from NX Node
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) ssh: connect to host 127.0.0.1 port 22: Connection refused#015
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXNodeExec::exec('ping', '', 127.0.0.1, 22, 'adminos', 'publickey') called at handlers/nxserver.pl line 7419
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handler_user_checklogin('adminos') called at NXShell.pm line 373
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handle_command('checklogin', 'adminos') called at handlers/nxserver.pl line 7196
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handler_user_add('username', 'adminos', 'system', 0, 'administrator', undef, 'uid', undef, ...) called at NXShell.pm line 373
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) NXShell::handle_command('adduser', 'username', 'adminos', 'system', 0, 'administrator', undef, 'uid', ...) called at nxserver.pl line 5263
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) main:arse_args called at nxserver.pl line 4429
Feb 28 21:11:51 localhost NXSERVER-3.3.0-15[5591]: ERROR: (exception id F7D4C5A0) eval {...} called at nxserver.pl line 4426
[root@libox keys]#
I know this is an old thread, however, I found this thread while trying to track down the answer. The issue I found was that the hostname was not added to the /etc/hosts file. Once I added the hostname, NX worked fine.
I got same problem but I found that my linux password has been expired, once I change my password, nomachine started working as usual. Hope this may help someone looking for answer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.