Repository navigation
MariaDB goes straight to maintenance after installing via pkgsrc #356
Description
Activity
Do we actually even need a pid file if SMF is managing this process directly instead of wrapping it in a svc method script?
Sorry, there are two issues here:
- The versions that I fixed in mariadb fails to start: configured pid file location does not exist #346 and backported fixes for aren't actually building in 2022Q4 at the moment, which is why only the older 10.4 version is available.
- The fix for 10.4 (which I based my 10.5/10.6 fixes on and was fixed by someone else) wasn't backported.
I'll get working on both.
Ok I've fixed the builds of 10.5 and 10.6 packages in NetBSD@4033f2d and NetBSD@13b9b4a, and also fixed creating the initial databases on first run in NetBSD@76ca8ff
I'll get these backported to 2022Q4 and let you know when the packages are available.
Ok the following packages are now available in 2022Q4:
$ pkgin se mariadb-server mariadb-server-10.6.11 MariaDB 10.6, a free MySQL compatible database (server) mariadb-server-10.5.18 MariaDB 10.5, a free MySQL compatible database (server) mariadb-server-10.4.20nb9 MariaDB 10.4, a free MySQL compatible database (server)I've tested them all to check they all correctly start up on a clean system using the following routine:
$ pkgin in 'mariadb-server>10.4<10.5' $ /usr/sbin/svcadm enable -r svc:/pkgsrc/mariadb:default ..check for running service, test with "mysql -uroot".. $ /usr/sbin/svcadm disable svc:/pkgsrc/mariadb:default $ pkg_delete mariadb\* $ /usr/sbin/svccfg delete svc:/pkgsrc/mariadb $ rm -rf /var/mysql /var/log/mariadbRepeat for:
$ pkgin in 'mariadb-server>10.5<10.6' $ pkgin in 'mariadb-server>10.6'Reacted by Brian Ewell- added a commit that references this issue
on Mar 12, 2023 - added 2 commits that reference this issue
on May 2, 2023 - added a commit that references this issue
on Oct 13, 2024 - added a commit that references this issue
on Nov 13, 2024 14 remaining items
- added 12 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on May 24, 2026 - added a commit that references this issue
on Sep 6, 2026 - added a commit that references this issue
on Sep 26, 2026
Metadata
Metadata
Assignees
Labels
No labels
TL;DR: It appears that mariadb-server is currently configured to expect a mariadb:mariadb writable directory at
/var/run/mariadb. Unfortunately, manually creating one at that path doesn't survive a reboot.Steps to reproduce: