Freepbx config issue after upgrading AsteriskNow

Joachim's picture
Posted September 7th, 2010 by Joachim (tadpole)

Hello everyone,

We run AsteriskNOW 1.7.1, and this afternoon we did a "yum update" to upgrade the system. Afterwards, we went to freepbx and did a module update first as the upgrade messages told us. We then tried to reload the configuration but that does not work.

We now run:
Asterisk 1.6.2.11
FreePBX 2.8.0.2

The module admin page tells us:
FreePBX Framework 2.8.0.2 FreePBX Disabled; Pending upgrade to 2.7.0.0
Seems like an odd message? Or does it just say our upgrade is still in progress and not finished as we haven't reloaded the cfg yet?

Now onto the main problem: when we apply configuration, this process ends in the following message:
PHP Fatal error: Call to undefined method extensions::addSectionComment() in /var/www/html/admin/modules/core/functions.inc.php on line 1725

This crashes the reload.


__________________


‹ A2billing 1.7 & Freepbx Trunk Asterisk Server Error ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

I've got the same issue...

hootjr29's picture
On September 7th, 2010 hootjr29 (tadpole) said:

I've got the same issue... any updates before I start diggin?


That is the danger of

mickecarlsson's picture
On September 8th, 2010 mickecarlsson (Developer) said:

That is the danger of running yum, it downgraded your FreePBX to 2.7. You need to reinstall FreePBX 2.8


__________________

Mikael Carlsson
(I am off-line, tinkering with my Chevy and my radios, don't know when I will be back)


The best way I found that

netadvanced's picture
On October 31st, 2010 netadvanced (tadpole) said:

The best way I found that worked for me is by excluding the freepbx package:
yum --exclude=freepbx update

I still check most modules manually and make sure the upgrade is not going to "retrograde" anything.

Thanks to the VM world, I now save a snapshot before any update. to be on the safe side and delete it a few days/weeks later.


I resolved it like this

billetkontoret's picture
On November 10th, 2010 billetkontoret (tadpole) said:

I had the same problem. I resolved by restoring a backup made via the FreePBX backup-module. It worked fine.