summaryrefslogtreecommitdiff
path: root/support-files/mariadb@.service.in
Commit message (Collapse)AuthorAgeFilesLines
* systemd: revert to KillMode=control-group for galeraDaniel Black2018-01-291-1/+0
| | | | | | When galera is used we want a stop to kill off not only the mysqld process but the entire process group created by galera to perform sst or wsrep_notify_cmd.`
* MDEV-13809: [service] should [Service] in systemd service filesDaniel Black2017-12-191-2/+3
|
* MDEV-12128: systemd - add Documentation= directivesDaniel Black2017-12-191-1/+3
|
* properly set paths in systemd unit filesChristian Hesse2017-03-071-10/+10
| | | | | Use variables in systemd unit file templetes to properly set paths in final systemd unit files.
* spelling fixesklemens2017-03-071-2/+2
|
* MDEV-10538: MariaDB fails to start without galera_recovery in systemd modeNirbhay Choubey2016-08-221-6/+9
| | | | | Update ExecStartPre scripts to not fail if 'galera_recovery' script is not available.
* MDEV-10404 - Improved systemd service hardening causes SELinux problemsSergey Vojtovich2016-08-171-1/+2
| | | | Disabled NoNewPrivileges until SELinux policy is fixed.
* MDEV-10298: Systemd hardeningCraig Andrews2016-07-121-0/+10
| | | | Add ProtectSystem=full, NoNewPrivileges=true, PrivateDevices=true, and ProtectHome=true to the systemd units.
* MDEV-10004: Galera's pc.recovery process fails in 10.1 with systemdNirbhay Choubey2016-06-271-2/+20
| | | | | | | | | | | | | | Galera recovery process works in two phases. In the first phase, mysqld is started as non-daemon with --wsrep-recover to recover and fetch the last logged global transaction ID. This ID is then used in second phase as the start position (--wsrep-start-position=XX) to start mysqld as daemon. As this process was implemented in mysqld_safe script, the recovery did not work when server was started using systemd. Fixed by introducing a shell script (wsrep_recovery.sh) that mimics the first phase of the recovery process.
* MDEV-10145: Systemd fails to start mysqld in multi-instance modeNirbhay Choubey2016-06-271-2/+6
| | | | | | --defaults-xxx options must be placed before all other options in the command line. Also moved MYSQLD_OPTS at the end so that its options take precedence.
* MDEV-9095 - [PATCH] systemd capability for --memlockSergey Vojtovich2015-12-221-0/+3
| | | | | | | Adjust systemd files to enable CAP_IPC_LOCK to allow rootless mlockall (triggered by memlock option). This is amended version of a patch originally submitted by Daniel Black.
* MDEV-8995: systemd - 16K open-files-limit by defaultDaniel Black2015-11-071-1/+1
|
* MDEV-9007: systemd - service mariadb bootstrapDaniel Black2015-11-021-1/+0
| | | | Now this error out and refers to galera_new_cluster.
* MDEV-427: systemd - use galera_new_cluster instead of bootstrapDaniel Black2015-11-021-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use galera_new_cluster instead. systemctl start mariadb@bootstrap will generate error message, use_galera_new_cluster.conf is the name of the file that will generate this error. Output: Job for mariadb@bootstrap.service failed. See "systemctl status mariadb@bootstrap.service" and "journalctl -xe" for details. ● mariadb@bootstrap.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb@.service; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/mariadb@bootstrap.service.d └─use_galera_new_cluster.conf Active: failed (Result: exit-code) since Thu 2015-10-15 19:27:52 CEST; 5s ago Process: 24334 ExecStart=/usr/bin/false (code=exited, status=1/FAILURE) Process: 24330 ExecStart=/usr/bin/echo Please use galera_new_cluster to start the mariadb service with --wsrep-new-cluster (code=exited, status=0/SUCCESS) Main PID: 24334 (code=exited, status=1/FAILURE) Oct 15 19:27:52 spaceman systemd[1]: Starting MariaDB database server... Oct 15 19:27:52 spaceman systemd[1]: mariadb@bootstrap.service: main process exited, code=exited, status=1/FAILURE Oct 15 19:27:52 spaceman systemd[1]: Failed to start MariaDB database server. Oct 15 19:27:52 spaceman systemd[1]: Unit mariadb@bootstrap.service entered failed state. Oct 15 19:27:52 spaceman systemd[1]: mariadb@bootstrap.service failed.
* MDEV-426: systemd PermissionsStartOnly=true by defaultDaniel Black2015-10-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | mariadb-service-convert during migration can create a file containing ExecStartPre=/usr/sbin/sysctl -q -w vm.drop_caches=3 if the users my.cnf contains [mysqld_safe] flush_caches. This sysctl entry change requires root access. No existing ExecStartPre requires execution requires execution as another user. There is a comment in the mariadb{,@}.service.in that indicates mysqld_install which would require -u mysql to explicity change user to mysql from root since PermissionsStartOnly=true. Otherwise the following error would be generated: Oct 14 07:38:38 spaceman systemd[1]: Starting MariaDB database server... -- Subject: Unit mariadb.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mariadb.service has begun starting up. Oct 14 07:38:38 spaceman sysctl[10089]: sysctl: permission denied on key 'vm.drop_caches' Oct 14 07:38:38 spaceman systemd[1]: mariadb.service: control process exited, code=exited status=255 Oct 14 07:38:38 spaceman systemd[1]: Failed to start MariaDB database server.
* MDEV-427/MDEV-5713 Add systemd script with notify functionalitySergey Vojtovich2015-10-121-13/+13
| | | | After review/QA fixes.
* MDEV-427/MDEV-5713 Add systemd script with notify functionalityDaniel Black2015-10-121-0/+133
View Lorry Controller Status