I also encountered that problem and couldn't find the issue in the
pre-/postinst or any other script so i did an ugly workaround to
complete the update. At your terminal enter:
[root@host] sleep 0.1 chown mysql:mysql /var/lib/mysql/* -R;
[root@host] aptitude safe-upgrade
The following partially
I have just encountered this issue as well. After upgrading the server
would not start with the same error message as the original server. I do
use InnoDB databases by default.
Output of my syslog:
Dec 18 17:42:04 localhost mysqld_safe[30287]: 131218 17:42:04 [Note] Plugin
'FEDERATED' is
Hi,
have you configured --log-error within my.cnf? See [0]
What does the error log says?
This is most likely due to custom configuriation below /etc/mysql/conf.d/
[0] http://dev.mysql.com/doc/refman/5.5/en/error-log.html
Cheers
B
--
To UNSUBSCRIBE, email to
Excerpts from Gary Dale's message of 2013-07-06 21:39:32 -0700:
Package: mysql-server-5.5
Version: 5.5.31+dfsg-0+wheezy1
Followup-For: Bug #682232
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading a server
Package: mysql-server-5.5
Version: 5.5.31+dfsg-0+wheezy1
Followup-For: Bug #682232
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading a server from squeeze to wheezy
* What exactly did you do (or not do) that was
Hello,
I have encountered this problem second time.
The upgrade from 5.1.49-3 to 5.5.31+dfsg-0+wheezy1 resulted in mysql server
not starting, which even breaks the mysql server installation, the errors
are the same as in this bugreport.
On one of machines, mysql is slightly used, on another
Package: mysql-server-5.5
Followup-For: Bug #682232
Debian Release: wheezy
I upgraded from squeeze to wheezy.
I have this bug.
I started mysqld with innodb_force_recovery = 1. Then, verified that none
of my tables actually used InnoDB by the following query:
SELECT table_schema, table_name
Hi Sergio, thanks for taking the time to report a bug.
Can you include your entire /etc/mysql/my.cnf And also a listing of
your datadir (usually /var/lib/mysql). I think the answer, since you
have no innodb tables, is to rm /var/lib/mysql/ib*. I have tested the
squeeze - wheezy upgrade and it
Clint:
/etc/mysql/my.cnf Attached.
A listing of my datadir is below.
And yes the answer was to rm /var/lib/mysql/ib*
After do that I can run mysqld normally with innodb_force_recovery = 0
Thanks for your help and work.
Regards.
Sergio Vernis
Debian:/var/lib/mysql# ls -la
total 20612
Hi -
On Fri, Jul 20, 2012 at 4:03 PM, Antti-Juhani Kaijanaho a...@debian.org wrote:
Package: mysql-server-5.5
Version: 5.5.24+dfsg-4
Severity: grave
Justification: renders package unusable
During an upgrade from squeeze to wheezy, I got this:
Setting up mysql-server-5.5 (5.5.24+dfsg-4)
On Sat, Jul 21, 2012 at 00:22:13 +0300, Antti-Juhani Kaijanaho wrote:
Julien, I notice you added a moreinfo tag without asking a question of me.
What info do you require of me?
That was probably before I saw your syslog, since for some reason you
replied out of thread.
Cheers,
Julien
On Fri, Jul 20, 2012 at 09:06:12PM +0100, Nicholas Bamber wrote:
After that relevant sections from syslog please.
Already sent several hours before your mail.
--
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
On Fri, Jul 20, 2012 at 10:24:08PM +0200, Julien Cristau wrote:
There's nothing to fix AFAICT, logcheck configuration doesn't need to be
readable by non-root.
Quite.
Julien, I notice you added a moreinfo tag without asking a question of me.
What info do you require of me?
--
Antti-Juhani
Package: mysql-server-5.5
Version: 5.5.24+dfsg-4
Severity: grave
Justification: renders package unusable
During an upgrade from squeeze to wheezy, I got this:
Setting up mysql-server-5.5 (5.5.24+dfsg-4) ...
[ ok ] Stopping MySQL database server: mysqld.
[FAIL] Starting MySQL database server:
On Fri, Jul 20, 2012 at 4:03 PM, Antti-Juhani Kaijanaho a...@debian.org wrote:
[FAIL] Starting MySQL database server: mysqld . . . . . . . . . . . . . .
failed!
Indeed, starting manually fails as well:
What do the logs (syslog etc) say?
Olaf
--
To UNSUBSCRIBE, email to
Package: mysql-server-5.5
Followup-For: Bug #682232
What are the etc logs? Anyway, /var/log/mysql* logs do not contain anything
relevant:
$ LC_ALL=C ls -l /var/log/mysql* | grep 'Jul 20'
-rw-r- 1 mysql adm0 Jul 20 17:05 /var/log/mysql.err
-rw-r- 1 mysql adm0 Jul 20 17:05
Package: mysql-server-5.5
Version: 5.5.24+dfsg-4
Followup-For: Bug #682232
I worked around this by the following:
First, started mysqld with innodb_force_recovery = 1. Then, verified that none
of my tables actually used InnoDB by the following query:
SELECT table_schema, table_name FROM
-- Configuration Files:
/etc/logcheck/ignore.d.paranoid/mysql-server-5_5 [Errno 13] Permission
denied: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_5'
/etc/logcheck/ignore.d.server/mysql-server-5_5 [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/mysql-server-5_5'
On Fri, Jul 20, 2012 at 21:06:12 +0100, Nicholas Bamber wrote:
-- Configuration Files:
/etc/logcheck/ignore.d.paranoid/mysql-server-5_5 [Errno 13] Permission
denied: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_5'
/etc/logcheck/ignore.d.server/mysql-server-5_5 [Errno 13]
19 matches
Mail list logo
