Unsolved
1 Message
0
360
July 25th, 2023 16:00
Another instance of nsrsnmd with PID 23221 is already running on host server
Hi nice to meet you!
I just updated networker from version 8 to version 19.9.0.1, it normally mounts a tape in a SL150 library, but when I unmount it it wouldn't let me. What may be happening (I tried to recreate library and it didn't work)
- This is a message from the systemctl status networker that alarms me:
jul 25 19:51:03 serverbkp root[23895]: NetWorker media: (info) Another instance of nsrsnmd with PID 23221 is already running on host serverbkp
- Message from daemon.raw:
71193 07/25/2023 08:22:44 PM 0 0 0 4162692928 26226 0 serverbkp nsrd NSR info Media Info: Another instance of nsrsnmd with PID 26658 is already running on host serverbkp
96548 07/25/2023 08:23:29 PM 5 17 999 3351361344 26658 0 serverbkp nsrsnmd NSR critical The nsrsnmd cannot process the control request from server serverbkp because this storage node is managed by server serverbkp.
Could it be a bug, did it happen to anyone with a linux oracle (in my case it's oracle 9)?
It leads me to think that there is a problem with the storage node serverbkp
Greetings
barry_beckers
393 Posts
0
July 31st, 2023 14:00
you are a daredevil if you went from nw8 (!) directly to the latest and greatest nw19.9.0.1? We'd consider that way too bleeding edge (regardless of the fact that only nw19.9 contains the latest security fixes, not yet introduced into nw19.8 yet). We'd actually prefer multiple cumulative hotfixes to have been released, so that would be nw19.7 or 19.8.
You might wanna explain a bit about the setup? Is see both the server and the storage node with the issue being reported as "serverbkp", so the NW backup server also controls the library?
And what do you mean with "I tried to recreate library and it didn't work"? Did you actually recreate the library but you encounter the same issue or did the recreation fail?
No older nsrsnmd from before the last NW restart hung? Checking if all processes are actually shutdown, when NW is shutdown is mandatory as NW itself is not always able to shut all processes down properly.
Recently the some issues encountered with NW storage nodes were related to the NW SN and the NW server not having matching auth methods set (so for example "0.0.0.0/0,nsrauth" vs. "0.0.0.0/0,nsrauth/oldauth).
https://www.dell.com/support/kbdoc/en-us/000205267/remote-storage-node-is-not-turning-into-a-ready-state-for-use?lang=en
some general KB articles regarding tape library issues:
https://www.dell.com/support/kbdoc/en-us/000079463?lang=en
https://www.dell.com/support/kbdoc/en-us/000069205