Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2

2015-02-18 Thread Otto Kekäläinen 
I will close this issue unless the original reporter adds some more
information that would enable us to reproduce the bug.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773223


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2

2015-02-18 Thread Gilles Mocellin 
Hello,

I can't reproduce it anymore.
I think you can close it.

Le 18 février 2015 12:22:44 CET, Otto Kekäläinen o...@seravo.fi a écrit :
I will close this issue unless the original reporter adds some more
information that would enable us to reproduce the bug.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773223


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2

2014-12-15 Thread Otto Kekäläinen 
Thank you Gilles for reporting this.

The mysqld init script should call on scripts that run mysql_upgrade,
which is suppose to handle situations like this. Have you tried
running mysql_upgrade manually?
This issue is possibly an upstream bug and I have asked upstream devs
for help regarding this.

Regarding the debconf string: thanks for spotting them, I just fixed
them in commit 
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=795666b08a79cfc418d9c6e7fac690ccdea41539


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2

2014-12-15 Thread Gilles Mocellin 

Le 15/12/2014 22:55, Otto Kekäläinen a écrit :

Thank you Gilles for reporting this.

The mysqld init script should call on scripts that run mysql_upgrade,
which is suppose to handle situations like this. Have you tried
running mysql_upgrade manually?

I just tried, but it said it's already upgraded.
I force the run and see that it does not touch mysql.innodb_table_stats ...

This issue is possibly an upstream bug and I have asked upstream devs
for help regarding this.
Probably, as I found on the Web some similar problems with even MySQL 
itself and that table.

Regarding the debconf string: thanks for spotting them, I just fixed
them in commit 
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/commit/?id=795666b08a79cfc418d9c6e7fac690ccdea41539

Ah ! I haven't even seen that, it's reportbug that lists debconf strings !


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773223: [debian-mysql] Bug#773223: mariadb-server-10.0: Fails to upgrade to 10.0.15-2

2014-12-15 Thread Gilles Mocellin 
Finaly, after retrying multiple times dpkg --configure -a, 
mariadb-server-10.0 succeed.


There's some logs I hadn't see before (not in the output of journalctl 
for the mysql unit) :


   Dec 15 23:17:44 guitare mysqld_safe[10908]: 141215 23:17:44 [ERROR]
   mysqld: Can't lock aria control file
   '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will
   retry for 30 seconds
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [ERROR]
   mysqld: Got error 'Could not get an exclusive lock; file is probably
   in use by another process' when trying to use aria control file
   '/var/lib/mysql/aria_log_control'
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [ERROR]
   Plugin 'Aria' init function returned error.
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [ERROR]
   Plugin 'Aria' registration as a STORAGE ENGINE failed.
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 2014-12-15 23:18:15
   7fde210c8780 InnoDB: Warning: Using innodb_additional_mem_pool_size
   is DEPRECATED. This option may be removed in future releases,
   together with the option innodb_use_sys_malloc and with the InnoDB's
   internal memory allocator.
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Using mutexes to ref count buffer pool pages
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: The InnoDB memory heap is disabled
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Mutexes and rw_locks use GCC atomic builtins
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Memory barrier is not used
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Compressed tables use zlib 1.2.8
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Using Linux native AIO
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Using CPU crc32 instructions
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Initializing buffer pool, size = 200.0M
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Completed initialization of buffer pool
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [ERROR]
   InnoDB: Unable to lock ./ibdata1, error: 11
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Check that you do not already have another mysqld process
   using the same InnoDB data or log files.
   Dec 15 23:18:15 guitare mysqld_safe[10908]: 141215 23:18:15 [Note]
   InnoDB: Retrying to lock the first data file
   Dec 15 23:18:16 guitare mysqld_safe[10908]: 141215 23:18:16 [ERROR]
   InnoDB: Unable to lock ./ibdata1, error: 11
   Dec 15 23:18:16 guitare mysqld_safe[10908]: 141215 23:18:16 [Note]
   InnoDB: Check that you do not already have another mysqld process
   using the same InnoDB data or log files.
   Dec 15 23:18:17 guitare mysqld_safe[10908]: 141215 23:18:17 [ERROR]
   InnoDB: Unable to lock ./ibdata1, error: 11

...

I don't know if I had a running process (mysqld_safe), I don't think as 
I have checked multiple times with ps -ef | grep mysql after stopping 
mysql and then starting it...



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org