AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20090317095859.2765c559@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:mail.onstor.net
NSV:
SSH:
R:<caeli.collins@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@exch1.onstor.net/INBOX	0	2779531E7C760D4491C96305019FEEB52AC760286C@exch1.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 17 Mar 2009 09:59:20 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: Caeli Collins <caeli.collins@onstor.com>
Subject: Re: Logfile turned over at the crucial time of system events
Message-ID: <20090317095920.63b9ff0c@ripper.onstor.net>
In-Reply-To: <2779531E7C760D4491C96305019FEEB52AC760286C@exch1.onstor.net>
References: <200903171523.n2HFNmL27060@mailhost-rtp.css.glasshouse.com>
	<2779531E7C760D4491C96305019FEEB52AC760286C@exch1.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Caeli,

He mentions elogs and "event logs."  Pardon my ignorance, but aren't
they the same thing?  In fact, I don't know what "event logs" would be
if that doesn't refer to elogs.  This would help me to understand this
problem a little better.

Cheers,

a


On Tue, 17 Mar 2009 08:36:19 -0700 Caeli Collins
<caeli.collins@onstor.com> wrote:

> It is very frustrating.
> 
> We've escalated a defect for it - 26330.
> 
> Please add your observations to it.
> 
> Caeli
> 
> 
> ________________________________
> From: Alan Cooke (Glasshouse)
> Sent: Tuesday, March 17, 2009 8:24 AM
> To: dl-cstech
> Subject: Logfile turned over at the crucial time of system events
> 
> Hi All,
> Is there an explanation or work going on about the elogs having
> "logfile turned over" in the messages file when some kind of event
> was occurring. I have seen this several times and it is very
> frustrating.
> 
> An example is Brevan Howard case 11870.
> Customer gets an email:
> Message : filesystem exception occurred on frontoffice2_vol1
> Time : Mar 13 19:40:49 2009
> 
> The overnight elogs show for that time:
> 
> Mar 13 18:00:01 onstor2 newsyslog[32082]: logfile turned over
> 
> Mar 13 22:00:01 onstor2 newsyslog[28687]: logfile turned over
> 
> 
> 
> But the events logs caught it:
> 
> Mar 13 19:40:42 onstor2 : 0:0:auth_agent:ERROR: nfxldap_getGroupId:
> Failed to send LDAP query. VS=3, class=125 key=shared-shares1-risk
> (traverse)
> 
> Mar 13 19:40:46 onstor2 : 1:3:efs:ERROR: 22931: FS: frontoffice2_vol1
> 0x400000000aa - amDeltaGetExtent - req - fs_yield:3431 event timeout
> on user write, startTime Fri Mar 13 19:10:44 2009, currTime Fri Mar
> 13 19:40:46 2009 (ra 0xffffffff8306dd74)
> 
> Mar 13 19:40:46 onstor2 : 1:3:efs:WARNING: 22932: FS:
> frontoffice2_vol1 0x400000000aa - amDeltaGetExtent - buf - Volume
> Exception: frame[0] = 0xffffffff830530d8
> 
> 
> 
> So on this occasion we were lucky but often there is just no clues.
> 
> 
> 
> Anyone know why this happens? Should I log a defect?
> 
> 
> 
> Regards ... Alan.
> 
> 
> 
