Post a Reply
3417 views

2.28 admin changes not implemented until fop2 restart

  1. 10 years ago

    bongfrog

    16 Sep 2014

    New 2.28 install, PiaF w/ freepbx 2.11 , noticed a few of the changes to the admin page but now have traced the main issue.
    When a change is made in the admin page , user password for example , the change is not 'implemented' until the fop2 service is restarted. I noticed that the system had the manager version 1.0 , I upgraded to the latest tar ball , now the manager is showing 1.0.1 but still have the same symptom. I have enabled fop2 debug and do not see any errors that jump out at me right away.

    any suggestions?

    Thanks,
    Mike

  2. admin

    16 Sep 2014 Administrator
    Edited 10 years ago by admin

    Hi,

    I have noticed that Asterisk 11.10.0 and 11.11.0 is not advertising a Reload event via AMI. That event is the one that triggers fop2 to reload itself. It is a bug in Asterisk, but I was not able to verify when exactly was introduced. Without a reload event being broadcasted via AMI, external application will never know when a reload is happening, that is the actual problem.

    In the meantime, doing:

    service fop2 reload

    will reload the configuration. There is no need for an actual restart.

  3. bongfrog

    16 Sep 2014

    Thanks for your quick response. This explains quite a bit of the issues that are happening at this install. Any quick hack that could be done to expose the fop2 reload via the GUI that you can think of off the top of your head ?

    Thanks

  4. admin

    29 Sep 2014 Administrator

    I did more research, the problem with reloading happens since Asterisk 11.8.0, it does not happen on previous 11.x version, and it does not happen in Asterisk 12. It is a regression bug that was introduced at that point. As I cannot fix already released asterisk versions, I did some updates on the fop2 manager itself to try to solve the issue somehow. Now, with fop2manager 1.0.3 you have the option to "reload fop2", it is not asterisk anymore, but just fop2. Whenever you make a change in FreePBX, asterisk will fail to notify that via AMI on the affected asterisk releases, but you can log into fop2 manager and issue a "fop2 reload", that will sync changes between your backend and fop2 itself. (new buttons will show, groups will be auto recreated, etc).

    Best regards,

  5. bongfrog

    30 Sep 2014

    Thanks for working this issue to a usable solution . I know that this is a better solution than having cron reload fop2 at 3:00 evey night. grin

    Thanks again

or Sign Up to reply!