[debian-mysql] jessie -> stretch upgrade with MySQL 5.5

Mon Apr 10 20:00:16 UTC 2017

I spoke too soon. I see the aforementioned errors in the log file:

2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Using mutexes to ref
count buffer pool pages
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: The InnoDB memory
heap is disabled
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Mutexes and rw_locks
use GCC atomic builtins
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: GCC builtin
__atomic_thread_fence() is used for memory barrier
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Compressed tables use
zlib 1.2.8
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Using Linux native
AIO
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Using SSE crc32
instructions
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Initializing buffer
pool, size = 128.0M
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Completed
initialization of buffer pool
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Highest supported
file format is Barracuda.
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Creating tablespace
and datafile system tables.
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Tablespace and
datafile system tables created.
2017-04-10 19:48:36 140304128580992 [Warning] InnoDB: Resizing redo log
from 2*320 to 2*3072 pages, LSN=1600094
2017-04-10 19:48:36 140304128580992 [Warning] InnoDB: Starting to delete
and rewrite log files.
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Setting log file
./ib_logfile101 size to 48 MB
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Setting log file
./ib_logfile1 size to 48 MB
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Renaming log file
./ib_logfile101 to ./ib_logfile0
2017-04-10 19:48:36 140304128580992 [Warning] InnoDB: New log files
created, LSN=1600524
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: 128 rollback
segment(s) are active.
2017-04-10 19:48:36 140304128580992 [Note] InnoDB: Waiting for purge to
start
2017-04-10 19:48:36 140304128580992 [Note] InnoDB:  Percona XtraDB
(http://www.percona.com) 5.6.35-80.0 started; log sequence number
1595685
2017-04-10 19:48:36 140303495309056 [Note] InnoDB: Dumping buffer
pool(s) not yet started
2017-04-10 19:48:36 140304075331328 [ERROR] Incorrect definition of
table mysql.proc: expected column 'sql_mode' at position 14 to have type
set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA
2017-04-10 19:48:36 140304075331328 [ERROR] Incorrect definition of
table mysql.event: expected column 'sql_mode' at position 14 to have
type
set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'),
found type
set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
ERROR: 1136  Column count doesn't match value count at row 1
2017-04-10 19:48:36 140304128580992 [ERROR] Aborting

2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Using mutexes to ref
count buffer pool pages
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: The InnoDB memory
heap is disabled
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Mutexes and rw_locks
use GCC atomic builtins
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: GCC builtin
__atomic_thread_fence() is used for memory barrier
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Compressed tables use
zlib 1.2.8
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Using Linux native
AIO
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Using SSE crc32
instructions
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Initializing buffer
pool, size = 128.0M
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Completed
initialization of buffer pool
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Highest supported
file format is Barracuda.
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: 128 rollback
segment(s) are active.
2017-04-10 19:48:39 140567571205504 [Note] InnoDB: Waiting for purge to
start
2017-04-10 19:48:39 140567571205504 [Note] InnoDB:  Percona XtraDB
(http://www.percona.com) 5.6.35-80.0 started; log sequence number
1616614
2017-04-10 19:48:39 140566939551488 [Note] InnoDB: Dumping buffer
pool(s) not yet started
2017-04-10 19:48:39 140567571205504 [Note] Plugin 'FEEDBACK' is
disabled.

But my mysqld process starts after that, unlike yours.

Cheers,
-- 
Ondřej Surý <ondrej at sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Mon, Apr 10, 2017, at 21:37, Ondřej Surý wrote:
> Paul,
> 
> I have a couple of questions to help with debugging this issue, as I
> can't reproduce the issue locally, so it might some broken state of your
> system.
> 
> 1. is there anything else in the /var/log/apt/history.log and
> /var/log/apt/term.log? Was the mysqld process shutdown correctly?
> 
> 2. what architecture this is?  (NAS boxes might not be x86-based.)
> 
> 3. how does output of `ls -l /var/lib/mysql/` look like (especially the
> debian-<ver>.flag)?
> 
> 4. was the database initialized on mysql-5.5 or it was something even
> older?
> 
> Cheers,
> -- 
> Ondřej Surý <ondrej at sury.org>
> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
> Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
> fast DNS(SEC) resolver
> Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
> pečení chleba všeho druhu
> 
> On Fri, Apr 7, 2017, at 13:24, Paul Gevers wrote:
> > Hi Otto (and all the others),
> > 
> > I just upgraded my NAS to Stretch which (in hind-sight) was running
> > MySQL 5.5. After the upgrade, the daemon wasn't running, so I thought to
> > install mariadb-server. However, now I get the following message in the
> > /var/log/mysql/error.log:
> > 
> > 2017-04-07 12:45:49 3053044544 [ERROR] Incorrect definition of table
> > mysql.proc: expected column 'sql_mode' at position 14 to have type
> > set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBT\
> > RACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL3\
> > 23','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZE\
> > RO_DATE','INVA
> > 2017-04-07 12:45:49 3053044544 [ERROR] Incorrect definition of table
> > mysql.event: expected column 'sql_mode' at position 14 to have type
> > set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUB\
> > TRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL\
> > 323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_Z\
> > ERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTI\
> > ON','PAD_CHAR_TO_FULL_LENGTH'), found type
> > set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GR\
> > OUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','\
> > NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
> > ERROR: 1136  Column count doesn't match value count at row 1
> > 2017-04-07 12:45:49 3062317056 [ERROR] Aborting
> > 
> > The daemon still isn't running (see the final "Aborting").
> > 
> > Is this a known issue? Can I fix it? Does this (and/or the MySQL/MariaDB
> > situation) warrant a note in the release notes?
> > 
> > I already tried running mysql_upgrade but that fails:
> > paul at fuji ~ $ sudo /usr/bin/mysql_upgrade
> > Version check failed. Got the following error when calling the 'mysql'
> > command line client
> > ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> > '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")
> > FATAL ERROR: Upgrade failed
> > 
> > Paul
> > 
> > 
> > 
> > _______________________________________________
> > pkg-mysql-maint mailing list
> > pkg-mysql-maint at lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
> > Email had 1 attachment:
> > + signature.asc
> >   1k (application/pgp-signature)
> 
> _______________________________________________
> pkg-mysql-maint mailing list
> pkg-mysql-maint at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint