Level 5

5 years ago

Solved

cannot connect to robotic software daemon (42)

Hi,

We've got a problem with our tape library due to a power failure, and requires a robot replacement.

After the change, both drives in one media server are down and returning an error:

root@pp-db01:~# /usr/openv/volmgr/bin/tpconfig -l
Device Robot Drive       Robot                    Drive                 Device         Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path           Device Path
robot      0    -    TLD    -       -  -          -                     pp-master.domain.com
  drive    -    0 hcart3    1    DOWN  -          HP.ULTRIUM6-SCSI.000  /dev/rmt/0cbn
  drive    -    1 hcart3    2    DOWN  -          HP.ULTRIUM6-SCSI.001  /dev/rmt/1cbn
root@pp-db01:~#
root@pp-db01:~#
root@pp-db01:~# /usr/openv/volmgr/bin/vmoprcmd -d
cannot connect to robotic software daemon (42)

Any input with the error? In media server 2, both drives are up.

root@pp-db02:~# /usr/openv/volmgr/bin/tpconfig -l
Device Robot Drive       Robot                    Drive                 Device         Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path           Device Path
robot      0    -    TLD    -       -  -          -                     pp-master.domain.com
  drive    -    0 hcart3    1      UP  -          HP.ULTRIUM6-SCSI.000  /dev/rmt/0cbn
  drive    -    1 hcart3    2      UP  -          HP.ULTRIUM6-SCSI.001  /dev/rmt/1cbn

Regards

Hi quebek Nicolai X2

Thank you guys for your help. Luckily, I've managed to bring up the drive in db01.

root@master:~# vmoprcmd

                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
master.domain.com                    760200    ACTIVE
pp-db02.domain.com                   760200    ACTIVE
pp-db01.domain.com                   760200    ACTIVE

                                PENDING REQUESTS


                                    <NONE>

                                  DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM6-SCSI.000     No      No                     No        hcart3-Clean
    master.domain.com    /dev/rmt/0cbn                        TLD
    pp-db02.domain.com   /dev/rmt/0cbn                        SCAN-TLD
    pp-db01.domain.com   /dev/rmt/0cbn                        TLD

HP.ULTRIUM6-SCSI.001     Yes     Yes    0017L6  0017L6  Yes       hcart3-Clean
    master.domain.com    /dev/rmt/1cbn                        TLD
    pp-db02.domain.com   /dev/rmt/1cbn                        SCAN-TLD
    pp-db01.domain.com   /dev/rmt/1cbn                        ACTIVE

Though I'm not sure 100% what make this up. What I did:

1. Reboot the master server

2. Reboot the tape library

After the reboot, drive in db01 is still down. What I tried is to manually bring up the path in the GUI:

Media and Device Management > Device Monitor > Select the drive. From the drive list (pp-db01), right click and click “Up Path”.

14 Replies

quebek

Moderator

5 years ago

Hey

What is the output from vmoprcmd and tpautoconf -report_disc

did you try to start and stop ltid on db01?

technimdaxviii

Level 5

5 years ago

Hi quebek,

This is the output from the db01

root@pp-db01:~# vmoprcmd

                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
pp-master.domain.com                    760200    ACTIVE
pp-db02.domain.com                   760200    ACTIVE
pp-db01.domain.com                   760200    ACTIVE

                                PENDING REQUESTS


                                    <NONE>

                                  DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM6-SCSI.000     No      No                     No        hcart3-Clean
    pp-master.domain.com    /dev/rmt/0cbn                        SCAN-TLD
    pp-db02.domain.com   /dev/rmt/0cbn                        TLD
    pp-db01.domain.com   /dev/rmt/0cbn                        DOWN-TLD

HP.ULTRIUM6-SCSI.001     No      No                     No        hcart3-Clean
    pp-master.domain.com    /dev/rmt/1cbn                        SCAN-TLD
    pp-db02.domain.com   /dev/rmt/1cbn                        TLD
    pp-db01.domain.com   /dev/rmt/1cbn                        DOWN-TLD
root@pp-db01:~#
root@pp-db01:~#
root@pp-db01:~# tpautoconf -report_disc
root@pp-db01:~#

What I tried was restart the netbakup service on db01:

Stop:
/usr/openv/netbackup/bin/goodies/netbackup stop

Start:
/usr/openv/netbackup/bin/goodies/netbackup start

Regards,

quebek
Moderator
5 years ago
Hey

So few more to run on db01

/usr/openv/volmgr/bin/scan

bpps -x

do you see drives there? I assume you did already attempt to UP these two? I would UP them again and create logs under /usr/openv/volmgr/debug

refer to https://www.veritas.com/support/en_US/doc/86063237-127664549-0/v28993834-127664549

Nicolai
Moderator
5 years ago
Hi technimdaxviii I have deleted the duplicate thread and removed the references to the duplicate thread since its now fixed.

Best Regards
Nicolai
- technimdaxviii
  Level 5
  5 years ago
  Hi Nicolai,
  
  Thank you, well appreciated.
  
  Regards

technimdaxviii

Level 5

5 years ago

Hi quebek Nicolai X2

Thank you guys for your help. Luckily, I've managed to bring up the drive in db01.

root@master:~# vmoprcmd

                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
master.domain.com                    760200    ACTIVE
pp-db02.domain.com                   760200    ACTIVE
pp-db01.domain.com                   760200    ACTIVE

                                PENDING REQUESTS


                                    <NONE>

                                  DRIVE STATUS

Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM6-SCSI.000     No      No                     No        hcart3-Clean
    master.domain.com    /dev/rmt/0cbn                        TLD
    pp-db02.domain.com   /dev/rmt/0cbn                        SCAN-TLD
    pp-db01.domain.com   /dev/rmt/0cbn                        TLD

HP.ULTRIUM6-SCSI.001     Yes     Yes    0017L6  0017L6  Yes       hcart3-Clean
    master.domain.com    /dev/rmt/1cbn                        TLD
    pp-db02.domain.com   /dev/rmt/1cbn                        SCAN-TLD
    pp-db01.domain.com   /dev/rmt/1cbn                        ACTIVE

Though I'm not sure 100% what make this up. What I did:

1. Reboot the master server

2. Reboot the tape library

After the reboot, drive in db01 is still down. What I tried is to manually bring up the path in the GUI:

Media and Device Management > Device Monitor > Select the drive. From the drive list (pp-db01), right click and click “Up Path”.

Forum Discussion

cannot connect to robotic software daemon (42)

14 Replies

Related Content

cannot connect to robotic software Daemon 42

connect connect to robotic software daemon (42)

NBU 7.1.0.2 - cannot connect to robotic software daemon (42)

After upgrade 7.7.3 - None-Robot control host gets error cannot connect to robotic software daemon

Cannot connect to robotic daemon 42