fop2 manager cannot connect after upgrade to 2.28

mbr01

Hi,
My system is Elastix 2.5. I installed fop2 from the add ons web page. Fop2 is working fine (version 2.25).

I then update to fop2 version 2.28 by manually download the update and do the 'make install' command.
As per another post, I then issue the following commands :
cp /usr/local/fop2/fop2.cfg /etc/asterisk/fop2
cp /usr/local/fop2/autoconfig* /etc/asterisk/fop2
cp /var/www/html/fop2/index.html /var/www/html/fop2/fop2.html
then update /etc/asterisk/fop2/fop2.cfg with the manager credentials.

But now fop2 manager cannot connect, reporting that authentication is failing:

[root@ELASTIX25 fop2]# /usr/local/fop2/fop2_server --debuglevel 9
Flash Operator Panel 2 - License file fop2.lic not found.
127.0.0.1 <- Response: Success
127.0.0.1 <- ActionID: 1
127.0.0.1 <- Challenge: 631291271

127.0.0.1 <- Response: Error
127.0.0.1 <- ActionID: 2
127.0.0.1 <- Message: Authentication failed

Failed to connect to asterisk - localhost:5038
Error Message: Login Failed to Asterisk (bad auth) at localhost:5038. Check your manager credentials!
Error occured on socket FOP2::AMI2=HASH(0x16b62e50)
CLEAN activity for buttons for server localhost as the connection was lost

Removing /var/www/html/fop2/fop2-variablesGENERAL.txt...

The thing is I am confident that my login/pwd are ok in fop2.cfg (and in manager.conf).
When I use the very same credentials in another app connecting to AMI, it's working fine. So for me the manager side is ok.

Any help appreciated.
Thanks

mbr01

This is a follow up to my previous post.

I just found that if I update /usr/local/fop2/fop2.cfg instead of /etc/asterisk/fop2, then fop2 server can connect.
So my question is, is it how it is supposed to work ? If yes, then why copying the file from /usr/local/fop2 to /etc/asterisk/fop2 ?

thanks

nicolas

The key for the confusion is the service init script. When your system starts fop2, or when you use "service fop2 start", "service fop2 stop", etc... it uses the init.d script to start/stop. That script reads command line options that are specified in the /etc/sysconfig/fop2 file, one of those options changes the default directory for configuration files to /etc/asterisk/fop2

RPM based installation, by request of distro mantainers, changed the config location from the default /usr/local/fop2 to /etc/asterisk/fop2

So, in Elastix, that uses .rpm for its package, the configuration files are in that location. That is why in the instructions I post for upgrading from elastix to a tarball version I added those commands to copy config files to the locations specified in the /etc/sysconfig/fop2 file

So, if you want to run the --test option with the fop2 server, to verify if the manager connects or not, you also have to pass the -c command line parameter you have in the OPTIONS line in the /etc/sysconfig/fop2 file:

/usr/local/fop2/fop2_server --test -c /etc/asterisk/fop2

When specifying that directory, then the test will be done with parameters set in /etc/asterisk/fop2/fop2.cfg file, the same file that will be used when your service starts at boot or via service start/stop commands.

Best regards,

mbr01

Thanks for the explanations.
This makes sense now.
Have a good day