Thanks to all that responed. Well as fate would have it we had a problem that
crashed SAP and Oracle. So we just stoped and restarted each member of the
cluster (no reboots).
I have included all the responses that I have recived so far
Steve Coates
reSource Partner
Steve
Try the following on the machine.
a. Try to ping all the service names if its attached to an IP address.
b . If the above doesn't work a good way of resolving this could be a
microsoft way of rebooting the cluster which would reinitialize
everything.
c. If you do not want to the above try the following
a. /sbin/init.d/asemember stop (On both machines)
b. /sbin/init.d/aseam stop (On both machines)/
On the first machine (Master node)
a. /sbin/init.d/aseam start
b. /sbin/init.d/asemember start
c. Monitor the daemon.log file
(/var/adm/syslog.dated/<latest-file>/daemon.log and see all activities
have finished.
The above commands put together should fix the issue.
Balaji/
Hello Steve,
Try to restart the asedirector process : kill <pid-asedirector>
For me this works ( DU 4.0D patchkit#5, ASE 1.5 )
regards,
Piet Lauwen
When it gets in that state I have found that there is no obvious recovery.
I would reboot all members and NB if you favour one member to run all your
applications then shutdown the others first and reboot that favoured
member on its own before bringing the other members up. It will save you
a lot of grief.
stuart mckenzie
Steve,
Looks like ASE director is confused.
Kill it.
New one will be elected and the problem should go away. (I hope.)
Regards,
Chris Jankowski
Compaq - Professional Services.
Chris Jankowski - Senior Systems Consultant chris_at_lagoon.meo.dec.com
Compaq Computer Australia Pty Ltd tel.+61 3 92753622
564 St. Kilda Rd, Melbourne 3004, AUSTRALIA fax +61 3 92753453
Entities should not be multiplied needlessly. - William of Ockham, razor of
Received on Wed Jan 05 2000 - 14:24:12 NZDT