[mccabec123]

Hey guys, I'm having an issue starting my MySQL daemon after rebooting my dedi, I have no clue why it's suddenly doing this, I'm running PHPMyAdmin from the server and also issuing certain commands through the CLI for MySQL, but after rebooting I'm getting this error everytime I try to start the instance of the daemon:

[root@ks23085 ~]# service mysqld start
Redirecting to /bin/systemctl  start mysqld.service
[root@ks23085 ~]# systemctl mysqld start
Unknown operation mysqld
[root@ks23085 ~]# systemctl start mysqld
Failed to issue method call: Unit name mysqld is not valid.
[root@ks23085 ~]# systemctl start mysqld.service
[root@ks23085 ~]# mysql
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/path/to/mysql.sock' (2)

It's completely bizarre as it was working perfectly before I rebooted it, I didn't update it or change the install, the only thing that I did do was install postfix, but I don't see why that would cause any issues with MySQL :S

I really need a hand on this one, I've tried several solutions from google with no results whatsoever. Thanks in advance guys.

This post has been edited by mccabec123: 28 July 2012 - 09:02 AM

[Lemur]

Try:

whereis mysql
whereis mysql-server

---

Look up init.d and how to add daemons to it, and that should get you up and on your way. It sounds like the changes didn't persist through reboot to that, so a flag would have to be added for mysqld.

[no2pencil]

Lemur, on 28 July 2012 - 07:25 PM, said:

Try:

whereis mysql
whereis mysql-server

I've always used
which mysqld

You can also validate that mysql is or isn't running by checking for the process id :

ps aux | grep -i mysql