Hi.
I have just upgrade de Fop2 Manager from 1.0.2 to 1.0.3
I upgrade from the Fop2 Manager console.
But after the upgrade, when I made changes, I can't reload the FOP2
I clic on the Reload Option, but nothing happens
I also try to go Actions, and clic on Reload FOP2, but it doesn't make any action
For a work arround I restart de FOP2 service, but I guess I was not supose to do that.
No, it is not supposed to do that. Please be sure to refresh your browser cache, if it still fails, try opening the javascript console on the browser and see if you catch any warnings/errors in there when you attempt a reload.
Having the same problem too. The changes have been made as can be seen by running /usr/local/fop2/autoconfig-users-freepbx.sh . However there are not loaded.
The logs by performing a reload using the manager page are:
[15:16:04.309] POST http://10.111.111.200/fop2/admin/fop2reload.php [HTTP/1.1 200 OK 38ms]
[15:16:20.233] POST http://10.111.111.200/fop2/admin/pagebs.fop2users.php [HTTP/1.1 200 OK 684ms]
[15:16:30.203] POST http://10.111.111.200/fop2/admin/fop2reload.php [HTTP/1.1 200 OK 28ms]
Changes using the Fop2 manager are effected only by restarting fop2 service.
Instead of running 'service fop2 restart' from command line, a 'service fop2 reload' works in loading the changes in fop2 manager page.
The fop2reload.php page includes functions.php and the function reload_fop2 reads as:
function reload_fop2() {
global $astman, $conf;
if(!$res = $astman->connect($conf['MGRHOST'].':'.$conf['MGRPORT'], $conf['MGRUSER'] , $conf['MGRPASS'], 'off')) {
unset($astman);
}
if ($astman) {
$res = $astman->UserEvent('ZAP/1','Reload');
unset($_SESSION[MYAP]['needsreload']);
}
}
You have to use the latest fop2 2.28 for the UserEvent reload to work, otherwise use the hup signal or Asterisk 12, it is possible to patch Asterisk >11.8 too to get the module reload events that were muted since that release due to a regression bug.
We're running Asterisk 11.6 and Fop2 2.28. The upgrade to Fop2 Manager 1.03 is causing the reload button in Fop2 Manager not to work.
By changing a line in functions.php from:
$res = $astman->UserEvent('ZAP/1','Reload');
back to
$res = $astman->reload();
makes the reload to work again.
We're not running ZAP.
ZAP is used as a dummy channel, it is not the issue with the reload. The issue is that you need 2.28 as of last week that has that slight change to accept userevent reloads, because Asterisk 11.8 and higher does not advertise reloads anymore via manager (because of a bug in those versions). Anyways, if you have a previous asterisk version, then doing an asterisk reload will work for fop2 also as you already found out.
Sorry to wake such an old post but I am having the same problem.
When I make changes to buttons or users, the changes only take affect after running "service fop2 reload".
The reload in the manager doesn't work for me.
I have 2.28 installed and had management 1.0.3. just upgraded the management to 1.0.5 (which now says version 2.0) and still same problem.
Any ideas what I should check?
Thanx
Update FOP2 to the latest version (2.29). There are two versions of 2.28 (because I did not had minor revisions implemented by then) One reloads when Asterisk sends a Reload event via the Asterisk Manager. Unfortunately, there is a regresion bug in Asterisk and since version 11.8 or so and up, those events are not sent. This does not happen on Asterisk 12 or 13, or asterisk previous 11.8.
So I have implemented a way to signar a Reload via manager UserEvents, and that was included in the latest 2.28, or on the new 2.29.00. So, Upgrade to 2.29.00, or reinstall 2.28 and reloads should work when you do an action "Reload FOP2" from the Asterisk Manager.
Or if you use an unaffected Asterisk version, the reload should be done when asterisk is reloaded also.
Best regards,
Thanx for your reply. Problem is my license is more than a year old so it doesn't let me upgrade.
I tried manually copying the files but "fop2_server -v" still says I have 2.28
Re-download FOP 2.28 for your platform and install over, that is all you should need to do, without touching license files or anything like that.
Best regards,