Ok I was hoping you weren’t going to say that it was just us.
I did find it.
[root@localhost ~]# locate fwconsole
/usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole
/usr/src/freepbx-13.0.64/amp_conf/htdocs/admin/modules/framework/amp_conf/bin/fwconsole
[root@localhost ~]#
Great!
Now run these commands
/usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole ma download framework
/usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole ma install framework
Then run
/var/lib/asterisk/bin/freepbx_engine[root@localhost ~]# /usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole ma download framework
PHP Fatal error: Class ‘FreePBX\Console\Application\FWApplication’ not found in /usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole on line 78
[root@localhost ~]# /usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole ma install framework
PHP Fatal error: Class ‘FreePBX\Console\Application\FWApplication’ not found in /usr/src/freepbx-13.0.64/amp_conf/bin/fwconsole on line 78
[root@localhost ~]#
Didn’t run the last command, figure it wouldn’t work.
Ok so now I am confused. You said this was an upgrade. But with “/usr/src/” having freepbx-13.0.64 it doesn’t seem like an upgrade at all this seems like a fairly recent distro install.
Actually this seems like a system that was installed with 13.0.64 but then someone restored a backup on to it with a far older version. This is FreePBX 13?
I didn’t say it was an upgrade. This particular system has been installed for many months. We have an image that we initially create the system from, then we run the Sangoma script to install our skin , then we install Sys admin Pro and run the upgrade scripts. This system is 6.12 never had 13 on it.
I just looked at sys admin pro and it is set to check for upgrades on a daily basis.
Is this running FreePBX 12 or 13. I do not care about Distro verison.
It seems the system was installed with FreePBX 13 then reverted back to FreePBX 12. If that is the case then you will need to bring it up with your tech because it’s not going to work.
I say this because the system is acting like FreePBX 12, but has remnants from FreePBX 13 (the installer in /usr/src for version 13 and the motd, again only version 13)
Since you didn’t answer my question I am only guessing. Please tell me the FreePBX version (framework)
When I run
cat /etc/schmooze/pbx-version I get 6.12.65.32
Going to Module Admin the Freepbx Framework version is 12.0.76.2
We have never installed or sent out 13
Looking at the update log in sys Admin Pro there are two updates in progress and Locked. We checked two systems and they are both locked
Usr/src says otherwise. This was originally a 13 system. The upgrade scripts never change usr/src so whatever freepbx is in there is the starting version.
I find myself in the same situation. A clean distro load on a machine with Freebx 12 and 6.12.65, never upgraded to 13, Sysadmin Pro being used, stuck on an upgrade. It’s almost as if the automatic updater went out and grabbed 10.13.66 and tried to do auto upgrade.
Update currently in progress! Please wait until complete.
2016-01-20 03:01:29: (6.12.65-32) Starting stage 5
2016-01-20 03:01:29: (6.12.65-32) Stage 5 complete
2016-01-20 03:01:29: (6.12.65-32) Starting stage 6
2016-01-20 03:01:29: (6.12.65-32) Stage 6 complete
2016-01-20 03:01:29: (6.12.65-32) Upgrade script complete
2016-01-20 03:01:29: () Upgrade process successfully completed!
2016-01-27 03:00:04: () Update sequence initialized
2016-01-27 03:00:04: () Upgrade process successfully completed!
2016-02-03 03:00:12: () Update sequence initialized
2016-02-03 03:00:12: () Upgrade process successfully completed!
2016-02-10 03:00:13: () Update sequence initialized
2016-02-10 03:00:13: () Upgrade process successfully completed!
2016-02-17 03:00:13: () Update sequence initialized
2016-02-17 03:00:13: () Requesting updates
2016-02-17 03:00:13: () Processing update
2016-02-17 03:00:13: (10.13.66-1) Starting stage 1
2016-02-17 03:01:42: (10.13.66-1) Stage 1 complete
2016-02-17 03:01:43: (10.13.66-1) Starting stage 2
2016-02-17 03:10:48: (10.13.66-1) Stage 2 complete
2016-02-17 03:10:48: (10.13.66-1) Starting stage 3
Even if sysadmin downloaded the upgrade scripts for 13 it wouldn’t install it in usr/src. Thats not how the upgrader works. To upgrade to 13 a single database value is changed and the modules upgrade. This is why it’s easy to see what the starting version of freepbx is by just looking in usr/src
This particular system was installed 6 months ago, we have NEVER deployed nor installed a 13 system. I realize the files are there, but they aren’t there because we installed it. I see that fcd_3 is having the same issue. At least the update issue
After talking with Tony the issue is that you were half way through a distro 12 to 13 upgrade. Sysadmin does this now. Or well it did. The upgrade had an issue so we removed it. So yoy are both halfway through.
To fix it you’ll need to upgrade to version 13 using the upgrade scripts from the wiki.
So the Sys admin was taking us to 13 and choked. Will unlocking the updater do the trick?
/usr/sbin/sysadmin_update_system --unlock
FYI-- I used the WIKi instructions to upgrade a version 12 (new setup) I was going to replace a system this weekend with it. Now when I log into it, it says it cannot connect to Asteisk. So Now I am not so sure I want to take this step on a system that is in use.
‘Fwconsole start’ should get the asterisk started.
That went through many thngs now I have a critical error found. retrieve_conf failed
Fwconsole chown should have been completed by fwconsole start but you can run it on it’s own. Fwconsole reload does the same thing as the ‘apply’ button. I find the cli much more convenient.