Major bug found

[Harlee Oseana]

Hi, I found a bug in the last update (version 4.2.4 / switch 1.6.19). The Default Settings page table, the outbound routes table and other tables in the system are missing rows. See the image attachment, notice the rules and conditions below tables is missing. Sometimes it appears partially as well. Anybody else encounter this?



In Firefox they sometimes show only a few of the rows, but sometimes they reappear. In internet explorer I get an error. This seems to be a bug in the php. I am running the application on CentOS (up-to-date).

 

[DigitalDaz]

Please don't cross post. Also, anything in Centos cannot really be described as 'major bug' as its not the recommended OS for FusionPBX and is not tested by the devs.

 

[Harlee Oseana]

Hi,

Sorry about the cross post, I posted the first one in the wrong category and forgot to remove this post.

I understand. So let's just call it a regular bug in CentOS. Any ideas how or where to fix this?

 

[DigitalDaz]

Sorry, no, this will be your problem with centos, its used by very few people and most seem to struggle with it. You may find someone on here using it.

 

[Harlee Oseana]

Are there any instructions anywhere I can find to revert back to a previous version?

Or if you can at least point me in the right direction to which files to look at I may be able to fix it myself and post it to help anybody facing this same problem in the future.

 

[Harlee Oseana]

Hope this helps anyone else with this problem. Fixed this issue by re-installing FusionPBX.

The issue started after updating CentOS and upgrading FusionPBX.

I thought this may be a FusionPBX issue, but it may only be a CentOS upgrade issue

Anyways, to fix the issue I did the following:

First I made a full system backup (always a good idea when working with production systems)
Then I made a backup of the database, and made a note of the current db password in the config.php file.
Move the previously copied source files to a backup folder to make sure a new source folder is created using the wget script.
Then I reinstalled using the install script for CentOS (ignore warnings of existing files/folders and database access requests - if you allow it access to the database it may reset your data and configurations).
Reboot the server
Change the db password in the config.php to the old db password
You should now have access to the fix application
Just in case I also opened and re-saved some data such as some extensions and SIP profiles and reloaded the ACL and XML to make sure any config files which were overridden have been set back to the my previous configuration

Voila !