X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7434E.C061CEF5@onstor-exch02.onstor.net>; Sun, 28 Jan 2007 18:39:51 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7434E.C061CEF5"
Content-class: urn:content-classes:message
Subject: RE: perforce is not responding
Date: Sun, 28 Jan 2007 18:39:51 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0133627F@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: perforce is not responding
Thread-Index: AcdCpq6RTGLoJ92uRWir6sUUGfI1CgAp0oA+
References: <BB375AF679D4A34E9CA8DFA650E2B04E0239255E@onstor-exch02.onstor.net>
From: "Ken Renshaw" <ken.renshaw@onstor.com>
To: "Brian DeForest" <brian.deforest@onstor.com>
Cc: "dl-Software" <dl-software@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7434E.C061CEF5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thanks Brian...I caught the trouble this time. The NTP daemon on liszt =
evidently didn't come up the last time the system was rebooted, with the =
result that it's time was off and running a few hours fast. 'Our' 10-11 =
PM outages were what Liszt thought was "Backup Time!" which explains the =
hard locks of the p4 database at unexpected times.

It shouldn't be a problem anymore. I've added a couple system health =
printouts to preface the autobuild emails and buildlogs to catch such =
things sooner.

Thanks again to all who pestered, er uh, I mean 'brought this to my =
attention' :)

-Ken=20


-----Original Message-----
From: Brian DeForest
Sent: Sat 1/27/2007 10:36 PM
To: Ken Renshaw
Cc: dl-Software
Subject: perforce is not responding
=20
I can ping 'liszt' but p4 just hangs.   Happened the other night to me =
as well but I forgot to mention it.   I recall this being a problem for =
a few people about a week ago also.   =20




------_=_NextPart_001_01C7434E.C061CEF5
Content-Type: text/html;
	charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.28">
<TITLE>RE: perforce is not responding</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Thanks Brian...I caught the trouble this time. The NTP =
daemon on liszt evidently didn't come up the last time the system was =
rebooted, with the result that it's time was off and running a few hours =
fast. 'Our' 10-11 PM outages were what Liszt thought was &quot;Backup =
Time!&quot; which explains the hard locks of the p4 database at =
unexpected times.<BR>
<BR>
It shouldn't be a problem anymore. I've added a couple system health =
printouts to preface the autobuild emails and buildlogs to catch such =
things sooner.<BR>
<BR>
Thanks again to all who pestered, er uh, I mean 'brought this to my =
attention' :)<BR>
<BR>
-Ken<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Brian DeForest<BR>
Sent: Sat 1/27/2007 10:36 PM<BR>
To: Ken Renshaw<BR>
Cc: dl-Software<BR>
Subject: perforce is not responding<BR>
<BR>
I can ping 'liszt' but p4 just hangs.&nbsp;&nbsp; Happened the other =
night to me as well but I forgot to mention it.&nbsp;&nbsp; I recall =
this being a problem for a few people about a week ago =
also.&nbsp;&nbsp;&nbsp;<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7434E.C061CEF5--
