OpenVZ Forum


Home » General » Support » Kernel leak problems.
Kernel leak problems. [message #35052] Tue, 24 February 2009 10:31 Go to next message
pug123 is currently offline  pug123
Messages: 22
Registered: July 2008
Junior Member
Hello,

One vps is crashing the whole node. In the logs before crash I can see:
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=1023, copied_seq=1867683170, rcv_nxt=1867683820
skb->len=650, *seq=1867683170, skb->seq=1867683170, skb->end_seq=1867683820, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=895, copied_seq=512751676, rcv_nxt=512752421
skb->len=745, *seq=512751676, skb->seq=512751676, skb->end_seq=512752421, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=1023, copied_seq=1867683170, rcv_nxt=1867683820
skb->len=650, *seq=1867683170, skb->seq=1867683170, skb->end_seq=1867683820, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=895, copied_seq=512751676, rcv_nxt=512752421
skb->len=745, *seq=512751676, skb->seq=512751676, skb->end_seq=512752421, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=1023, copied_seq=1867683170, rcv_nxt=1867683820
skb->len=650, *seq=1867683170, skb->seq=1867683170, skb->end_seq=1867683820, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=895, copied_seq=512751676, rcv_nxt=512752421
skb->len=745, *seq=512751676, skb->seq=512751676, skb->end_seq=512752421, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=1023, copied_seq=1867683170, rcv_nxt=1867683820
skb->len=650, *seq=1867683170, skb->seq=1867683170, skb->end_seq=1867683820, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=895, copied_seq=512751676, rcv_nxt=512752421
skb->len=745, *seq=512751676, skb->seq=512751676, skb->end_seq=512752421, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=1023, copied_seq=1867683170, rcv_nxt=1867683820
skb->len=650, *seq=1867683170, skb->seq=1867683170, skb->end_seq=1867683820, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=895, copied_seq=512751676, rcv_nxt=512752421
skb->len=745, *seq=512751676, skb->seq=512751676, skb->end_seq=512752421, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=1023, copied_seq=1867683170, rcv_nxt=1867683820
skb->len=650, *seq=1867683170, skb->seq=1867683170, skb->end_seq=1867683820, offset=-1
KERNEL: assertion: flags&MSG_PEEK
VE5300 pid 31492 comm lighttpd
flags=0x0, len=895, copied_seq=512751676, rcv_nxt=512752421
skb->len=745, *seq=512751676, skb->seq=512751676, skb->end_seq=512752421, offset=-1


It seems that this user is running lighthttpd. After some time the server crashes at all and I see kernel panic. Please advise.

My kernel version is:
2.6.18-92.1.18.el5.028stab060.2PAE

(ovzkernel-PAE-2.6.18-92.1.18.el5.028stab060.2)
Re: Kernel leak problems. [message #35054 is a reply to message #35052] Tue, 24 February 2009 11:13 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hello,

I looked for this message in Internet and found some problems that might be related to your problem (just the same message no more). For example
https://bugzilla.redhat.com/show_bug.cgi?id=451804

Are you able to reproduce this problem? If yes, could you possibly check RedHat kernel 2.6.18-92.1.18.el5?
The full crash message is needed anyway.
Could you please provide it.
Don't hesitate to file a bug to OpenVZ bugzilla.
http://bugzilla.openvz.org/
Re: Kernel leak problems. [message #35057 is a reply to message #35054] Tue, 24 February 2009 12:47 Go to previous message
pug123 is currently offline  pug123
Messages: 22
Registered: July 2008
Junior Member
Hello,

Thank you for answer.

It could be hard as this is production server :/ For sure it it coused by user's lighthttpd. When he starts it then it flooding the server console with these messages.
Previous Topic: Problem with new Lenny Kernel
Next Topic: *SOLVED* Access two subnets on two different NICs from VE with venet adapter
Goto Forum:
  


Current Time: Sun Jun 16 12:07:40 GMT 2024

Total time taken to generate the page: 0.04125 seconds