Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Can't Inventory, Can't Connect to Robotic SW Daemon

Status
Not open for further replies.

cmsterm

Systems Engineer
Oct 10, 2018
8
0
0
US
Hello all,

I was getting errors on my tape library that the hard picker was jammed and errors of an orphaned tape. This was causing all backups to fail.
One tape was found to be having issues in the picker, while it wasn't jammed it was apparent it should be removed as it had scrapes on it from hardware issues, I deemed it as a loss, removed it, leaving its original slot empty, and had everything put back together since the picker looked fine.
When the library was powered back up I watched the picker inside do its thing, looked fine, sounded fine.
I went to go start a new inventory to see if there would be problems with the removed tape or if my problems were solved and backups were succeeding again. I got the error:


robot inventory failed: Requested slot does not exist in robot (228)


I put the bad tape back in the original slot it was before and attempted another inventory. I received the same error.
I tried restarting the library, and trying another inventory, same error.

I read on a Veritas site that I should stop/restart the Media Manager Device Daemon.
While waiting for this to complete I received the error:


miscellaneous error (96)


When I went to retry it showed the only option available was to start the Media Manager Device Daemon. So I attempted to start it.
I received error:


oprd returned abnormal status (96)


Now when attempting an inventory I receive:


cannot connect to robotic software daemon (42)


I tried to reboot the library again and I have all the same results.

I have 1 master server and 1 robot TLD(0)


--

Trying to watch the console for any more info while it's running behind the netbackup software:

"/usr/openv/volmgr/bin/vmpool" -h servername.domainname.com -listscratch
(SR-2)execCommand:
Protocol Code: 1
Status: 0
Time Taken: 631ms
Error Msg:
Server Locale: en_US
TO[0]:"/usr/openv/volmgr/bin/vmpool" -h servername.domainname.com -
listscratch
FROM[0]: Scratch Pools
FROM[1]: =============
FROM[2]: Scratch
Aux data: null
TimeTaken: PCode:1,"/usr/openv/volmgr/bin/vmpool" -h servername.dialog
-direct.com -listscratch ,631

"/usr/openv/volmgr/bin/vmpool" -h servername.domainname.com -list_catalog_b
ackup
(SR-2)execCommand:
Protocol Code: 1
Status: 0
Time Taken: 490ms
Error Msg:
Server Locale: en_US
TO[0]:"/usr/openv/volmgr/bin/vmpool" -h servername.domainname.com -
list_catalog_backup
FROM[0]: Catalog Backup Pools
FROM[1]: ====================
FROM[2]: CatalogBackup
Aux data: null
TimeTaken: PCode:1,"/usr/openv/volmgr/bin/vmpool" -h servername.dialog
-direct.com -list_catalog_backup ,490

"/usr/openv/volmgr/bin/vmupdate" -rt tld -rn 0 -rh servername.domainname.c
om -vh servername.domainname.com -nostderr -use_barcode_rules -use_seed
(SR-2)execCommand:
Protocol Code: 1
Status: 42
Time Taken: 15706ms
Error Msg: cannot connect to robotic software daemon (42)
Server Locale: en_US
TO[0]:"/usr/openv/volmgr/bin/vmupdate" -rt tld -rn 0 -rh servername.d
ialog-direct.com -vh servername.domainname.com -nostderr -use_barcode_rule
s -use_seed
FROM[0]: cannot connect to robotic software daemon (42)
Aux data: null
TimeTaken: PCode:1,"/usr/openv/volmgr/bin/vmupdate" -rt tld -rn 0 -rh d
fppnbusrv01.domainname.com -vh servername.domainname.com -nostderr -use
_barcode_rules -use_seed ,15706






 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top