Re: Leap Second cause Cluster crashes for anyone?

From: LS Cheng <>
Date: Fri, 2 Jan 2009 16:40:09 +0100
Message-ID: <>

Not about your problem but having oprocd running when the third party cluster is running as well means the installation wasnt right, it's not a not recommended configuration but rather not supported



On Fri, Jan 2, 2009 at 3:47 PM, <> wrote:

> Some more info. We also use Veritas Clusterware, and apparently, also have
> oprocd running (which is not the recommended configuration). But we also
> have experienced it on clusters with no Veritas involved. For that, Oracle
> recommends "other non-VCS customers need to have CRS 10203 at recent MLR or
> BP patch + Solairs fix for CR#6595936"
> But setting css diagwait from the default value of 0.5 to 13, makes them
> immune, in either cases. Metalink has a note on setting this, which needs
> clusterware to be down on all nodes. But can be set only on and
> above.
> Regards
> Raj
> *Bjoern Rost <>*
> Sent by:
> 01/02/2009 09:35 AM
> Please respond to
> To
> cc
> Subject
> Re: Leap Second cause Cluster crashes for anyone?
> Hi Rajesh
> On Fri, 2009-01-02 at 15:00, wrote:
> > Nothing in the CRS logs. The OS logs have no messages except for
> > Solaris booting up again. For clusters where we had changed the css
> > diagwait to 13, no such issues.
> >
> > Anyone else experience this?
> We *might*. I am chasing some crash/reboot issues in a sol10 x64 cluster
> that I couldn't explain so far. nothing in crs logs, nothing in
> syslog/messages. Both machines use ntp to update local time. How do I
> change diagwait?
> But then again, i have another (very similar) cluster that does not show
> these problems.
> Bjoern
> --
> ------------------------------
> This communication is for informational purposes only. It is not intended
> as an offer or solicitation for the purchase or sale of any financial
> instrument or as an official confirmation of any transaction. All market
> prices, data and other information are not warranted as to completeness or
> accuracy and are subject to change without notice. Any comments or
> statements made herein do not necessarily reflect those of JPMorgan Chase &
> Co., its subsidiaries and affiliates. This transmission may contain
> information that is privileged, confidential, legally privileged, and/or
> exempt from disclosure under applicable law. If you are not the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution, or use of the information contained herein (including any
> reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any
> attachments are believed to be free of any virus or other defect that might
> affect any computer system into which it is received and opened, it is the
> responsibility of the recipient to ensure that it is virus free and no
> responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and
> affiliates, as applicable, for any loss or damage arising in any way from
> its use. If you received this transmission in error, please immediately
> contact the sender and destroy the material in its entirety, whether in
> electronic or hard copy format. Thank you. Please refer to
> for disclosures relating to UK
> legal entities.
Received on Fri Jan 02 2009 - 09:40:09 CST

Original text of this message