FreePBX distro 22.214.171.124.
[2018-07-29 08:24:56] WARNING db.c: Error executing SQL (COMMIT): disk I/O error
[2018-07-29 08:24:56] WARNING db.c: Error executing SQL (ROLLBACK): cannot rollback - no transaction is active
Immediately after that the call drops.
The system is on a RAID server, and I checked everything I could think of. Raid is green. The host server checks out, disk system says no errors. I can’t find anything in the host hardware logs. I also ran checkdb on the MariaDB databases. No errors found.
I would like to do something like fsck on the partition, but I have not been able to figure out what to do, because FreePBX installs a LVM volume and I’m not familiar with the commands.
OK, let me ask this a different way.
Is it possible to configure or start Asterisk so that it uses RAM for SQL, instead of reading it from disk? I have 100 gigs of RAM in that server.
We are dropping multiple calls a day due to “disk I/O error”, this is really intolerable. And it worked for over 12 years before with no problem. All the way back to early Trixbox. Again, there is no problem on the disks.
OK, here’s where I’m at now.
I built an entirely new FreePBX 14 on a new VM.
Then, I did a full backup from my production system and restored it to the new server.
Then I shut everything down. I moved the newly created disk over to the production server and started it up. I thought that would be the end of my problems.
To my surprise, I have a ton of errors now.
One of the main problems is that the new system refuses to use my Letsencrypt certificate from the previous installation. I even deleted the certificate and completely regenerated it. Nope. FreePBX insists on using a local temporary cert that is not trusted. Every page is full of errors because of this.
Second, every time I try to configure anything on the new installation, I get a big red banner on the top of the screen that says UNDEFINED. And I cannot click on “Apply Config”. I just go through a cycle of Apply Config and UNDEFINED errors.
I think i’m down to this one issue now.
FreePBX is not using the correct certificate for TLS.
I’ve tried deleting the certificate and regenerating on from Letsencrypt. It made no difference. FreePBX still serves an invalid certificate.
If I go to /etc/asterisk/keys and run openssl x509 -in mycert.pem -text, it is perfectly valid. The problem is that FreePBX is not using it. It keeps serving an invalid temp certificate from when it the system was in testing.