> package mysql-server-5.1 5.1. > keywords in config files and show a reasonable message instead of just > ideally, ubuntu install script should be intelligent and detect outdated > most of them do not show the deamon.log files so i can't tell for sure. ![]() > this might also apply to the other recently submitted mysqld bugs, but FAIL Starting MySQL database server: mysqld. > Oct 6 09:59:30 asterios mysqld: 091006 9:59:30 /usr/sbin/mysqld: When running the command sudo service mysql start this is the output. > the daemon.log attached to this bug shows the same as mine: > problem (this is because they removed berkeley db support in mysql) > config file, removing "skip-bdb" from /etc/mysql/my.cnf solved the > in my case the mysql server failed to start because of the outdated I haven't looked at what went wrong with apparmor perhaps someone here will explain it and save me the trouble. At this point things are looking good, although my testing has been very limited. The GRUB_CMDLINE_LINUX_DEFAULT="quiet splash apparmor=0" work-around allowed me to install and configure MySQL 5.1. Perhaps the six month upgrade cycle is too aggressive? I understand that upgrades are a major support hassle, but if we want common users to embrace Ubuntu we are going to need a smooth upgrade process. I am a technical user, and I keep my systems in good order, so it is disappointing that we are seeing this sort of update trouble. This is the second update in a row that had some major failure for me (jaunty and karmic). The GRUB_CMDLINE_ LINUX_DEFAULT= "quiet splash apparmor=0" work-around allowed me to install and configure MySQL 5.1. To resolve it, first check the user that your mysqld is attempting to run as this will be the user 'mysql' in a default Debian install (I assume it should be the same for Ubuntu) to verify this, check /etc/mysql/my.cnf and look for a 'user xxx' line. Of course purging caused many of my installed applications to be removed, so it's been an ongoing hassle. Not finding the exact cause of the error, I tried going back to 5.0, and ultimately purged MySQL and tried a fresh install. I went in and tried reinstalling from Synaptic, and that's when I got this error. It was only then that I realized that karmic included an "upgrade" to MySQL 5.1. Everything seemed to update okay, but later when I went to run a MySQL backup I couldn't do it. ![]() I had this problem on a vanilla update from jaunty to karmic. Title: package mysql-server-5.1 5.1.37-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProcVersionSign ature: Ubuntu 2.6.31- 11.38-generic Package mysql-server-5.1 is not configured yet.ĭpkg: error processing mysql-server (-configure):ĭependency problems - leaving unconfiguredĮrrorMessage: subprocess installed post-installation script returned error exit status 1 Mysql-server depends on mysql-server-5.1 however: Subprocess installed post-installation script returned error exit status 1ĭpkg: dependency problems prevent configuration of mysql-server: Invoke-rc.d: initscript mysql, action "start" failed.ĭpkg: error processing mysql-server-5.1 (-configure): # localhost which is more compatible and is not less secure.Setting up mysql-server-5.1 (5.1.37-1ubuntu4). # Instead of skip-networking the default is now to listen only on General_log_file = /home/tangr/mysql-logs/mysql.log
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |