umut_var
2 Bronze

networker 18.1 setup problem

Jump to solution

umut_var_0-1618851319841.png

I install the rpm packages without any erro

but after systemctl start networker

nsrexecd starts but after that no other deamons are starting.

 

0 Kudos
1 Solution

Accepted Solutions
bingo.1
4 Ruthenium

Re: networker 18.1 setup problem

Jump to solution

A portmapper is a tool that dynamically distributes/maps TCP/IP port usage. There are sending ports (in NW also known as Connection Ports) and receiving ports (listening ports, in NW aka: Service Ports). Service Ports are the ones you usually restrict by firewall rules. For interoperability, specific port ranges are restricted worldwide to allow communication between all computers. So at least one portmapper must be provided by an OS which supports TCP/IP, additional portmappers may be provided by the application.

Now - NW (already the NC client package) of course uses both port types And it provides an extra portmapper. there are at least 4 service ports involved but by default 2000 are enabled. Unfortunately, 2 ports are fixed: 7937 & 7938. And this is obviously the problem. I think, these conflicts will be corrected if you let NW make the firewall adjustments during installation but I am not completely sure as I never ran into this problem.

To change these settings, please read my recent thread https://www.dell.com/community/NetWorker/nsr-ports-conflict/td-p/7855267/jump-to/first-unread-messag...

BTW - the advice to modify the hosts table is not wrong but the effect applies more to name resolution. And if you want to verify the port usage, use netstat -a .

 

 

View solution in original post

4 Replies
bingo.1
4 Ruthenium

Re: networker 18.1 setup problem

Jump to solution

All necessary NW packages seem to be installed, except for the nre... software (NW's java runtime environment). If missing, only the NW client daemon will start.

Please verify all installed packages and whether you have run the appropriate scripts after installation. You will find more info in /nsr/logs/daemon.raw.

For a proper output please run nsr_render_log /nsr/logs/daemon.raw.

Also keep in mind that the latest NW version is 19.4.0.1. You may want to install this version.

 

0 Kudos
umut_var
2 Bronze

Re: networker 18.1 setup problem

Jump to solution

Hey Bingo.1

I tried to install 18.2

but I got the same error.

As you suggested I run nsr_render_log daemon

I could not paste the output here, but there is onr obvious error

nsrpsd RPC error RPC client handle: Connection refused.

nsrpsd RPC error Unable to create the connection with 'portmapper' to host 'localhost6' with address '::1' at port number 7938.

nsrpsd RPC critical Check whether the client services are running on the host '::1'

and

nsrpsd RPC error Unable to create the connection with 'portmapper' to host 'localhost' with address '127.0.0.1' at port number 7938

I am searching this error for 2 days. Every one advised to took up to /etc/hosts file.  But it is ok.

There is a dns-server on the machine and it can not resolve its on ip address to its hostname (nsloopup).

I thought this can be the problem, but I could not disable it.

I am searching now what the portmapper is?

Do you have an advise for the solution of this error?

thanks

0 Kudos
crazyrov
4 Beryllium

Re: networker 18.1 setup problem

Jump to solution

NetWorker is very much dependent on the name resolution of a hostname to IP. So if you ping a hostname and you are unable to get an IP then NetWorker wont be able to bring the nsrd up. Incase that is working make sure you are running nsr_shutdown -f before attempting a start the service again.
Looking at the error it looks like nsrexecd itself has not completed initializing so the rest of the services on your server will not come up either.

HTH,
For NetWorker related content - https://www.youtube.com/channel/UC4JLsVyXMyjbQ4i1NaJj5IQ

0 Kudos
bingo.1
4 Ruthenium

Re: networker 18.1 setup problem

Jump to solution

A portmapper is a tool that dynamically distributes/maps TCP/IP port usage. There are sending ports (in NW also known as Connection Ports) and receiving ports (listening ports, in NW aka: Service Ports). Service Ports are the ones you usually restrict by firewall rules. For interoperability, specific port ranges are restricted worldwide to allow communication between all computers. So at least one portmapper must be provided by an OS which supports TCP/IP, additional portmappers may be provided by the application.

Now - NW (already the NC client package) of course uses both port types And it provides an extra portmapper. there are at least 4 service ports involved but by default 2000 are enabled. Unfortunately, 2 ports are fixed: 7937 & 7938. And this is obviously the problem. I think, these conflicts will be corrected if you let NW make the firewall adjustments during installation but I am not completely sure as I never ran into this problem.

To change these settings, please read my recent thread https://www.dell.com/community/NetWorker/nsr-ports-conflict/td-p/7855267/jump-to/first-unread-messag...

BTW - the advice to modify the hosts table is not wrong but the effect applies more to name resolution. And if you want to verify the port usage, use netstat -a .

 

 

View solution in original post