OpenVZ Forum: Support » Oopses in Glibc...

Home » General » Support » Oopses in Glibc...

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Oopses in Glibc... [message #12609 is a reply to message #12332]

Fri, 04 May 2007 07:31

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

Just an idea: glibc corrupted area can be detected due to 2 reasons:
- HW memory corruptions, so check your HW (http://wiki.openvz.org/Hardware_testing)
- Software memory corruptions. Yes, software can be faulty too :@)
The same software can work find with another kernel, since e.g. RHEL5 kernel has so called execschield feature, which randomizes address space and if software is not ready for this - can affect it. So you can try booting with "noexec=off" kernel option or try mainstream 2.6.18-OVZ kernel.

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

[Message index]

		Oopses in Glibc... By: m.s.tremer on Wed, 25 April 2007 09:21
		Re: Oopses in Glibc... By: Vasily Tarasov on Wed, 25 April 2007 13:42
		Re: Oopses in Glibc... By: m.s.tremer on Wed, 25 April 2007 16:11
		Re: Oopses in Glibc... By: Vasily Tarasov on Wed, 25 April 2007 16:24
		Re: Oopses in Glibc... By: m.s.tremer on Wed, 25 April 2007 16:33
		Re: Oopses in Glibc... By: Vasily Tarasov on Wed, 25 April 2007 17:58
		Re: Oopses in Glibc... By: m.s.tremer on Wed, 25 April 2007 18:13
		Re: Oopses in Glibc... By: dev on Fri, 04 May 2007 07:31

Previous Topic:	Can't use IPTables inside a VE - still broken
Next Topic:	Create private network between VPS not bound to NIC

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Feb 17 23:56:15 GMT 2026

Total time taken to generate the page: 0.18983 seconds