Closed

Backup_newbie

1 Rookie

•

8 Posts

0

505

April 13th, 2023 22:00

add one new storage node server and this one don't work

Backgroud：

one NW server+one Storage Node server with many successful backup

plan to add one more storage node server into this Networker environment

OS:

Oracle linux 8.2

installed networker software：

rpm -qa | grep lgto
lgtoclnt-19.6.1.0-1.x86_64
lgtonode-19.6.1.0-1.x86_64
lgtoxtdclnt-19.6.1.0-1.x86_64

started service and port：

nsrports
Service ports: 7937-9936
Connection ports: 0-0

when i try to add Library and AFTD device on this SN and run the backup，it failed！i nsr_render_log the daemon and checked many errors below

173679 04/14/2023 12:27:05 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 8693 from connection port range 0-0: Cannot assign requested address

173679 04/14/2023 12:27:10 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

173679 04/14/2023 12:28:13 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:28:13 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:28:19 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:28:19 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:29:22 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:29:22 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:29:29 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7984 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:29:29 AM 4 2 12 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Remote system error - Cannot assign requested address

173679 04/14/2023 12:30:33 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

173679 04/14/2023 12:30:39 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

173679 04/14/2023 12:31:43 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 8450 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:31:43 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:31:49 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:31:49 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:32:52 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7984 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:32:52 AM 4 2 12 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Remote system error - Cannot assign requested address

173679 04/14/2023 12:32:58 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 8693 from connection port range 0-0: Cannot assign requested address

173679 04/14/2023 12:34:01 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 8450 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:34:01 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:34:07 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7984 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:34:07 AM 4 2 12 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Remote system error - Cannot assign requested address

173679 04/14/2023 12:35:09 AM 3 1 2 1988085504 2012047 0 nsrexecd SYSTEM error Unable to bind socket to port 7938 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:35:09 AM 4 2 7 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Authentication error; why = Server rejected credential

173679 04/14/2023 12:35:16 AM 3 1 99 3244881728 2320429 0 nsrmmd#2 SYSTEM error Unable to bind socket to port 7984 from connection port range 0-0: Cannot assign requested address

79965 04/14/2023 12:35:16 AM 4 2 12 3244881728 2320429 0 nsrmmd#2 RPC severe Unable to authenticate with nsrd on for remote monitoring: Remote system error - Cannot assign requested address

Responses(6)

B

Backup_newbie

1 Rookie

•

8 Posts

0

April 13th, 2023 23:00

new SN OS firewall disabled and network firewall to NW server are all open

DNS is ok

B

Backup_newbie

1 Rookie

•

8 Posts

0

April 13th, 2023 23:00

I have tried deleted “peer information” on both NW server and new storage node side and restarted the networker service and still not work

B

Backup_newbie

1 Rookie

•

8 Posts

0

April 13th, 2023 23:00

new storage node server ‘s forward and back-forward DNS can be found on NW server

B

barry_beckers

393 Posts

0

April 17th, 2023 04:00

If it is a vanilla deployment with nw above nw19.4, then it will no longer have oldauth enabled. If the current nw server might already be in place a long time then it might have stated to use both nsrauth AND oldauth, which might lead to a conflict, that we also encountered with newly deployed clients.

See for example KB https://www.dell.com/support/kbdoc/en-us/000205267/remote-storage-node-is-not-turning-into-a-ready-state-for-use .

As the KB article shows:

On NetWorker server:
Run the following command on the CLI:

nsradmin -p nsrexec
NetWorker administration program.
Use the "help" command for help.
nsradmin> . type: nsrla
Current query set
nsradmin> show auth methods
nsradmin> print
auth methods: "0.0.0.0/0,nsrauth/oldauth";

On the remote storage node :

nsradmin -p nsrexec
NetWorker administration program.
Use the "help" command for help.
nsradmin> . type: nsrla
Current query set
nsradmin> show auth methods
nsradmin> print
auth methods: "0.0.0.0/0,nsrauth";

Cause
The auth method on the NetWorker server does not match the auth method on the remote storage node.

But I don't see the error mentioned from the KB article:

"Unable to connect to server: Unable to authenticate with server nsrserver: Authentication error; why = Client credential too weak". Do you see other things like "nsrsnmd NSR notice 22 Shutting down snmd" on the Networker storage node?

C

crazyrov

4 Operator

•

1.3K Posts

0

April 17th, 2023 07:00

@Backup_newbie , Along with the steps from Barry. Please also try running the following command

nsrrpcinfo -p storage-node-hostname

B

barry_beckers

393 Posts

0

April 17th, 2023 11:00

And the same from the NW SN towards the backup server.

On top of that you then also use nsrrpcinfo to actually see if each specific port of the stated running NW service is actually listening? Below script beats having to do that each and every time manually...

However even if below also shows just fine, still there can be issues, like due to the issue I mentioned earlier.

$ cat nsrrpcinfo_checks.sh
# use nsrrpcinfo -p output to run nsrrpcinfo checks to individual ports of systems running NW services.
# usage : ./nsrrpcinfo_checks.sh 

# v. 0.1 19-9-2022 BB

HOST_TO_CHECK=$1

nsrrpcinfo -p $HOST_TO_CHECK > /tmp/nsrrpcinfo_check.$$

echo "nsrpcinfo -p $HOST_TO_CHECK output:"

cat /tmp/nsrrpcinfo_check.$$
echo "*********************************************"

cat /tmp/nsrrpcinfo_check.$$|grep -v "PROGRAM" |while read line
do
#echo $line
PROGRAM=`echo $line|awk '{print $1}'`
VERSION=`echo $line|awk '{print $2}'`
PROTOCOL=`echo $line|awk '{print $3}'|cut -c1`
PORT=`echo $line|awk '{print $4}'`\
SERVICE=`echo $line|awk '{print $5}'`

echo output of : \"nsrrpcinfo -n $PORT -$PROTOCOL $HOST_TO_CHECK $PROGRAM $VERSION\" for SERVICE $SERVICE
nsrrpcinfo -n $PORT -$PROTOCOL $HOST_TO_CHECK $PROGRAM $VERSION

done

rm /tmp/nsrrpcinfo_check.$$

actual output, where NW_SN_to_check is the name/IP of the system to check:

# ./nsrrpcinfo_checks.sh NW_SN_to_check
nsrpcinfo -p NW_SN_to_check output:
PROGRAM VERSION PROTOCOL PORT SERVICE
100000 2 tcp 7938 nsrportmapper Port Mapper
100000 2 udp 7938 nsrportmapper Port Mapper
390436 1 tcp 9343 nsrexecd GSS Authentication
390435 1 tcp 9415 nsrexecd Resource Mirror
390113 1 tcp 7937 nsrexecd Remote Execution
390440 1 tcp 8739 nsrexecd_nsrfa Remote File Access
390111 1 tcp 8508 nsrsnmd Storage Node Management
390104 305 tcp 9164 nsrmmd Media Multiplexor
390104 405 tcp 7984 nsrmmd Media Multiplexor
*********************************************
output of : "nsrrpcinfo -n 7938 -t NW_SN_to_check 100000 2" for SERVICE nsrportmapper
Program 100000 version 2 ready and waiting
output of : "nsrrpcinfo -n 7938 -u NW_SN_to_check 100000 2" for SERVICE nsrportmapper
Program 100000 version 2 ready and waiting
output of : "nsrrpcinfo -n 9343 -t NW_SN_to_check 390436 1" for SERVICE nsrexecd
Program 390436 version 1 ready and waiting
output of : "nsrrpcinfo -n 9415 -t NW_SN_to_check 390435 1" for SERVICE nsrexecd
Program 390435 version 1 ready and waiting
output of : "nsrrpcinfo -n 7937 -t NW_SN_to_check 390113 1" for SERVICE nsrexecd
Program 390113 version 1 ready and waiting
output of : "nsrrpcinfo -n 8739 -t NW_SN_to_check 390440 1" for SERVICE nsrexecd_nsrfa
Program 390440 version 1 ready and waiting
output of : "nsrrpcinfo -n 8508 -t NW_SN_to_check 390111 1" for SERVICE nsrsnmd
Program 390111 version 1 ready and waiting
output of : "nsrrpcinfo -n 9164 -t NW_SN_to_check 390104 305" for SERVICE nsrmmd
Program 390104 version 305 ready and waiting
output of : "nsrrpcinfo -n 7984 -t NW_SN_to_check 390104 405" for SERVICE nsrmmd
Program 390104 version 405 ready and waiting

View All

No Events found!

NetWorker

add one new storage node server and this one don't work

Was this post helpful?