Today after update some of us notice this: |# systemctl start mariadb.service |
|Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. # systemctl status mariadb.service ● mariadb.service - 10.1 database server Loaded: loaded (/lib/systemd/system/mariadb.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2017-04-22 20:52:17 CDT; 4s ago Process: 8098 ExecStopPost=/mysql-wait-stop (code=exited, status=203/EXEC) Process: 8097 ExecStartPre=/mysql-check-socket (code=exited, status=203/EXEC) Apr 22 20:52:17 ben79-pc systemd[8097]: mariadb.service: Failed at step EXEC spawning /mysql-check-socket: No such file or Apr 22 20:52:17 ben79-pc systemd[8098]: mariadb.service: Failed at step EXEC spawning /mysql-wait-stop: No such file or di Apr 22 20:52:17 ben79-pc systemd[1]: Failed to start 10.1 database server. |||
Is it something started on demand by something that uses it or is this a bug?
-- Ben Bullard ben79 -------------------- OpenMandriva-QA Team
_______________________________________________ OM-Cooker mailing list OM-Cooker@ml.openmandriva.org http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org
