DS 6.1 won't start as cluster service

Question

Hi!
RG: hylas-ldap
Resources:
Logical Hostname hylas
HAStorage ldap-data-1 (Diskgroup contains instance data)
I installed DS 6.0 and patched up to 6.1. As the topic says... I'm able to start the instance on every node of the Cluster (SC 3.2) with "dsadm start /path/to/instance". Prior to that I switched the RG over to the node where the DS is started manually.
Once I register the SUNW.ds6ldap instance in my RG, it won't start.
Log:
Jul 31 11:57:55 xxxx SC[SUNW.ds6ldap,hylas-ldap,ds--argolis-disks-ldapdata1-hylas,dsldap_svc_start]: [ID 833212 daemon.info] Attempting to start the data service under process monitor facility.
Jul 31 11:57:55 xxxx Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource ds--argolis-disks-ldapdata1-hylas status on node xxxx change to R_FM_ONLINE
Jul 31 11:57:55 xxxx Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource ds--argolis-disks-ldapdata1-hylas status msg on node xxxx change to <Completed successfully.>
Jul 31 11:57:55 xxxx Cluster.PMF.pmfd: [ID 887656 daemon.notice] Process: tag="hylas-ldap,ds--argolis-disks-ldapdata1-hylas,0.svc", cmd="/bin/sh -c /opt/SUNWdsee/ds6/bin/dsadm start /argolis/disks/ldapdata1/hylas", Failed to stay up.
I tried to execute the bold commandline... it quits with "Error: Missing subcommand".
Adding the missing quotes "/bin/sh -c \"/opt/SUNWdsee/ds6/bin/dsadm start /argolis/disks/ldapdata1/hylas\" would certainly help, but where do I apply the fix?
Maybe thats not the problem... any hint is appreciated.
TIA && rgds,
orknase

Answer 1

Hi, ludovicp!
dsadm start exec /path/to/instance works fine. The only time it doesn't start up is when I enable dsargolis-disks-ldapdata1-hylas in RG hylas-ldap and switch the RG online.
snip taken after dsadm start ...
dsadm info /argolis/disks/ldapdata1/hylas
Instance Path:               /argolis/disks/ldapdata1/hylas
Owner:                       root(root)
Non-secure port:             389
Secure port:                 636
Bit format:                  64-bit
State:                       Could be retrieved using Sun Cluster commands.
Server PID:                  12191
DSCC url:                    -
Sun Cluster resource group:  hylas-ldap
SMF application name:        -
Instance version:            D-A00So yes, it looks like a problem with the interaction SC/DS. The agent submits the same command. Thats why I thought the defect #6563445 is related to it. Oh well, I think on monday the service plan information will be available to this account and I will have a few more possibilities to check.
Rgds,
orknase
Message was edited by:
orknase