You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assignee: mfriedrich
Status: Resolved (closed on 2017-01-11 16:39:24 +00:00)
Target Version: 2.6.1
Last Update: 2017-01-11 16:39:24 +00:00 (in Redmine)
Icinga Version: 2.6.0
Backport?: Not yet backported
Include in Changelog: 1
Setting up mysql-server-5.7 (5.7.16-1) ...
...
Preparing to unpack .../icinga2-ido-mysql_2.6.0-1_amd64.deb ...
Unpacking icinga2-ido-mysql (2.6.0-1) ...
Processing triggers for libc-bin (2.24-8) ...
Setting up icinga2-ido-mysql (2.6.0-1) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/icinga2-ido-mysql.conf
Creating config file /etc/dbconfig-common/icinga2-ido-mysql.conf with new version
Creating config file /etc/icinga2/features-available/ido-mysql.conf with new version
checking privileges on database icinga2 for icinga2@localhost: user creation needed.
granting access to database icinga2 for icinga2@localhost: success.
verifying access for icinga2@localhost: success.
creating database icinga2: success.
verifying database icinga2 exists: success.
populating database via sql... error encountered populating database:
mysql said: ERROR 1101 (42000) at line 24: BLOB, TEXT, GEOMETRY or JSON column "comment_data" can"t have a default value
dbconfig-common: icinga2-ido-mysql configure: noninteractive fail.
dbconfig-common: icinga2-ido-mysql configure: ignoring errors from here forwards
done.
dbconfig-common: flushing administrative password
Processing triggers for libc-bin (2.24-8) ...
Fix IDO MySQL schema for MySQL >= 5.7
Including an example upgrade removing the defaults.
NOTE: A schema update doesn"t seem to be needed, MySQL is updating
internally.
The problem comes up on fresh schema imports on MySQL 5.7.
refs #13633
Fix IDO MySQL schema for MySQL >= 5.7
NOTE: A schema update doesn"t seem to be needed, MySQL is updating
internally.
The problem comes up on fresh schema imports on MySQL 5.7.
fixes #13633
The text was updated successfully, but these errors were encountered:
This issue has been migrated from Redmine: https://dev.icinga.com/issues/13633
Created by mfrosch on 2016-12-16 09:28:48 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2017-01-11 16:39:24 +00:00)
Target Version: 2.6.1
Last Update: 2017-01-11 16:39:24 +00:00 (in Redmine)
Changesets
2016-12-16 10:34:02 +00:00 by mfrosch 5d1fd79
2016-12-16 13:01:05 +00:00 by mfrosch a2ecc5c
2016-12-16 14:17:55 +00:00 by mfrosch a6b62a5
2016-12-16 14:51:12 +00:00 by mfrosch ac24ed8
2017-01-11 16:37:17 +00:00 by mfrosch 399827c
The text was updated successfully, but these errors were encountered: