Forum / NoMachine for Linux / NX node: set bind/connect ip
- This topic has 2 replies, 2 voices, and was last updated 9 years, 10 months ago by ponch.
-
AuthorPosts
-
January 19, 2015 at 12:00 #5961ponchParticipant
Hello!
Trying to use NoMachine 4.4 with headless configuration.
Read this manual https://www.nomachine.com/AR10K00710 but only got “No session available..”
While debugging found this thing:
2015-01-16 21:17:14 556.944 14461 NXNODE WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 25001: Inappropriate ioctl for device from NXClientMonitor::__openClientMonitorSocket.
2015-01-16 21:17:14 658.939 14461 NXNODE Cannot get exit code from process 14530. Process still running.
2015-01-16 21:17:14 659.377 14461 NXNODE NXConnect to 127.0.0.1 25001 from NXClientMonitor::__openClientMonitorSocket.
2015-01-16 21:17:15 024.099 14663 NXNODE WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 12001: Broken pipe from NXSessionMonitor::__send_to_the_agent.
2015-01-16 21:17:15 024.452 14663 NXNODE Cannot connect to the agent, wait.
2015-01-16 21:17:15 025.606 14663 NXNODE NXParser: signal ‘CHLD’ received.
2015-01-16 21:17:15 026.025 14663 NXNODE Received ‘SIGCHLD’ signal:going to handle it
2015-01-16 21:17:15 026.482 14663 NXNODE handleSIGCHLD
2015-01-16 21:17:15 027.092 14663 NXNODE NXParser: signal ‘CHLD’ received.
2015-01-16 21:17:15 027.488 14663 NXNODE Received ‘SIGCHLD’ signal:going to handle it
2015-01-16 21:17:15 027.926 14663 NXNODE handleSIGCHLD
2015-01-16 21:17:15 062.861 30746 NXSERVER WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 20000: Inappropriate ioctl for device from main::send_command_to_server.
2015-01-16 21:17:15 265.890 30746 NXSERVER NXConnect to 127.0.0.1 20000 from main::send_command_to_server.
2015-01-16 21:17:15 422.882 14461 NXNODE WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 25001: Inappropriate ioctl for device from NXClientMonitor::__openClientMonitorSocket.
2015-01-16 21:17:15 524.927 14461 NXNODE Cannot get exit code from process 14530. Process still running.
2015-01-16 21:17:15 525.229 14461 NXNODE NXConnect to 127.0.0.1 25001 from NXClientMonitor::__openClientMonitorSocket.
2015-01-16 21:17:16 027.965 30746 NXSERVER WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 20000: Inappropriate ioctl for device from main::send_command_to_server.
2015-01-16 21:17:16 230.014 30746 NXSERVER NXConnect to 127.0.0.1 20000 from main::send_command_to_server.
2015-01-16 21:17:16 290.951 14461 NXNODE WARNING! NXPL::NXConnect cannot connect to 127.0.0.1, 25001: Inappropriate ioctl for device from NXClientMonitor::__openClientMonitorSocket.
2015-01-16 21:17:16 393.010 14461 NXNODE Cannot get exit code from process 14530. Process still running.
2015-01-16 21:17:16 393.430 14461 NXNODE NXConnect to 127.0.0.1 25001 from NXClientMonitor::__openClientMonitorSocket.somehow it is trying to connect to loopback address. while those port are attached to another ip (172.16.0.6). How do i change such behaviour? how do i set bind ip address or connect ip address?
tcp 0 0 0.0.0.0:4000 0.0.0.0:* LISTEN 30779/nxd
tcp 0 0 172.16.0.6:12001 0.0.0.0:* LISTEN 14461/nxnode.bin
tcp 0 0 172.16.0.6:20001 0.0.0.0:* LISTEN 14188/nxserver.bin
tcp 0 0 172.16.0.6:25001 0.0.0.0:* LISTEN 14530/nxclient.bin
tcp 0 0 172.16.0.6:20970 0.0.0.0:* LISTEN 30746/nxserver.bin
udp 0 0 0.0.0.0:5353 0.0.0.0:* 14530/nxclient.bin
udp 0 0 0.0.0.0:5353 0.0.0.0:* 14530/nxclient.bin
udp 0 0 172.16.0.6:5353 0.0.0.0:* 14461/nxnode.bin
udp 0 0 0.0.0.0:5353 0.0.0.0:* 14461/nxnode.binThanks!
January 19, 2015 at 14:01 #5982HavenParticipantHello ponch,
NoMachine require associating local IP address 127.0.0.1 with localhost hostname.
Please check if you can (temporarily) set the value for localhost to ‘127.0.0.1’ in ‘/etc/hosts’ file on the troublesome server.
Then after restart of nxserver it should be possible to establish sessions.If the issue persists please gather debug information following the instructions here:
https://www.nomachine.com/AR07K00677
Send them to issues[at]nomachine[dot]com with your ‘/etc/hosts’ file.January 20, 2015 at 09:05 #5983ponchParticipantDid the trick. Thanks! Now i can attach to my session.
-
AuthorPosts
This topic was marked as solved, you can't post.