Elastix 4 Database Driver Error for Endpoint Configuration

scottalanmiller

Elastix 4 is pretty flaky, just as an FYI. If you are building a new PBX now, I would seriously recommend looking into switching to FreePBX instead. It is much more up to date and supported at this point. Elastix pretty much died when they failed to get Elastix 3 out the door and Elastix 2 support totally failed. Elastix 4 is their attempt at a come back and right now, it's not being well maintained and doesn't work reliably. It's got some nice stuff to it and I hope that they figure things out and get it working, but it is not looking good at this point.

FreePBX stepped up and took what was the Elastix marketshare and support community away. Pretty much everyone that was on Elastix has moved to it and it works great.

scottalanmiller

Wonderful, if you Google this error, we are already the top hit for Elastix 4! Good for SEO, bad for finding the answer.

scottalanmiller

Okay @lucale I'm grasping a bit here as I don't have a test system to work on, but...

Start by trying this...

yum install sqlite

And let me know the output. My guess is that it is trying to use SQlite and that that is not installed.

lucale

Thanks for your answer!

let me tell you that after install about 3 or 4 times elastix using your instructions with some little modifications always endpoint has problems with the database, other times the problem was the username.

Now, I change the username to connect to the database from asteriskuser to root in the file paloSantoEndpoints.class.php and get other error ERR: failed to get database credentials

yum install sqlite
Failed to set locale, defaulting to C
Complementos cargados:fastestmirror
Loading mirror speeds from cached hostfile

base: mirror.gtdinternet.com
commercial-addons: elastix.adaptixnetworks.com
elastix-base: elastix.adaptixnetworks.com
elastix-extras: elastix.adaptixnetworks.com
elastix-updates: elastix.adaptixnetworks.com
epel: epel.gtdinternet.com
extras: mirror.gtdinternet.com
updates: mirror.gtdinternet.com
El paquete sqlite-3.7.17-8.el7.x86_64 ya se encuentra instalado con su versi?n m?s reciente
Nada para hacer

scottalanmiller

@lucale there is every possibility that the Endpoint Configuration simply does not work in Elastix 4. That's not a component that we often use and we migrated everything off of Elastix 4 because of its stability and support problems. But at this point, basically no one uses Elastix 4 so there just might not be people reporting issues with it

lucale

Problem SOLVED

To fix this problem it's necessary add the user and password for the database in the file /etc/amportal.conf

AMPDBUSER=asteriskuser
AMPDBPASS=yourultrasecretpassword

After that the endpoint will be fully functionally

scottalanmiller

@lucale said in Elastix 4 Database Driver Error for Endpoint Configuration:

Problem SOLVED

To fix this problem it's necessary add the user and password for the database in the file /etc/amportal.conf

AMPDBUSER=asteriskuser
AMPDBPASS=yourultrasecretpassword

After that the endpoint will be fully functionally

So AMP was not working at all then? How did we get focused on the Endpoint Configuration manager? None of the interface should have been working if this was not done.

I believe that the step to make this work is in the instructions as it is a known problem with Elastix. I thought that the fix for the main AMP database was built in.

scottalanmiller

Had you done this step after the initial build? Did you get the on console screen to set the AMP password?

systemctl enable mariadb.service
systemctl enable httpd.server
reboot

lucale

@scottalanmiller Of course, I did.

scottalanmiller

@lucale said in Elastix 4 Database Driver Error for Endpoint Configuration:

@scottalanmiller Of course, I did.

And did the correct prompts come up, but just fail to set the database correctly?

lucale

@scottalanmiller Exactly, until now i have only problems with that database.

scottalanmiller

@lucale said in Elastix 4 Database Driver Error for Endpoint Configuration:

@scottalanmiller Exactly, until now i have only problems with that database.

Elastix has been having huge problems with their database stuff not being reliable in Elastix 4 across the board. But at least with the old builds, it was working after some standard modifications.

But I can't state enough that I would not keep using Elastix 4. They are just not able to support the product any longer. It's just too risky to use in production today.