[MDEV-23061] Extra engines enabled through config are not loaded after initial installation (#2) Created: 2020-06-30 Updated: 2021-09-14 |
|
| Status: | Stalled |
| Project: | MariaDB Server |
| Component/s: | Platform Debian |
| Affects Version/s: | 10.5 |
| Fix Version/s: | 10.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Otto Kekäläinen |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | regression | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
It appears that the fix made for
Server restart makes it appear. On 10.4 it works normally, the engine is there right away, unless of course the system is affected by |
| Comments |
| Comment by Otto Kekäläinen [ 2020-07-01 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
I confirm this issue is present in 10.5.4:
I will look into this. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2020-07-01 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
By the way elenst, have you seen is this detected/visible on any test in buildbot.askmonty.org or any other CI system we have access to? | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Elena Stepanova [ 2020-07-01 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yes, it was happening massively in buildbot in the past days, after I removed the suppression for | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2020-07-03 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Debug "trace" of that maintainer scripts run during installation attached. MDEV-23061-debug.txt | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2021-04-04 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
This was maybe fixed via https://github.com/MariaDB/server/commit/7c2079f600bacbd4d24762159550b3d40ad856c1 in https://github.com/MariaDB/server/pull/1504. I have not yet had time to verify properly. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Elena Stepanova [ 2021-08-03 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
It still happens at least on 10.5.11
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2021-09-14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
i can verify this indeed happens if `apt install mariadb-server mariadb-plugin-rocksdb` is run and both are installed at the same time. This is because apt setups the package `mariadb-server` first:
The file `/etc/mysql/mariadb.conf.d/rocksdb.cnf` does not exist when mariadbd is started at 16 seconds past and thus is not loaded/activated. If `mariadb-plugin-rocksdb` is installed separately, it will trigger the systemd service `mariadb` to reload, but the trigger does not run when they are co-installed. Debian packages have a concept of pre-depends and mariadb-plugin-rocksdb could perhaps pre-depend on the server, but it seems a bit of a misuse of that directive and we would need to test first if it even has any effect on triggering the server restart. One option would be to somehow force the trigger or server restart via the `mariadb-plugin-rocksdb` postinst script. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2021-09-14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Maybe some adjustment to the triggers might help with this?
|