I made another attempt, this time checked the server-side system logs for any clues to the apparent ssh disconnect. Here are the pertinent lines:
In server /var/log/auth.log:
Dec 29 16:04:19 D2-FRIEDMAN nxexec: pam_unix(nx:session): session opened for user friedman by (uid=116)
Dec 29 16:04:19 D2-FRIEDMAN nxexec: pam_ck_connector(nx:session): cannot determine display-device
Dec 29 16:04:19 D2-FRIEDMAN nxexec: pam_unix(nx:session): session closed for user friedman
In server /usr/NX/var/log/nxd.log:
Info: Connection from 192.168.161.4 port 47542 accepted on Mon Dec 29 16:03:59 2014.
Info: Connection from 192.168.161.4 port 47542 process 16112 started on Mon Dec 29 16:03:59 2014.
Warning: Handler process 12651 terminated by signal 1, SIGHUP.
Info: Connection from 192.168.161.7 port 56285 process 12651 closed on Mon Dec 29 16:04:16 2014.
In server /usr/NX/var/log/nxerror.log:
Info: Handler started with pid 16112 on Mon Dec 29 16:04:00 2014.
Info: Handling connection from 192.168.161.4 port 47542 on Mon Dec 29 16:04:00 2014.
Info: Connection from 192.168.161.4 port 47542 closed on Mon Dec 29 16:04:19 2014.
Info: Handler with pid 16112 terminated on Mon Dec 29 16:04:19 2014.
In server /usr/NX/var/log/nxserver.log:
2014-12-29 16:04:10 262.537 16112 NXSERVER User ‘friedman’ logged in from ‘192.168.161.4’.
2014-12-29 16:04:16 169.986 12651 NXSERVER WARNING! Process (12687) finished with signal ‘9’.
2014-12-29 16:04:16 170.095 12651 NXSERVER WARNING! NXNodeExec: session node [12687] finished abnormally with exit code [9].
Starting cleaning procedure.
The time codes should give some indication of the sequence of events. The curious thing is the message
“cannot determine display-device”
from nxexec in /var/log/auth.log. Is any of this helpful?
– dhfx