Bug 1874446
| Summary: | mariadb is improperly configured after update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Hill <dhill> |
| Component: | mariadb | Assignee: | Michal Schorm <mschorm> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | damien.ciabrini, hhorak, ljavorsk, mbayer, mkocka, mmuzila, mschorm, SpikeFedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | mariadb-10.4.14-2.fc32 mariadb-10.4.14-2.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-05 18:32:26 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Duplicate of BZ: #1873999 FEDORA-2020-47f48474ae has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-47f48474ae FEDORA-2020-b6ef280648 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b6ef280648 FEDORA-2020-9c0d1f10a5 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9c0d1f10a5 FEDORA-2020-9c0d1f10a5 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9c0d1f10a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9c0d1f10a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-b6ef280648 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b6ef280648` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b6ef280648 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-9c0d1f10a5 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2020-b6ef280648 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |
1. Please describe the problem: /etc/my.cnf.d/mariadb-server.cnf contains the following: [mysqld] datadir=@MYSQL_DATADIR@ socket=@MYSQL_UNIX_ADDR@ log-error=@LOG_LOCATION@ pid-file=@PID_FILE_DIR@/@DAEMON_NO_PREFIX@.pid which prevents mariadb from starting with the following error message: Aug 30 17:35:22 zappa mysql-prepare-db-dir[1656168]: Database MariaDB is not initialized, but the directory @MYSQL_DATADIR@ is not empty, so initialization cannot be done. Aug 30 17:35:22 zappa mysql-prepare-db-dir[1656168]: Make sure the @MYSQL_DATADIR@ is empty before running mysql-prepare-db-dir. 2. Specify used package versions # dnf list installed | grep -i -e maria -e mysql -e galera 3. Does a systemd journal say anything about the issue? # journalctl -xe -u mariadb -u mysqld 4. Please check and attach the MariaDB or MySQL server log? ("/var/log/mariadb/mariadb.log" or "/var/log/mysql/mysqld.log") 5. Please check and paste your configuration here; remove sensitive information. # /usr/libexec/mysqld --print-defaults 5. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: