OpenVZ Forum


Home » General » Support » OpenVZ problem or not ?
Re: OpenVZ problem or not ? [message #7543 is a reply to message #7489] Tue, 17 October 2006 11:34 Go to previous messageGo to previous message
dev is currently offline  dev
Messages: 1693
Registered: September 2005
Location: Moscow
Senior Member

glibc messages warn you about corrupted memory heap.
This can be due to numerous reasons:
1. application writes beyond the allocated memory ranges and thus corrupts some glibc data.
All the apaches theoretically can crash if you use the same version of httpd and mod_'s. You can try to debug it via running apache under njamd or similar memory debugger. It will point you the broken code.

2. It can be hardware memory corruption.
Check dmesg and /var/log/message output on suspicous messages like this:
MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
Bank 2: 940040000000017a


See more details here:
http://wiki.openvz.org/Machine_check_exception
http://wiki.openvz.org/Hardware_testing


http://static.openvz.org/userbars/openvz-developer.png
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How to install OpenVZ on Ubuntu ?
Next Topic: DDOS attack on VPS
Goto Forum:
  


Current Time: Sun Sep 01 06:24:15 GMT 2024

Total time taken to generate the page: 0.05895 seconds