[MDEV-13207] PrivateDevices breaks systemd service on Debian 8.8 Created: 2017-06-29 Updated: 2023-01-10 Resolved: 2017-08-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Packaging |
| Affects Version/s: | 10.2.6 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Claudio Nanni | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback, systemd | ||
| Environment: |
Debian 8.8 |
||
| Issue Links: |
|
||||||||
| Description |
|
The option in the systemd MariaDB service file: PrivateDevices=true Prevents the service to start on Debian 8.8. To make the service start that must be set to 'false'. |
| Comments |
| Comment by Daniel Black [ 2017-06-29 ] |
|
Why? What device is being accessed? Is this because if innodb storage on raw devices or similar? Documentation indicate sometimes this workaround is needed https://mariadb.com/kb/en/mariadb/systemd/. |
| Comment by Daniel Black [ 2017-07-04 ] |
|
journalctl -u mariadb might show this information Your my.cnf file(s) might also provide a way to reproduce this. |
| Comment by Daniel Black [ 2023-01-10 ] |
|
Seems likely caused by proxmox, or maybe containers, or whatever is running systemd not providing sufficent access in the cgroup heirarchy. https://stackoverflow.com/questions/75076342/mariadb-wont-start-suddenly/75076999#75076999 I suspect whatever cause its fixed by now or there would be a lot more watchers on this issue. |