Unable to load config after module update

Hi Everyone -

I’m having an issue updating FreePBX.

The module being updated is sysadmin, from 2.10.0.51 to 2.10.0.52.

After processing the update, I get the following error:

Reload failed because retrieve_conf encountered an error: 1

exit: 1
found language dir fr for directory, not installed on system, skipping
[FATAL] Unable to load configuration due to extension count being less than available

There is no detailed info on the main screen. Any ideas what could be causing this?

I have the FreePBX distro and my current version is: FreePBX 2.10.1.5

Saw that System Admin 2.10.0.53 was available so I updated to it.

The Apply Config button appeared, but I get this error when I try to apply the config:
exit: 1found language dir fr for directory, not installed on system, skipping[FATAL] Unable to load configuration due to extension count being lesss than available
How can I fix this or revert System Admin?
Thanks for your help,
Bob

Likewise, I’m having the same problem. Any fix for this yet?

I am getting the same issue. You can remove it and the error goes away, but if you reload it you get the error again. I don’t see how you load the old version back

I would vote this is a bug in this module. I don’t see an option to go back. I am glad I only loaded this on my non production box for the moment.

But on my production box. I have no idea which module is failing.

On box I was about to demo today.

Uninstalling and reinstalling doesn’t work.

In fact uninstalling won’t even let me apply and reload.

The same problem her, looks like a bug, anyway to downgrade or disable it

uninstalling sys admin fixed the problem

After: System Admin 2.10.0.53 will be disabled

all is fine.

This is a commercial module right? I don’t need it for the basic install as far as I know.

Did you reboot/restart asterisk after you uninstalled? I uninstalled twice and it didn’t fix it for me.

The bug was fixed and pushed in the -55 of sysadmin. Sorry about that.

  1. Uninstall ‘System Admin’ module
  2. Apply Config

Encountered the same problem after running upgrade-2.210.62-5.sh.

Remember to always test updates before deploying.
We do.

.55 works without any further issues.