[FreeNX-kNX] Port Assignment

Wed Mar 11 22:32:28 UTC 2015

Hey all.  Having issues with TCP port binding on the server from client.
Some quick specs:

Client:  Mac 10.9.5 running NoMachine v4.3.30
Server:  FreeNX version 0.7.3-6.el5.centos
NX Agent 3.4.0

When attempting to connect to one of our FreeNX servers, we're seeing the
following output:

-----Begin Paste-----
Copyright (C) 2001, 2010 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '2596'.
Session: Starting session at 'Wed Mar 11 17:21:38 2015'.
Info: Proxy running in server mode with pid '2596'.
Error: Call to bind failed for TCP port 35022. Error is 98 'Address already
in use'.
Error: Aborting session with 'Unable to open display
'nx/nx,options=/users/testuser/.nx/C-blade015-31022-B88B9BA2369A5DC1AB0AA53AA52EFC60/options:31022''.
Session: Aborting session at 'Wed Mar 11 17:21:38 2015'.
Session: Session aborted at 'Wed Mar 11 17:21:38 2015'.
NX> 1006 Session status: closed
NX> 596 Session startup failed.
rm: cannot remove
`/users/testuser/.nx/C-blade015-31022-B88B9BA2369A5DC1AB0AA53AA52EFC60//.nfs00000000f0ccece1000002a3':
Device or resource busy
NX> 1001 Bye.
Info: Closing connection to slave with pid 1979.
Info: Closing connection to slave with pid 1979.
-- NX SERVER START: -c /usr/bin/nxserver - ORIG_COMMAND=
-- NX SERVER START:  - ORIG_COMMAND=
Info: Using fds #4 and #3 for communication with nxnode.
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: not detected)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: testuser
NX> 102 Password:
NX> 103 Welcome to: blade015 user: testuser
NX> 105 listsession --status="suspended,running" --type="shadow"
NX> 127 Sessions list of user 'testuser' for reconnect:

Display Type             Session ID                       Options  Depth
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: testuser
NX> 105 startsession --link="adsl" --backingstore="1" --encryption="1"
--cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
--composite="1" --media="0" --render="1" --session="blade015"
--type="unix-gnome" --geometry="830x525" --keyboard="pc105/us"
--client="macosx" --screeninfo="830x525x24+render"

NX> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: not detected)
NX> 700 Session id: blade015-31022-652636BB5741BBDE55624B8D12FF22DF
NX> 705 Session display: 31022
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: 24c502ef2ec1281600e73fae76372332
NX> 702 Proxy IP: 192.168.1.115
NX> 706 Agent cookie: 24c502ef2ec1281600e73fae76372332
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 1009 Session status: starting
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
SESSION_LOG_CLEAN=0 in node.conf and investigate
"/users/jkholmes/.nx/F-C-blade015-31022-652636BB5741BBDE55624B8D12FF22DF/session".
You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to
test the basic functionality. Session log follows:
NX> 105
NXAGENT - Version 3.4.0
-----End Paste-----

I've seen this discussed in previous threads here:
http://marc.info/?l=freenx-knx&m=138442658819979&w=2

Checking port 35022 reveals that it's in use by LDAP, bound to a different
user on that NX server.  So, we're trying to figure out the best way to
change the port, either from the client or the server, that would result in
a successful login.  Currently, the symptoms are, double-click connection
name from NoMachine app, it requests password, password success, requests
session type (Gnome, KDE, etc) and once that session type is selected, it
hangs at "Creating session".  I've tried going into the testuser's
~/.nx/config/blade015.nxs and changing the NoMachine daemon port from 4000
to 4001, but that doesn't seem to have the intended effect as, after having
saved the change, then closing and re-opening the NoMachine client to
reconnect changes that value back to 4000.  I can't change the server
variable "DISPLAY_BASE=" because others are connected to it, but I feel
pretty confident that if/when their connection is dropped, they'll be faced
with the same issues as our testuser.  BTW, testuser was simply to recreate
the problem another user is having which is exactly the same output from
the /var/log/nx/nxserver.log file for testuser.

Regards,
lmind
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20150311/0549428f/attachment.html>