neither mysql_safe or mysql_wait_ready exist but the service file is linking them.
also i would like to note that After=network.target should be removed since mysql can be used locally, it doesnt require the network to operate and booting before ore after network serving should make no difference?
(In reply to C.J. Wijtmans from comment #1) > also i would like to note that After=network.target should be removed since > mysql can be used locally, it doesnt require the network to operate and > booting before ore after network serving should make no difference? I would like to note that this should not be removed because of the potential to hang the server. MySQL expects every interface that it is configured to be available on startup. If you bind it to 192.168.0.1 and that interface is not up, it will hang trying to bind to it. Now this may clear up since systemd is in parallel, but I've never tested if the binding clears if the network is started later.
hmm that is true i guess? i will edit the service file to work today.
well. what happens if you have no network service will mysql hang/fail?
okay, the binaries actually exist. Unit mysqld.service has begun starting up. Nov 08 17:56:24 HTPC systemd[1]: mysqld.service start request repeated too quick Nov 08 17:56:24 HTPC systemd[1]: Failed to start MySQL database server. -- Subject: Unit mysqld.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02c -- -- Unit mysqld.service has failed. -- -- The result is failed. Nov 08 17:56:24 HTPC systemd[1]: Unit mysqld.service entered failed state.
yeah just ignore my stupidity. /var/log/mysql did not exist then i created it and it had the wrong permissions.
