Unsolved
This post is more than 5 years old
3 Posts
0
12706
Networker connecting to host failed: remote system error- No connection could be made because the target machine actively refused it
Hello,
I am NEW to Networker. We recently deployed Networker 9.2.0 in our environment. I have installed Linux host and it has installed successflly but while adding linux host on Networker following error
Networker connecting to host failed: remote system error- No connection could be made because the target machine actively refused it
After Googling, I exhausted all available solutions to fix this issue but still no success
I don't have any issues with DNS resolution and my Windows Firewall on the server as well as Virtual Machines is turned off.
I would appreciate your help
ble1
2 Intern
2 Intern
•
14.3K Posts
1
September 13th, 2017 14:00
9.2 is fairly new (too new) and one version of it was pulled out so first question is if this is 9.2.0.3 which is the latest released? Second, this normally means that server could not connect to client. When you do nsrrpcinfo -p from your server - do you get response? If not, check if daemons are started as by default they are not after installation you need to do /etc/init.d/networker start on your linux client). Last, check log on client (nsr_render_log /nsr/logs/daemon.raw) to see if there is any error.
Vinayak12y
3 Posts
0
September 14th, 2017 00:00
Thank you for looking into the issue.when i am executing # /etc/init.d/networker start getting below error /etc/init.d/networker: line 47: /opt/nsr/admin/nsr_envexec: No such file or directory
ble1
2 Intern
2 Intern
•
14.3K Posts
0
September 16th, 2017 12:00
OK, now we know daemons are not started
I really can't say much about 9.2 as it is new fresh and I didn't test it so I will look back to 9.1.0.x example and you can compare it.
I suspect function start_service() fails... here is how it looks on 9.1.0.x:
The bold line is line 47 and it seems like this might be the same. Somewhere before that there is definition and comment that reads as following:
In your case it seems like /opt/nsr/admin/nsr_envexec is not there. Try to find it first... for example "find / -name nsr_envexec -print".
In my case it is /opt/nsr/admin/nsr_envexec as defined by script (same is defined in your script). My best guess from seen so far is that this script is missing on your system. Not sure if this is bug with installation or something else (one would need to check rpm). In my case (but I do not know if this is compatible with 9.2 code base) this looks as following:
bingo.1
2.4K Posts
0
September 17th, 2017 16:00
I understand that this is a message from a remote client (not the NW server itself).
It means that the communication between both clients is fine (by default they communicate via ports 7937 & 7938) -
however 'the connection has actively been refused'.
Usually it will be generated if the NW server is not allowed to access the client - the client will refuse the access.
How does NW control that? - via the file /nsr/res/servers. It should contain each allowed NW server - one per line.
So edit the file appropriately (it might contain a typo) or delete it (careful - in this case you would allow all NW servers to access the client).
Whenever you make a change to the file you must restart the NW daemon on the NW client to activate the change.
BTW - run 'nsr_render_log /nsr/logs/daemon.raw' on the client - it should tell you more.
Jalli Raj
17 Posts
0
September 29th, 2017 12:00
can you paste the output of the client name
From Networker server can you run
nsrrpcinfo -p