From: sysadmin_at_qlusters.com
Date: Mon 17 Nov 2003 - 15:48:22 GMT
('binary' encoding is not supported, stored as-is)
('binary' encoding is not supported, stored as-is)
The e-mail you have sent to this domain (qlusters.com) did not reach its indended destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
---------
You may see the original e-mail below. If you feel that this is error message is incorrect or
you have a question then feel free to press "reply" to this e-mail and e-mail the Administrator.
Thank you,
Qlusters INC.
attached mail follows:
On Mon, Nov 17, 2003 at 08:53:56AM -0400, James MacLean wrote:
> Hi Matt,
>
> On my system, when it Oopses, it's down for the count. No ping or
> anything. Keyboard lights flashing just to point out it's in bad shape :).
when the keyboard leds start to flash, it's a panic
and you should capture/copy the stack trace (oops) and
feed it through ksymoops, this way, we could not only
pity you for the crash, but also try to figure out how
it happened ...
TIA,
Herbert
> I saw the oops this morning, but didn't copy all the register data and
> stack log as it is always so much to pencil down :), and I was hoping this
> was already being tracked down ;).
>
> Maybe I should grab that if 1.1.3 dies tomorrow am?
definitely ...
> JES
>
> On Mon, 17 Nov 2003, Matt Ayres wrote:
>
> > I have 2 servers who keep crashing, sometimes every few hours... I am
> > still working on a console solution so I don't know the exact place
> > where the problem is.
> >
> > The servers are in a "half hung" state, they respond to PING and will
> > open TCP connections, but they won't send any data back.
> >
> > Is this how yours responds or is it a hard lock?
> >
> > I've tried with 2.4.22-c17e, 2.4.23pre8-c17h and 2.4.22-vs1.0.0 all with
> > the same results.
> >
> > On Mon, 2003-11-17 at 06:00, James MacLean wrote:
> > > Hi folks,
> > >
> > > 2 nights in a row at 4:00am when netstat runs, the system is Oopsing. I
> > > was running vs1.1.2 and am now upgrading to vs1.1.3 but do not see
> > > anything that suggests a fix in in the diffs.
> > >
> > > Possibly I am the only lucky one :)? I remember this happening some time
> > > ago in earlier vservers, and someone new the fix. The Oops was within
> > > tcp_get_info if I am reading the System.map correctly.
> > >
> > > JES
> >
>
> --
> James B. MacLean macleajb_at_ednet.ns.ca
> Department of Education
> Nova Scotia, Canada
> B3M 4B2
>
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver