[MDEV-10049] MariaDB upgrade fails in postinst (DEB) Created: 2016-05-10  Updated: 2019-05-28  Resolved: 2019-05-28

Status: Closed
Project: MariaDB Server
Component/s: Packaging
Affects Version/s: 10.0.25
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Arjen Lentz Assignee: Sergey Vojtovich
Resolution: Won't Fix Votes: 1
Labels: None
Environment:

Debian Linux, Ubuntu Linux

Issue Links:
Relates
relates to MDEV-8437 plugin variables conflict with bootst... Closed

 Description   

mariadb-server-10.0 package was failing with exit code 7.
After trying to track down the exact cause using a number of manual debug techniques we found the error was happening when running "/bin/bash /usr/bin/mysql_install_db --rpm --user=mysql --disable-log-bin" in the postinst script. This was because variables in the my.cnf file were not recognised.

The following varliables needed to be commented out for it to run:

query_response_time_stats=ON
server_audit_output_type=syslog
server_audit_logging=ON
server_audit_events=QUERY_DDL

Uncommenting them after the upgrade seems to be causing no issues.



 Comments   
Comment by Arjen Lentz [ 2016-05-10 ]

I should note we've had this fail on a number of versions, the upgrade to 10.0.25 being just the latest.

Comment by Elena Stepanova [ 2016-05-10 ]

arjen,

So, you have these plugins installed? Or are they loaded upon server startup?

Comment by Arjen Lentz [ 2016-05-11 ]

Hi Elena!
They are in the mysql.plugins table.

Comment by Elena Stepanova [ 2016-05-11 ]

This problem was solved in 10.1 in the scope of MDEV-8437.

svoj, danblack, do you think it's possible and reasonable to backport the fix to 10.0?

Comment by Daniel Black [ 2016-05-12 ]

https://github.com/MariaDB/server/commit/60ad339 and https://github.com/MariaDB/server/commit/8e40f9b are the 10.1 commits.

It looks like both concepts can be applied to 10.0 where the file location is debian/dist/

{Ubuntu|Debian}

/mariadb-server-10.0.postinst.

Comment by Sergey Vojtovich [ 2019-05-28 ]

10.0 is EOL now, so it looks like there's nothing to fix. Should be fixed in 10.1+.

Generated at Thu Feb 08 07:39:17 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.