I had installed FreePBX on an eMachines (AMD processor) desktop and everything was working well. I went away for business for a few days and when I returned, this is the message that is showing:
FATAL ERROR
DB Error: connect failed
Trace Back
/var/www/html/admin/libraries/db_connect.php:63 die_freepbx()
[0]: DB Error: connect failed
Could you please help solve my pblm? I got the same fatal error and as a beginner in freepbx, it is not easy to find it by myself. Thanks for your help.
FATAL ERROR
DB Error: connect failed
Trace Back
/var/www/html/admin/libraries/db_connect.php:63 die_freepbx()
[0]: DB Error: connect failed
Had the same issue and a newbie (so may not be right or a good answer)… but found this on another website and it helped me
service mysqld stop
mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak
service mysqld start
No. It is not intentional. Maybe it is related to my VM Vitualbox on which i installed the asterisknow ?
Unless Asterisknow, nothins else is installed on it :(.
thanks for yur help.
I just dealt with this error after my virtual machine shut down ungracefully. mariniar’s suggestion to rename the mysqld.sock file worked for me. Login to the virtual machine’s console as the root user and execute these three commands exactly:
service mysqld stop
mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak
service mysqld start
i have the same problem, and the solution is the same, but why happens?
i have the freepbx on a esxi enviroment, and when the server lost the power, the pbx not start automatycally, i have to connect via ssh and put these commands.
everytime that the server lost the power, not autostart, i tested 3 or 4 times and allways fail
there is a solution for this problem?
thanks for all
When MySQL, the PBX’s database server, crashes unexpectedly, as with a power outage to the computer it’s running on, it leaves this mysql.sock file behind. The file is created as a normal and necessary part of MySQL’s operation, it’s called a “socket” (see http://en.wikipedia.org/wiki/Unix_file_types#Socket for details). If MySQL is stopped gracefully, this file is deleted automatically.
As I replied to markbhai, if you expect your system to operate properly, power protection is necessary (along with using the server’s power button appropriately).
If this is truly a production system, then it should be on conditioned power, at least a battery backup with suitable runtime reserves. In my case, I’m running a system at home and do have a battery backup with about 30 minutes of reserve, enough for the most common outages. My recent outage lasted four hours, though, and I haven’t configured my systems to do an auto-shutdown when the battery unit reaches a predetermined reserve level (which should be configured for a “production” system).
If proper power protection, as well as protecting the power switch, is in place, your proposed script should be unnecessary. If you aren’t able to provide that, then your script would be an acceptable workaround (personally, I’d test for the existence of the file before the rename command; search for “bash file test operators” in your favorite search engine for details).
!!