Elastix 4 Install Errors with SQLite Unable to Update Admin Password
-
Because it's beta software?
Why is this still at beta 1 after almost 7 months? Their lack of progress is concerning...
-
I would never go back to Elastix at this point. They abandoned it (the FreePBX based version) once. Figured out it was a mistake. Then used a kickstarter to get funding to speed development of porting it to CentOS 7 and they have not done dick.
-
@JaredBusch said:
I would never go back to Elastix at this point. They abandoned it (the FreePBX based version) once. Figured out it was a mistake. Then used a kickstarter to get funding to speed development of porting it to CentOS 7 and they have not done dick.
Right now I definitely agree. We put in a bit of time this week working on both Elastix MT and Elastix 4 builds and both are broken and worthless. As you said, seven months of no development. It looks suspiciously like Elastix has given up and gone the OpenFiler route of keeping the website up but the shop is empty. I have a feeling that Elastix is gone now.
They made the mistake of doing really dumb things (Elastix 3/MT) and failing at it at the exact same time that Schmooze took FreePBX to its own distro and fixed the majority of Elastix' problems. Had Elastix faltered without the FreePBX distro there to steal all of their userbase things might have been different. But the timing left them completely exposed.
-
FreePBX is up and working on CentOS 7 already, by the way. They are staying pretty much on the leading edge.
-
I just set up the FreePBX distro at home and it couldn't have been easier.
-
@johnhooks said:
I just set up the FreePBX distro at home and it couldn't have been easier.
The distro is still CentOS6.5 I believe. To get 7 you have to install 7 first then use the scripted install.
-
@JaredBusch said:
@johnhooks said:
I just set up the FreePBX distro at home and it couldn't have been easier.
The distro is still CentOS6.5 I believe. To get 7 you have to install 7 first then use the scripted install.
Oh OK. Guess I'm in for some more work. Have you used Google voice with it? Outbound works great, inbound is spotty.
-
@johnhooks said:
Have you used Google voice with it? Outbound works great, inbound is spotty.
I've used GoogleVoice with PBX in a Flash for years. Works flawlessly. Should be no reason that it works any differently in FreePBX.
-
@JaredBusch said:
@johnhooks said:
Have you used Google voice with it? Outbound works great, inbound is spotty.
I've used GoogleVoice with PBX in a Flash for years. Works flawlessly. Should be no reason that it works any differently in FreePBX.
Are you using the motif module? I used simonics and they create a sip trunk for you. The distribution doesn't have the motif module in it from what I could see.
-
@johnhooks said:
Are you using the motif module? I used simonics and they create a sip trunk for you. The distribution doesn't have the motif module in it from what I could see.
I am not sure what integration PBX in a Flash uses, they present it as a trunk once setup. Been a long time since I set it up.
-
@JaredBusch said:
@johnhooks said:
Are you using the motif module? I used simonics and they create a sip trunk for you. The distribution doesn't have the motif module in it from what I could see.
I am not sure what integration PBX in a Flash uses, they present it as a trunk once setup. Been a long time since I set it up.
Ok thanks!
-
Looping back, exact same issue remains on the production Elastix 4 release.
-
Here is the full error text after the install:
No Elastix CallCenter database found. No A2Billing database found. No VTigerCRM database found. Updating FreePBX database password: mysql... files... updated Updating FreePBX admin password: mysql... files... updated Updating FreePBX ARI password: mysql... files... updated Updating Flash Operator Panel password: mysql... files... updated Updating Asterisk Manager Interface password: mysql... files... updated Updating Elastix admin password: sqlite... FATAL: unable to update Elastix admin password: SQLSTATE[HY000]: General error: 1 no such table: acl_user -
Got this fixed. Issue is all connected. It has to do with how the dependencies are picked up from the repo.
