SUGGESTIONS MySQL Error: FreePBX Won't Start

[wa4zlw]

I manage our synagogues PIAF and been getting emails from vitellity that calls not terminating. I assumed this was normal registration issue and it would have failed over to the voip.ms trunk.

Nope. Asterisk down again!

FATAL ERROR

DB Error: connect failed

Trace Back

/var/www/html/admin/libraries/db_connect.php:71 die_freepbx()
[0]: DB Error: connect failed

/var/www/html/admin/bootstrap.php:85 require_once()
[0]: /var/www/html/admin/libraries/db_connect.php

/etc/freepbx.conf:9 require_once()
[0]: /var/www/html/admin/bootstrap.php

/var/www/html/admin/config.php:99 include_once()
[0]: /etc/freepbx.conf

┌────────────────────────SYSTEM INFORMATION───────────────────────────┐
│ Asterisk = OFFLINE | Dahdi = ONLINE | MySQL = OFFLINE │
│ SSH = ONLINE | Apache = ONLINE | Iptables = ONLINE │
│ Fail2ban = ONLINE | Internet = ONLINE | Ip6Tables = ONLINE │
│ Disk Free = ADEQUATE| Mem Free = ADEQUATE| NTPD = ONLINE │
│ Postfix = ONLINE | Samba = ONLINE | Webmin = ONLINE │
│ Ethernet0 = ONLINE | Ethernet1 = N/A | Wlan0 = N/A │
│ │
│ PIAF Installed Version = 2.0.6.4 under *HARDWARE* │
│ FreePBX Version = 2.11.0.37 │
│ Running Asterisk Version = UNKNOWN │
│ Asterisk Source Version = 11.6.0 │
│ Dahdi Source Version = 2.7.0.1 │
│ Libpri Source Version = 1.4.14 │
│ IP Address = 10.196.4.10 on eth0 │
│ Operating System = CentOS release 6.4 (Final) │
│ Kernel Version = 2.6.32-358.23.2.el6.i686 - 32 Bit │
│ Incredible Version = 11.7 │
└─────────────────────────────────────────────────────────────────────┘

I reported this months ago and forgot what was done to clear this and I requested it be added to the distro and never heard anything back. I'm assuming they had a power failure or something that tripped the UPS.

I'm at work during lunch looking at this and need to get it up before Shaboos sets in.

THanks leon

 

[wa4zlw]

amportal restart fails as such:

root@pbx:~ $ amportal restart

Fetching FreePBX settings with gen_amp_conf.php..
/usr/local/sbin/amportal: line 49: [FATAL]: command not found

/var/lib/asterisk/bin/freepbx_engine: line 98: [FATAL]: command not found
**** WARNING: ERROR IN CONFIGURATION ****
astrundir in '/etc/asterisk' is set to but the directory
does not exists. Attempting to create it with: 'mkdir -p '

mkdir: missing operand
Try `mkdir --help' for more information.
**** ERROR: COULD NOT CREATE ****
Attempt to execute 'mkdir -p ' failed with an exit code of 1
You must create this directory and the try again.
WARNING: Always run Incredible PBX behind a secure hardware-based firewall.
root@pbx:~ $

 

[rossiv]

Check and see if the mysql server is started.
On CentOS, I think it's 'service mysqld status' or 'service mysql status'

 

[tm1000]

Look at your own profile page I was able to find the original issue with the fix: http://pbxinaflash.com/community/index.php?threads/fix-mysql-db-error.14750/#post-94733

and no it has not been added to any piaf installs. It is in the FreePBX distro. Has been there for months.

 

[wa4zlw]

thanks folks...if freepbx fixed it then why when stuff comes up it doesnt run this to fix it?
We should, IMHO, do this. seems to happen everytime a power failure hits of course

 

[tm1000]

The FreePBX Distro only. This is a distro level feature. I have said that several times now. It is up to your distro to add this (FreePBX itself can't)

 

[wardmundy]

The fix has been posted since May. It takes about 3 seconds to cut and paste the lines to your server.

wa4zlw: You participated in that thread so why are you still having the same problem if you fixed it??

 

[wa4zlw]

yes I have and tm1000 says above the distro needs to add it. I have not done so since my original post. which if I were to "fix it" then anytime a change is done or I change colors or pull a new distro I have to reinvent the wheel. if the distro has it I or others dont have to worry about it.

Leon

 

[wardmundy]

Leon (aka wa4zlw):
We plan to add the patch as time permits. In the past 8 years, we've seen this issue raised about three times. Two of those were from you.

So... in the scheme of things, we prioritize resources. We don't do this for a living like tm1000. We do it for fun. Unless you want to fund the next build, use the patch. Otherwise, wait or switch distros if you believe the grass is greener elsewhere. But don't keep raising the same issue. It wastes everyone's time. Thanks.

 

[wa4zlw]

thanks ward...i appreciate all that and understand.

 

[james]

To assist the user base who may be having this issue, I would like to contribute to the inclusion of the aforementioned fix. I encourage others to donate as well so we can get these fixes included so people can stay on PBX in a flash. Simply click the donate link at the top of the page. Thanks wardmundy for all of your hard work.

 

[tm1000]

We are just trying to be helpful to your community, we are not trying to push our own product but the fact remains that it is fixed in our own distro in an init.d script, I've pretty much written out what the init.d script should look like. I never had to reply in this thread with the fix or the other thread, I could have just let everyone assume (incorrectly) that Leon's mysql database was crashed/broken beyond repair and that he should/needed to do a full reinstall, is that fair to let that happen? If I comment on the fix that we figured out and also say that it's in the FreePBX distro that is not fair? So the fix is fair and welcome but the comment about our distro is not....... Take it or leave it.

When people ask about PIAF on *our* forums and even in IRC (in which PIAF conversation and questions come up more than you'd think) we are pretty open and nice about it. Users can choose what they want, they should make up their own minds. We shouldn't have to feel ashamed for talking about our products here... or should we?

Furthermore, James and I both have worked on FreePBX for several years in our free time without getting paid. I wrote Endpoint Manager for this community (PIAF) in my free time, completely unpaid. I managed Superfecta completely unpaid (with Lorne). James wrote the freepbx hello world module, the original teletorture module and others completely unpaid. So I fail to see how the argument of "we get paid for this" applies to anything. Are we not welcome here because we turned a hobby into a job? Isn't that the point of all this?

Just trying to provide for the community that I love/respect. That is all. I hope for Leon's sake that he writes this down, because if he asks about it again I'm sure we will all travel down this same rat-hole again and I'd really hate to see that.

Instant Coffee Fix:

service mysqld stop
rm -Rf /var/lib/mysql/mysql.sock
service mysqld start

Long Term Fix:

echo "service mysqld stop" >> /etc/rc.d/rc.local
echo "rm -Rf /var/lib/mysql/mysql.sock" >> /etc/rc.d/rc.local
echo "service mysqld start" >> /etc/rc.d/rc.local

 

[wardmundy]

Thanks, tm1000. We provided a similar fix last May in the first thread in which this was raised by the same wa4zlw.

We all appreciate everything you and james do/have done for both the FreePBX and PIAF projects. Just wish some of the snarky comments could be avoided. Tends to poison a good conversation.

 

[ostridge]

Instant Coffee Fix:

service mysqld stop
rm -Rf /var/lib/mysql/mysql.sock
service mysqld start

Long Term Fix:

echo "service mysqld stop" >> /etc/rc.d/rc.local
echo "rm -Rf /var/lib/mysql/mysql.sock" >> /etc/rc.d/rc.local
echo "service mysqld start" >> /etc/rc.d/rc.local

Hi my Coffee turned sour when I used your fix on my Rpi2 Raspbian (wheezy) as signature below

root@pi2:/var/run/mysqld# service mysqld stop
mysqld: unrecognized service

So I amended your script to read service mysql stop, which I think worked (except that when I replicated the stop, there is no mysql.sock to rm)

#!/bin/bash

service mysql stop
rm -Rf /var/lib/mysql/mysql.sock
service mysql start

That would mean that my Long Term Fix (LTF) would/should read:-

echo "service mysql stop" >> /etc/rc.d/rc.local
echo "rm -Rf /var/lib/mysql/mysql.sock" >> /etc/rc.d/rc.local
echo "service mysql start" >> /etc/rc.d/rc.local

I have not tested that LTF. I hope I got that right?
No-Joy its not there - try echo "rm -Rf /run/mysql/mysql.sock"

root@pi2:/etc# ls -Al /var/lib/mysql/mysql.sock
ls: cannot access /var/lib/mysql/mysql.sock: No such file or directory

root@pi2:/etc# ls -Al  /var/run/mysqld/mysqld.sock
srwxrwxrwx 1 mysql mysql 0 Nov 10 03:43 /var/run/mysqld/mysqld.sock

added code below to /etc/rc.local Trying with 'rm -Rf /run/mysqld/mysql.sock'.

# the folowing is to cleanup 'mysql.sock' if exist when mysql stopped
#exit 0
service mysql stop
rm -Rf  /run/mysqld/mysql.sock  # or is it ?  rm -Rf /var/run/mysqld/mysql.sock
service mysql start

exit 0

 

[wardmundy]

@ostridge: You've dredged up a thread that's over 2 years old. The syntax for Debian/Ubuntu/Raspbian is different than what's used on the RedHat/CentOS/SL platforms. None of those implementations even existed when this thread was created.

Also be sure your entries precede the exit 0 line in rc.local.

 

[ostridge]

@ostridge: You've dredged up a thread that's over 2 years old. The syntax for Debian/Ubuntu/Raspbian is different than what's used on the RedHat/CentOS/SL platforms. None of those implementations even existed when this thread was created.

Also be sure your entries precede the exit 0 line in rc.local.

Thanks for the pointer I had spotted the EXIT 0 and wasnt sure where it wanted to be.
Shouldn't that script have magically found its way into the updates/distros?

I'm getting a delay with incoming/7777/internal calls due to mysql gone away.
By the time call rings and gets answered caller gone away.

rc.local not at /etc/rc.d/rc.local
in Wheezy its at /etc/rc.local and there is not an /etc/rc.d directory
Regards

 

[wardmundy]

/etc/rc.local should be symlinked to /etc/rc.d/rc.local