Ubuntu LAMP server issue - mysql start error

  • Thread starter Thread starter rolfbeethoven
  • Start date Start date
R

rolfbeethoven

Guest
I'm running the Ubuntu Hardy standard OpenVZ template that I downloaded from the proxmox web interface. I'm trying to make it into a LAMP server, but when I install mysql, I get the error shown below. I'm using a bridge ethernet and have successfully ssh'd in to work in the terminal. I found a reference about mysql not working properly until one edits the init.d script, however I wasn't able to find what changes need to be made or discover by looking at the script what is going wrong. Is there a good guide on making a LAMP server in OpenVZ? This has to be one of the most common uses for a guest OS.

Thanks.


root@samba:~# apt-get install mysql-server-5.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
mysql-server-5.0 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 49 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up mysql-server-5.0 (5.0.51a-3ubuntu5.8) ...
* Stopping MySQL database server mysqld [ OK ]
* Starting MySQL database server mysqld [fail]
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.0 (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
mysql-server-5.0
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@samba:~#
 
Thanks. I double the memory, swap and HD space (mem/swap to 1024, HD to 16) and it worked! I was read the link that you mentioned before, but I obviously missed something.

From the status screen I could see that anything was "in the red". How could I have determined which parameter needed to be boosted?

Also, the status still shows the old parameters (mem/swap at 512). Did I really change them?

Thx.
 
If your run out of memory you will see this in the syslog of your container (just see /var/log/syslog inside your ubuntu).

on the host or guest just take a look on the failcounts ('user_beancounters'):

Code:
 cat /proc/user_beancounters