nsrmmgd: failed query for volume

Question

Hi!

Customer have EBS 7.3 Server and Windows 2003 SP1 Clients.
He Update first the Clients to 7.3 and all works fine.
After he update the Server from 7.2 to 7.3 the first problem was, that he cannot connect with adminstrator.
Customer do:

root@BM-IS001:/usr/sbin/nsr# ./nsraddadmin -u "user=SYSTEM, host=bm-is007.pallas.com"
added user 'user=SYSTEM, host=bm-is007.pallas.com' to the administrator list

After this, he cannot mount one Tape. We see this error:

02/17/06 15:52:42 nsrd: [Jukebox `BM-LIB001', operation 2]. Initiated operation `operation: "Load"; operation device: "/dev/rmt/5ubn"; operation slots: " 1"; write enabled: "Yes"; '.
02/17/06 15:54:47 nsrmmgd: failed query for volume PGU530, authentication type 0 not adequate (1, 13)
02/17/06 15:55:12 nsrd: /dev/rmt/5ubn Verify label operation in progress
02/17/06 15:57:19 nsrd: [Jukebox `BM-LIB001', operation # 2]. failed query for volume PGU530, authentication type 0 not adequate (1, 13)
02/17/06 15:57:19 nsrd: /dev/rmt/5ubn Eject operation in progress
02/17/06 15:58:06 nsrd: [Jukebox `BM-LIB001', operation # 2]. Finished with status: retryable
02/17/06 15:58:06 nsrmmgd: RAP error: Invalid resource data.
02/17/06 15:58:06 nsrmmgd: Cannot update operation status resource (instance 2).

Here the nsrjb -v

root@BM-IS001:/# nsrjb -v
setting verbosity level to `1'

Jukebox BM-LIB001: (Ready to accept commands)
slot volume used pool barcode volume id recycla
1: PGU530 full BackupTapesBM PGU530 1307853140 no
2: PGU531 100% BackupTapesBM PGU531 1274298874 no
3: PGU532 77% BackupTapesBM PGU532 1240744592 no
4: PGU500 0% BackupTapesBM PGU500 bc8f840e-00000005-48f442f4-43f442f4-01b90000-c0a80305 no
5: PGU501 0% BackupTapesBM PGU501 7ab1bbf5-00000005-47f44344-43f44344-01ba0000-c0a80305 no
6: PGU516 0% BackupTapesBM PGU516 6ec04d8f-00000005-46f44394-43f44394-01bb0000-c0a80305 no
7: PGU517 0% BackupTapesBM PGU517 dbd031a4-00000005-45f443e5-43f443e5-01bc0000-c0a80305 no
8: PGU512 full BackupTapesBM PGU512 4b1f1c46-00000005-5fa2c2f9-43a2c2f9-15a20000-c0a80305 no
9: PGU481 full BackupTapesBM PGU481 064f50bd-00000005-25becb83-43becb83-07dc0000-c0a80305 no
10: PGU482 full BackupTapesBM PGU482 b83ebf2d-00000005-23becbee-43becbee-07de0000-c0a80305 no
11: PGU483 full BackupTapesBM PGU483 86baa62c-00000005-21becc3d-43becc3d-07e00000-c0a80305 no
12: PGU484 full BackupTapesBM PGU484 208fedc9-00000005-20becca3-43becca3-07e10000-c0a80305 no
13: PGU514 full BackupTapesBM PGU514 fb97f718-00000005-1ebecd34-43becd34-07e30000-c0a80305 no
14: PGU515 full BackupTapesBM PGU515 ba0c6e59-00000005-1dbecdcc-43becdcc-07e40000-c0a80305 no
15: PGU518 full BackupTapesBM PGU518 4852b5c8-00000005-96d109bf-43d109bf-126b0000-c0a80305 no
16: PGU519 full BackupTapesBM PGU519 7bfa87ff-00000005-94d10a53-43d10a53-126d0000-c0a80305 no
17: PGU520 full BackupTapesBM PGU520 54b4f9e7-00000005-91d10b22-43d10b22-12700000-c0a80305 no
18: PGU521 full BackupTapesBM PGU521 d8fdae8d-00000005-90d10bc5-43d10bc5-12710000-c0a80305 no
19: PGU522 full BackupTapesBM PGU522 758f7fa6-00000005-8fd10c67-43d10c67-12720000-c0a80305 no
20: PGU523 full BackupTapesBM PGU523 59b5f4b8-00000005-8ed10cfb-43d10cfb-12730000-c0a80305 no
21: PGU524 full BackupTapesBM PGU524 d8d8724e-00000005-8dd10d8e-43d10d8e-12740000-c0a80305 no
22: PGU529 0% CloneTapesBM PGU529 ebc85bce-00000005-4cf44166-43f44166-01b50000-c0a80305 no
23: PGU528 0% CloneTapesBM PGU528 7b266efe-00000005-4af4421b-43f4421b-01b70000-c0a80305 no
24: PGU499 0% CloneTapesBM PGU499 349c3084-00000005-a4e34e93-43e34e93-085d0000-c0a80305 no
25: PGU441 16% ARZPool PGU441 211b7012-00000005-9d679f86-42679f86-01670000-c0a80305 no

25 volume(s), 9 volumes are less than 80% full.
6753 GB estimated capacity, 1227 GB remaining (82% full)

drive 1 (/dev/rmt/5ubn) slot :
drive 2 (/dev/rmt/6ubn) slot :

The next question is, we fix the problem not, it is possible to remove from EBS Server the Version 7.3 and installed 7.2?

ble1 · Answer

After he update the Server from 7.2 to 7.3 the first
problem was, that he cannot connect with
adminstrator.
Customer do:

This is very well covered in installation guide for EBS 7.3.

After this, he cannot mount one Tape. We see this
error:

Do you get this error only for this volume or do you get this error for any other volume as well?

Did you open a support call with support?

Here the nsrjb -v

As you can see, first 3 volumes have short volids - not sure if this is expected or not. Did you check mmedia database with mminfo for this volumes and their volids?

The next question is, we fix the problem not, it is
possible to remove from EBS Server the Version 7.3
and installed 7.2?

No, as stated in documentation there is no way back - unless you do mmrecov with 7.2 again. If you had 7.2 before it is possible that even 7.2 cause something bad which 7.3 could not handle. Check you mm as suggested above and open this as a support ticket with your support get covered.

ble1 · Answer

Mike,Open this with support - it could be something trivial like name resolution or nsrexecd in need of restarting and it could be something worse - hopefully if that would be some kind of problem fix could exist.The auth type 0 error can mean number of things and it happens while communicating to the new library operation daemon - nsrmmgd. So it could be an issue and perhaps not such a big deal. Currently engineering is the only one who has better understanding of these things for 7.3 code so case for this would a good idea.

mg115301 · Answer

Do you get this error only for this volume or do you get >this error for any other volume as well?

We see this volume for all volumes.
And every time authentication type 0 not adequate

As you can see, first 3 volumes have short volids - not >sure if this is expected or not. Did you check mmedia >database with mminfo for this volumes and their volids?

We will check this. Wait for results.

NetWorker

nsrmmgd: failed query for volume

Was this post helpful?