MySQL Connect Error in Vicidial

Because my UPS failed, my Vicidial Server did not get to shutdown properly when the power flickered for a second. This caused the MySQL error and I can't get past anything after clicking "Agent" or "Administration".

Here's what I did in the Linux Command Line:

mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak
service mysqld start

After that, it was okay. Keep this piece of code close to you, if you expect power outages to happen... or if you're too lazy to use "sudo poweroff". See reason for this code at the source from stackoverflow.com

Update:

• Make sure when you use MV to rename the file, you don't use a name that already exists. For the 2nd time this happened, I renamed it to mysql1.sock.bak
• I also had another incident where the mysql.sock did not exist. Turns out, my root was already 100% capacity. View post here: http://simplevicidial.blogspot.com/2016/04/no-mysqlsock-because-root-partition-is.html

Source: http://stackoverflow.com/questions/20407292/centos-another-mysql-daemon-already-running-with-the-same-unix-socket