Description of problem:
I assume, who ever wants to use toku needs this fixed asap, so severity = high.
Feb 2 13:37:25 s36 systemd: /usr/lib/systemd/system/mariadb.service.d/tokudb.conf:1: Assignment outside of section. Ignoring.
Content #### /usr/lib/systemd/system/mariadb.service.d/tokudb.conf :
someone is missing his [service] header...
Version-Release number of selected component (if applicable):
# rpm -qf /usr/lib/systemd/system/mariadb.service.d/tokudb.conf
A) HOW can two installed packages be the source of one file?
RPM/dnf do prevent this by default, afaik.
B) Does mariadb run without toku .. in other words: can i just remove it without consequences ? ( myisam and innodb fans here )
C) as the database has run without an error for a week, libjemalloc.so.2 seems not to be needed on init of the database itself. If toku is not initalized later( i.e. when needed), ask yourself : is that line necessary at all ?
Jut to not leave this without a response:
I started the work on it a while back - based on: https://bugzilla.redhat.com/show_bug.cgi?id=1668375
In F29+ there should be fixes available in either stable or testing repo.
As a part of more changes, I weakend the dependency on TokuDB SE, so it won't be pulled in by default.
Here is a commit that fixes the issue:
see line 1078 for the fix
As F28 is still maintained, it should get this patch too.
mariadb-10.2.21-3.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2dde8b87a5
mariadb-10.2.21-3.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2dde8b87a5
mariadb-10.2.21-3.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.