© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I don't know if this bug is still open, (or if my problem is related to another bug), but the 'released fix' hasn't been in the lucid repositories.
when I perform the following
sudo apt-get install mysql-server-5.1
this is the output...
___
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
tinyca mailx
The following NEW packages will be installed
mysql-server-5.1
0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 0B/7,008kB of archives.
After this operation, 15.0MB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously deselected package mysql-server-5.1.
(Reading database ... 271591 files and directories currently installed.)
Unpacking mysql-server-5.1 (from .../mysql-
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Setting up mysql-server-5.1 (5.1.41-
101027 15:46:57 [Note] Plugin 'FEDERATED' is disabled.
101027 15:46:57 InnoDB: Started; log sequence number 0 44233
101027 15:46:57 InnoDB: Starting shutdown...
101027 15:46:58 InnoDB: Shutdown completed; log sequence number 0 44233
start: Job failed to start
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
___
My concern is that this is the LTS version. As always I am upgrading after the version has been out for a while, in the expectation that problems like these would not occur.
My initial upgrade from 8.04 broke MySQL, and stopped my local test versions for a number of test web sites (drupal) and a test implementation of Sugar CRM I had going.
I assume that there is a similar problem in the 10.04 LTS server edition also ? if so that will be bad new for someone!
I hope someone out there is able to regress the 'fix released' notification, or at least confirm that my problems are not specific to my setup.
I followed m2nis' details on post 23 for removing my old mysql instalation (or rather I renamed the directories so as to retain my data tables), then I did the following
___
su mysql service mysql start
start: Rejected send message, 1 matched rules; type="method_call", sender=":1.50" (uid=112 pid=20679 comm="start) interface=
___
then so as to confirm that it is indeed not running...
___
ps aux|grep mysql
root 20762 0.0 0.1 3328 784 pts/0 S+ 22:40 0:00 grep mysql
___
During my upgrade (which I performed stepwise through the versions, as I wasn't being given the option to go directly from 8.04 to 10.04?) I was prompted to file a bug report about mysql, here is the link to it
https:/
The reason I think this is in fact somehow all related is because my var/log/syslog ouptut looks remarkable similar to the original posters
I am now going to try implementing the changes as suggested above, to see if that solves my problem.
David