Hi Herbert,
Just a quick nod that 1.1.5 works as promised on this end. Can not make it
Oops with netstat :).
take care,
JES
On Wed, 19 Nov 2003, Herbert Poetzl wrote:
On Tue, Nov 18, 2003 at 07:50:25PM -0400, James MacLean wrote:
Hi Herbert:
Hi James!
I really would appreciate if
On Tue, Nov 18, 2003 at 07:50:25PM -0400, James MacLean wrote:
Hi Herbert:
Hi James!
I really would appreciate if you could test the following:
take a 2.4.23-rc1 as you patched it, _without_ the RT stuff
This one Oopses. Fresh 2.4.22 + 23rc1 patch + vserver-1.1.3.
and a 2.4.22
I think that typically when servers respond like this that it's the disk I/O
subsystem that has locked up?
Sam
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
Hi Dariush,
Old vserver for me is fine (2.4.22 + c17). Wanted to make up a new kernel,
saw this new branch of Vserver with 2.4.23-rc1 patches ready to go, so
went that route :).
I also patched in/ turned on the realtime kernel. It patched clean, but
hey, who knows ;(. But the Oops suggests
On Tue, Nov 18, 2003 at 08:46:34AM -0400, James MacLean wrote:
Hi Dariush,
Old vserver for me is fine (2.4.22 + c17). Wanted to make up a new kernel,
saw this new branch of Vserver with 2.4.23-rc1 patches ready to go, so
went that route :).
I also patched in/ turned on the realtime
On Tue, 18 Nov 2003, James MacLean wrote:
take a 2.4.23-rc1 as you patched it, _without_ the RT stuff
This one Oopses. Fresh 2.4.22 + 23rc1 patch + vserver-1.1.3.
and a 2.4.22 with vs1.00 with the RT stuff
This one was Ok, as are the old vservers.
Arg, I tested this one without the
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,
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
Hi Herbert,
Been too long since I've been playing with kernel oops :(. I started to
write down the Oops screen and got too tired too quickly and missed
getting enough info. What happen to it being trapped in
/var/log/somefile ? I use to just run ksymoops on that and get what was
needed.
