X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C77871.8968909B@onstor-exch02.onstor.net>; Fri, 6 Apr 2007 10:32:23 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C77871.8968909B"
Content-class: urn:content-classes:message
Subject: Cluster daemons die when time is advanced
Date: Fri, 6 Apr 2007 10:32:23 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E032A6DDE@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Cluster daemons die when time is advanced
Thread-Index: Acd4cYlA3Ct6BInzQoaIwwL9VdCOXw==
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "dl-cstech" <dl-cstech@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C77871.8968909B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

EricC noticed this occurs when you change the time on a filer running
2.2.2.1 (using "system time set..."):

Apr  6 10:33:00 CSLAB2 : 0:0:pm:ERROR: pm_sig_handler:
/usr/local/agile/bin/cluster_server (pid 8741) exited with status 1
Apr  6 10:33:00 CSLAB2 : 0:0:nfxsh:NOTICE: cmd[5]: system time set
200704061033.00 : status[0]
Apr  6 10:33:01 CSLAB2 : 0:0:pm:ERROR: pm_sig_handler:
/usr/local/agile/bin/cluster_contrl (pid 23472) exited with status 0

It's consistently repeatable if you bump the time back or ahead a minute
or two.

Are cluster_contrl's and cluster_server's deaths on time change
intentional?

--
Eric Barrett - ONStor Support - 1-408-963-2407 - eric@onstor.com

ONStor US Support:
Phone: 1-866-726-3453; email: support@onstor.com



------_=_NextPart_001_01C77871.8968909B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Cluster daemons die when time is advanced</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">EricC noticed this occurs when you =
change the time on a filer running 2.2.2.1 (using &quot;system time =
set...&quot;):</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Apr&nbsp; 6 10:33:00 CSLAB2 : =
0:0:pm:ERROR: pm_sig_handler: /usr/local/agile/bin/cluster_server (pid =
8741) exited with status 1</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Apr&nbsp; 6 10:33:00 CSLAB2 : =
0:0:nfxsh:NOTICE: cmd[5]: system time set 200704061033.00 : =
status[0]</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Apr&nbsp; 6 10:33:01 CSLAB2 : =
0:0:pm:ERROR: pm_sig_handler: /usr/local/agile/bin/cluster_contrl (pid =
23472) exited with status 0</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">It's consistently repeatable if you =
bump the time back or ahead a minute or two.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Are cluster_contrl's and =
cluster_server's deaths on time change intentional?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">--</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">Eric Barrett - ONStor Support - =
1-408-963-2407 - eric@onstor.com</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">ONStor US Support:</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">Phone: 1-866-726-3453; email: =
support@onstor.com</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C77871.8968909B--
