Highlighted
davidkrotil Super Contributor.
Super Contributor.
1264 views

Cluster resource in comatose

Hi,
I getting this error often, one node crashes and cluster resources from crashed node going to comatose with

Cannot bind server, failure reason = -632

When both nodes are online , migration is without any problem.

OES2015 SP1

I have many clusters and this error not everytime on same cluster.
Labels (1)
0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: Cluster resource in comatose

In article <davidkrotil.8ejvgn@no-mx.forums.microfocus.com>, Davidkrotil
wrote:
> I getting this error often, one node crashes and cluster resources from
> crashed node going to comatose with
>
> Cannot bind server, failure reason = -632
>
> When both nodes are online , migration is without any problem.


That makes me think that perhaps those cluster resources have
dependencies to one node that happens to be the crashed one. Or that the
dependency is unavailable such as if it was on the crashed node and
hasn't yet come up (timing?)
I would look carefully as the LDAP pointers involved, as well as LUM

perhaps the DotOutParser Utility may help nailing what they are failing
on (if you aren't already using it)
https://www.novell.com/documentation/oes2015/clus_admin_lx/data/dotoutpar
ser.html


Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
davidkrotil Super Contributor.
Super Contributor.

Re: Cluster resource in comatose

This error is after NCP bind command, this is only error, which I found anywhere on system.
0 Likes
davidkrotil Super Contributor.
Super Contributor.

Re: Cluster resource in comatose

I found the cause, SLP server was crashed. Should be more reliable in my opinion.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Cluster resource in comatose

davidkrotil;2478203 wrote:
I found the cause, SLP server was crashed. Should be more reliable in my opinion.


Depending on your environment, you can setup multiple SLP DA to point to.
Unless you're referring to the SLP service on the cluster node that crashed, so that it was unable to talk to the DA?
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.