You are here
Last week I started getting "out of memory" errors in my 2009.6 mediawiki (MW) VM. After doing an apt-get upgrade, things would work fine for a while until the console would be soiled with error such as (see screenshot):
Out of memory: kill process 5023 (apache2) score 225331 or a child
Killed process 5023 (apache2)
Out of memory: kill process 4497 (mysqld) scrore 32182 or a child
Killed process 4497 (mysqld)
Firefox just shows a blank page, Chrome reports an error:
Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.
So i started comparing this MW to another very similar MW installation based off of the same 2009.6 ISO. I didn't have any problems there, but I also hadn't run the Linux upgrade yet. I compared LocalSettings, AdminSettings, made dumpbackups and mysqldump exports, just in case. But nothing I'd find would pinpoint the problem. So I upgraded the second MW as well. And this also led to failures on that VM. Clearly, something is not right in both installation when doing an upgrade. Apt-get must forget to correct something.
Both php5 and mysql5 were upgraded, as can be seen from the update log. Nothing was changed (by me) in any config files right before/after the update. Both VMs have 512MB but I bumped the first one up to 1GB to see if that helped. Same difference.
Even though the console shows the Out of memory error, both mysql.err and mysql.log in /var/log are empty.
Any ideas?
apt-get logs
Going thru the apt-get logs to see what was changed and adapted, I noticed that the VM upgraded itself from apache 2.2.8 to 2.2.9 and deposited to cfg files in /etc/apache2 that were marked as new but not merged with my existing cfg files:
So I checked out the new files but discovered nothing shocking, except the following mention:
# If you just change the port or add more ports here, you will likely also # have to change the VirtualHost statement in # /etc/apache2/sites-enabled/000-default # This is also true if you have upgraded from before 2.2.9-3 (i.e. from # Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and # README.Debian.gz NameVirtualHost *:80 Listen 80 <IfModule mod_ssl.c> # SSL name based virtual hosts are not yet supported, therefore no # NameVirtualHost statement here Listen 443 </IfModule>Caused by a manual MySQL root pwd change?
Could it be caused by a manual change of the MySQL root passwd and it not being in sync with the secret keys that are mentioned in the janadmin thread?
Just a hunch... if so, how do I reset the secret keys along with the MySQL root pwd?
Add new comment