Start a Conversation

Unsolved

This post is more than 5 years old

C

905

November 25th, 2016 05:00

nsrexecd on NetWorker 8.2 RHEL 7 Client erroneously binds to ipv6 address

Hi Experts

Our Linux Engineers built up an Environment for Docker-Containers. On Default Docker is buildung up an IPv6 network for its communication needs.

I'm now unable to backup this Environment and found out that nsrexecd has bound its Services to one of the ipv6 addresses.

vlx00198 ~]# netstat -tulpen | grep nsr

tcp6       0      0 :::8682                 :::*                    LISTEN      0          37771      5109/nsrexecd      

tcp6       0      0 :::7937                 :::*                    LISTEN      0          38007      5109/nsrexecd      

tcp6       0      0 :::7938                 :::*                    LISTEN      0          37987      5109/nsrexecd      

tcp6       0      0 :::8905                 :::*                    LISTEN      0          37768      5109/nsrexecd      

udp6       0      0 :::7938                 :::*                                0          37985      5109/nsrexecd

Assuming that NetWorker follows a defined process to bind nsrexecd to a certain ip address during startup I'd like to ask if it is possible to change the default behaviour.

  • How can I control which IP address NetWorker is going to use?
  • How can the Linux Admin change the behaviour, if it isn't possible to change it on the NetWorker side?

Many thanks for your help!

Regards

Christian

14.3K Posts

November 26th, 2016 12:00

NW will bind to primary system address/IP.

No Events found!

Top