Repository navigation
mariadb fails to start: configured pid file location does not exist #346
Description
Activity
- added a commit that references this issue
on Dec 19, 2022 - added a commit that references this issue
on Jan 4, 2023 Worse and furthermore, the pid file location hard coded in the method script causes mariadb to ignore a
pid_file=/x/ydirective in its config file.Sorry I missed this! Will get it fixed on Monday and backport to 2022Q4.
- added a commit that references this issue
on Jan 28, 2023 - added 2 commits that reference this issue
on Mar 12, 2023 - added a commit that references this issue
on Apr 28, 2023 - added a commit that references this issue
on Jun 2, 2023 - added a commit that references this issue
on Jul 4, 2023 - added a commit that references this issue
on Sep 2, 2023 - added a commit that references this issue
on Oct 11, 2023 25 remaining items
- added 13 commits that reference this issue
on May 14, 2026 - added a commit that references this issue
on Jun 15, 2026 - added a commit that references this issue
on Sep 6, 2026
Metadata
Metadata
Assignees
Labels
No labels
The supplied method script specifies a pid file location in a directory that does not exist, /var/run/mariadb. The method script cannot create the directory because it is already running as mariadb. For mysql, it looks like the approach taken was to place the pid file in /var/mysql, where the daemon does have write access.