Hi Nicolas,
I have mysql-server-core-5.5 installed because of a dependancy from KDE
(kdepim - kmail - kdepim-runtime - akonadi-server - akonadi-backend-mysql
- mysql-server-core). I also have mysql-common installed, but *not* mysql-
server-5.5. mysql-server-core-5.5 and mysql-common are both at version
5.5.23-2 and I just upgraded both from 5.1 a few days ago.
The only config file I can see is /etc/mysql/my.cnf (attached). (The users
have no .mycnf (or whatever the name is) files.) It seems to be unchanged
from the one shipped with mysql-common.
Below are my experiments and results. As a quick summary, it looks like
/usr/sbin/mysqld fails when /etc/mysql/conf.d is not present, but works when
it is present even if it is empty. The mysql-server-5.5 package ships
/etc/mysql/conf.d (and the file mysqld_safe_syslog.cnf inside): I think a
simple solution to the problem would be for mysql-server-core-5.5 package to
ship an /etc/mysql/conf.d, either empty or with mysqld_safe_syslog.cnf inside.
(I think a better (upstream) solution would be for mysqld not to fail if that
directory is not present...)
1. On starting /usr/sbin/mysqld (as a regular user or root) from the command
line I get the error:
$ /usr/sbin/mysqld
/usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2)
Fatal error in defaults handling. Program aborted
There is no apparent log file in /var/log, in $HOME, or in the directory in
which the command was run.
This is the problem that kept amarok from working correctly for me.
2. If I made the empty directory /etc/mysql/conf.d:
$ /usr/sbin/mysqld
120515 17:48:11 [Warning] Can't create test file /var/lib/mysql/lenny.lower-
test
120515 17:48:11 [Warning] Can't create test file /var/lib/mysql/lenny.lower-
test
/usr/sbin/mysqld: Can't change dir to '/var/lib/mysql/' (Errcode: 2)
120515 17:48:11 [ERROR] Aborting
120515 17:48:11 [Note] /usr/sbin/mysqld: Shutdown complete
It's the same when run as root. Again, there is no apparent log file.
This solves the problem with amarok.
3. I also made the empty directory /var/lib/mysql:
120515 17:49:53 [Warning] Can't create test file /var/lib/mysql/lenny.lower-
test
120515 17:49:53 [Warning] Can't create test file /var/lib/mysql/lenny.lower-
test
120515 17:49:53 [Warning] One can only use the --user switch if running as
root
120515 17:49:53 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
120515 17:49:53 [ERROR] Can't open the mysql.plugin table. Please run
mysql_upgrade to create it.
120515 17:49:53 InnoDB: The InnoDB memory heap is disabled
120515 17:49:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120515 17:49:53 InnoDB: Compressed tables use zlib 1.2.7
120515 17:49:53 InnoDB: Using Linux native AIO
120515 17:49:53 InnoDB: Initializing buffer pool, size = 128.0M
120515 17:49:53 InnoDB: Completed initialization of buffer pool
120515 17:49:53 InnoDB: Operating system error number 13 in a file operation.
InnoDB: The error means mysqld does not have the access rights to
InnoDB: the directory.
InnoDB: File name ./ibdata1
InnoDB: File operation call: 'create'.
InnoDB: Cannot continue operation.
Running this as root is the same but without the 3 warning lines at the
beginning. Again, no logs.
This looks like it things are working correctly, but with no database files to
access in /var/lib/mysql.
4. After removing the two empty directories I created, /etc/mysql/conf.d
/var/lib/mysql, I installed mysql-server-5.5 and its dependencies (mysql-
client-5.5 libdbd-mysql-perl). Everything worked as expected: root could
start mysqld but a regular user could not because of the permissions on
/var/lib/mysql. /etc/mysql/conf.d was created. The logs in /var/log/mysql*
are strangely empty.
5. I purged mysql-server-5.5 (and mysql-client-5.5 libdbd-mysql-perl).
/etc/mysql/conf.d was removed, so back to step 1. (/var/lib/mysql was not
removed, presumably to avoid deleting data.)
Please let me know if I can provide anything further.
Best,
Jan
On Tuesday, May 15, 2012 02:56:17 PM Nicholas Bamber wrote:
Jan,
I've already replied. Actually we did need to know about this as per my
latest email. I hope the transition goes okay and sorry for the mess.
The Debian MySQL team got short staffed and now everything is a rush and
chaos.
On 15/05/12 22:42, Jan Medlock wrote:
Apologies for re-assigning, then.
Is there any additional info I can send (to either Amarok or MySQL
maintainers)?
On Tuesday, May 15, 2012 02:02:40 PM Modestas Vainius wrote:
reassign 672207 amarok 2.5.0-1
severity 672207 grave
tags 672207 - moreinfo
thanks
On 2012 m. of May 15 d., Tuesday 23:48:05 Nicholas Bamber wrote:
tag 672207 +moreinfo
thanks,
Please send:
1.) Whatever you have for config (Put '' in place of any passwords)
2.) log files of it working
3,) log files of it not working.
I, as Amarok maintainer, can confirm that