Disk Enclosures
1752288 Members
4319 Online
108786 Solutions
New Discussion юеВ

Re: SDM Command failed.

 
Aaron Sheard
Frequent Advisor

Re: SDM Command failed.

I am now having the same problem. How was this issue resolved?

TIA

Aaron
"uh, hey... did we get a good backup last night?"
Eugeny Brychkov
Honored Contributor

Re: SDM Command failed.

Hai,
try the following actions:
1. /opt/sanmgr/hostagent/sbin/HA_trigger stop
2. /opt/sanmgr/hostagent/sbin/dial_trigger stop
3. find file 'DeviceDBFile' and move it (or rename) to another location;
4. /opt/sanmgr/hostagent/sbin/dial_trigger start
5. /opt/sanmgr/hostagent/sbin/HA_trigger start
and then try armdiscover, armdsp -i and armdsp -a
Eugeny
David Reno
Advisor

Re: SDM Command failed.

Where can I get the software installed into the /opt/sanmgr? It doesn't seem to exist on my hosts.

My HP-UX version is:
HPUX11i-OE-MC B.11.11.0209 HP-UX Mission Critical Operating Environment Component
Aaron Sheard
Frequent Advisor

Re: SDM Command failed.

make sure the two required daemons are running. The start scripts are located in /opt/sanmgr/hostagent/sbin

They are called HA_trigger and dial_trigger.

i would suggest a stop/start on each of those and make sure they start correctly, and then do an armdiscover
"uh, hey... did we get a good backup last night?"
Aaron Sheard
Frequent Advisor

Re: SDM Command failed.

make sure the two required daemons are running. The start scripts are located in /opt/sanmgr/hostagent/sbin

They are called HA_trigger and dial_trigger.

i would suggest a stop/start on each of those and make sure they start correctly, and then do an armdiscover
"uh, hey... did we get a good backup last night?"
Aaron Sheard
Frequent Advisor

Re: SDM Command failed.

make sure the two required daemons are running. The start scripts are located in /opt/sanmgr/hostagent/sbin

They are called HA_trigger and dial_trigger.

i would suggest a stop/start on each of those and make sure they start correctly, and then do an armdiscover
"uh, hey... did we get a good backup last night?"
Eugeny Brychkov
Honored Contributor

Re: SDM Command failed.

One copy of CV was shipped with your VA. If you lost it (CD) then call HP - neither CV nor Autopath nor SecureManager are not available for download
Eugeny
Andrey Pevnev
Advisor

Re: SDM Command failed.

I have the same problem :((

bash-3.00# armdsp -i
Error logging in: TIMEOUT EXPIRED
bash-3.00# armdiscover
This could take several minutes ...

Failed to obtain remote database interface to host: localhost
bash-3.00# ping localhost
PING localhost: 64 byte packets
64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms

----localhost PING Statistics----
1 packets transmitted, 1 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0


I've done that you suggested:

bash-3.00# /opt/sanmgr/hostagent/sbin/HA_trigger stop

ERROR: Failed to stop HostAgent normally. Try to kill the process
NOTE: killing zombie jre thread 1562
NOTE: HostAgent has stopped
bash-3.00# /opt/sanmgr/hostagent/sbin/dial_trigger stop
NOTE: Stopping diald. Please wait...
NOTE: dial stopped.

bash-3.00# mv /var/opt/sanmgr/commandview/server/data/DeviceDBFile /var/opt/sanmgr/commandview/server/data/DeviceDBFile.bak

bash-3.00# /opt/sanmgr/hostagent/sbin/HA_trigger start
NOTE: Starting HostAgent
NOTE: HostAgent started
bash-3.00# /opt/sanmgr/hostagent/sbin/dial_trigger start
NOTE: Starting diald....
NOTE: Done...


But it's still doesn't work :( :(

Maybe any other ideas?
Torsten.
Acclaimed Contributor

Re: SDM Command failed.

Andrey,

please start your own thread!

T.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!