Conference smurf::ase

1992.0. "Can't modify a DRD service" by NETRIX::"[email protected]" (John McDonald) Mon Apr 07 1997 17:00

I hava a customer that is trying to modify a DRD service. He makes the
changes in asemgr, but when he says 'yes' to modify the service, it comes
back with 'Add/Start failed'.

First I had him run clu_ivp on both members - no problems there. I then
had him run 'drd_ivp -p -v -c' on both member, which also showed no
problems. I then suggested he trun on informational-level logging to
get a better idea of what's happening and he sent me the logs. The only
message I can find in the logs is the 'Add/Start failed', with no
explanation as to why.

Here is the log:

Apr  4 20:45:16 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4806
check 6 /dev/rvol/devdg/dev6 
Apr  4 20:45:17 db1 ASE: mcdb1 Agent Info: exec'ing:
/var/ase/sbin/lsm_dg_action 7937 check devdg rz16 rzb16 rzc16 rzd16 rze16
rzf16 rzg16 rzh16 rz27 rzb27 rzc27 rzd27 rze27 rzf27 rzg27 rzh27 
Apr  4 20:45:17 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 7942
check 7 /dev/rvol/devdg/dev7 
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Info: exec'ing:
/var/ase/sbin/lsm_dg_action 4816 check devdg rz16 rzb16 rzc16 rzd16 rze16
rzf16 rzg16 rzh16 rz27 rzb27 rzc27 rzd27 rze27 rzf27 rzg27 rzh27 
Apr  4 20:45:17 db1 ASE: mcdb1 Agent Info: exec'ing:
/var/ase/sbin/lsm_dg_action 7952 check devdg rz16 rzb16 rzc16 rzd16 rze16
rzf16 rzg16 rzh16 rz27 rzb27 rzc27 rzd27 rze27 rzf27 rzg27 rzh27 
Apr  4 20:45:17 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 7957
check 8 /dev/rvol/devdg/dev8 
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4821
check 7 /dev/rvol/devdg/dev7 
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Info: exec'ing:
/var/ase/sbin/lsm_dg_action 4831 check devdg rz16 rzb16 rzc16 rzd16 rze16
rzf16 rzg16 rzh16 rz27 rzb27 rzc27 rzd27 rze27 rzf27 rzg27 rzh27 
Apr  4 20:45:17 db1 ASE: mcdb1 Agent Notice: deleting service dev_drd
Apr  4 20:45:17 db1 ASE: mcdb1 Agent Info: exec'ing:
/var/ase/sbin/lsm_dg_action 7968 delete devdg rz16 rzb16 rzc16 rzd16 rze16
rzf16 rzg16 rzh16 rz27 rzb27 rzc27 rzd27 rze27 rzf27 rzg27 rzh27 -h mcdb1 
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4836
check 8 /dev/rvol/devdg/dev8 
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Notice: deleting service dev_drd
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Info: exec'ing:
/var/ase/sbin/lsm_dg_action 4848 delete devdg rz16 rzb16 rzc16 rzd16 rze16
rzf16 rzg16 rzh16 rz27 rzb27 rzc27 rzd27 rze27 rzf27 rzg27 rzh27 -h mcdb1 
Apr  4 20:45:17 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4863
delete 1 /dev/rvol/devdg/dev1 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4874
delete 2 /dev/rvol/devdg/dev2 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4885
delete 3 /dev/rvol/devdg/dev3 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4896
delete 4 /dev/rvol/devdg/dev4 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4907
delete 5 /dev/rvol/devdg/dev5 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4918
delete 6 /dev/rvol/devdg/dev6 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4929
delete 7 /dev/rvol/devdg/dev7 
Apr  4 20:45:18 db1 ASE: mcdb2 Agent Info: exec'ing: /var/ase/sbin/drdmgr 4940
delete 8 /dev/rvol/devdg/dev8 
Apr  4 20:45:19 db1 ASE: mcdb2 Director Info: ASE_DELETE_SERVICE Reply from
Agent seq: 126 ch: 0  ASE_OK
Apr  4 20:45:19 db1 ASE: mcdb2 Director Info: Reply from mcdb2
Apr  4 20:45:32 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8005
delete 1 /dev/rvol/devdg/dev1 
Apr  4 20:45:32 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8016
delete 2 /dev/rvol/devdg/dev2 
Apr  4 20:45:33 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8027
delete 3 /dev/rvol/devdg/dev3 
Apr  4 20:45:33 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8038
delete 4 /dev/rvol/devdg/dev4 
Apr  4 20:45:33 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8049
delete 5 /dev/rvol/devdg/dev5 
Apr  4 20:45:33 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8060
delete 6 /dev/rvol/devdg/dev6 
Apr  4 20:45:33 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8071
delete 7 /dev/rvol/devdg/dev7 
Apr  4 20:45:33 db1 ASE: mcdb1 Agent Info: exec'ing: /var/ase/sbin/drdmgr 8082
delete 8 /dev/rvol/devdg/dev8 
Apr  4 20:45:34 db1 ASE: mcdb2 Director Info: ASE_DELETE_SERVICE Reply from
Agent seq: 123 ch: 4  ASE_OK
Apr  4 20:45:34 db1 ASE: mcdb1 AseMgr Info: Service deleted.
Apr  4 20:45:34 db1 ASE: mcdb1 AseMgr Notice: Deleted service dev_drd
Apr  4 20:45:34 db1 ASE: mcdb2 Director Info: Reply from mcdb1
Apr  4 20:45:34 db1 ASE: mcdb2 Director Notice: deleted service
Apr  4 20:46:47 db1 ASE: mcdb1 AseMgr Info: Sending blocking ASE_FREE_LOCK to
mcdb2 at channel 3 seq 26 len 48
Apr  4 20:46:47 db1 ASE: mcdb1 Agent Info: AseMgr on 'mcdb1' disconnected
Apr  4 20:46:47 db1 ASE: mcdb2 Director Info: ASE_FREE_LOCK Request from
AseMgr seq: 26 ch: 5 
Apr  4 20:46:47 db1 ASE: mcdb1 AseMgr Info: ASE_FREE_LOCK Reply from Director
seq: 26 ch: 3  ASE_OK
Apr  4 20:46:47 db1 ASE: mcdb1 AseMgr Error: Add/Start failed - Service
dev_drd not added...
Apr  4 20:46:47 db1 ASE: mcdb2 Director Info: freed the database lock
Apr  4 20:46:47 db1 ASE: mcdb2 Director Info: AseMgr on 'mcdb1' no longer
reachable
Apr  4 20:47:22 db1 ASE: local HSM Info: connected to by AseMgr
Apr  4 20:47:22 db1 ASE: local AseMgr Info: connected to HSM
Apr  4 20:47:22 db1 ASE: local AseMgr Info: Sending blocking HSM_INQ_LIST to
mcdb1 at channel 0 seq 0 len 48
Apr  4 20:47:22 db1 ASE: local HSM Info: HSM_INQ_LIST Request from AseMgr seq:
0 ch: 1 
Apr  4 20:47:22 db1 ASE: local AseMgr Info: HSM_INQ_LIST Reply from HSM seq: 0
ch: 0  ASE_OK
Apr  4 20:47:22 db1 ASE: local AseMgr Info: connected to AseLogger
Apr  4 20:47:22 db1 ASE: local AseMgr Info: logging to log daemon on mcdb2
Apr  4 20:47:22 db1 ASE: mcdb1 Agent Info: connected to by AseMgr
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: logging to log daemon on mcdb1
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: connected to Agent
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: Sending blocking ASE_INQ_DIR to
mcdb1 at channel 2 seq 4 len 48
Apr  4 20:47:22 db1 ASE: mcdb1 Agent Info: ASE_INQ_DIR Request from AseMgr
seq: 4 ch: 4 
Apr  4 20:47:22 db1 ASE: mcdb2 Director Info: connected to by AseMgr
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: ASE_INQ_DIR Reply from Agent seq:
4 ch: 2  ASE_OK
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: connected to Director
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: Sending blocking ASE_INQ_HOST to
mcdb2 at channel 3 seq 8 len 48
Apr  4 20:47:22 db1 ASE: mcdb1 Agent Info: AseMgr on 'mcdb1' disconnected
Apr  4 20:47:22 db1 ASE: mcdb2 Director Info: ASE_INQ_HOST Request from AseMgr
seq: 8 ch: 5 
Apr  4 20:47:22 db1 ASE: mcdb1 AseMgr Info: ASE_INQ_HOST Reply from Director
seq: 8 ch: 3  ASE_OK
Apr  4 20:47:22 db1 ASE: mcdb2 Director Info: sent member state information to
ASE manager on mcdb1
Apr  4 20:47:22 db1 ASE: mcdb2 Director Info: AseMgr on 'mcdb1' no longer
reachable
Apr  4 20:47:28 db1 ASE: local HSM Info: connected to by AseMgr
Apr  4 20:47:28 db1 ASE: local AseMgr Info: connected to HSM

Anyone have any ideas, either about what might have caused the problem or
how I can scrounge some more details?

Thanx.
John McDonald
Atlanta CSC

[Posted by WWW Notes gateway]

Sorry.

It's TCR 1.4 on DU 4.0b with all patches.

John McDonald
Atlanta CSC

[Posted by WWW Notes gateway]

    John,
    
    What versin of ASE is the customer running?
    
    What does the asemgr session look like?  Since the log is not giving
    any extra information this might tell us something.  Looking at the
    code I have to believe that the customer was doing a DRD service add.
    The add or start failed which then put him into the modify.  The
    modify was either not chosen or it also failed and they got 
    "Add/Start failed".  In any case, the error in the daemon.log is 
    from a service add failure.
    
    I at a loss to explain why there is no more informational messages 
    in daemon.log.  Make sure to check on both systems for more
    information.  You can also turn ase logging off and log locally
    to remove it from the equation.
    
    With the lack of information given in daemon.log I think you are 
    going to have to enter a QAR to get some more help on this problem.
    
    -- Greg
    

Greg,

Thanx for the reply. We managed to solve the problem. The customer was using
8 LSM volumes in the DRD service, and it turns out one of them had some
problems (know bug). ase didn't complain when he tried to add the bad
one, but it failed (as shown in the log). I'm not sure why we didn't
get more info, though.

John McDonald
Atlanta CSC

[Posted by WWW Notes gateway]

    I am glad you have your problem solved, however, it concerns me that
    you did not get an error in the daemon.log.  Can you please send me
    email describing the configuration and problem that you had.  I want
    to try and reproduce it on my systems so I can fix it if possible.
    
    Thanks.
    
    -- Greg