Users cannot log in after FreePBX/Asterisk update

Jeffrey Smith

After updating FreePBX to 10.13.66 and Asterisk to 13.5, users cannot log in to FOP2. When testing with
/usr/local/fop2/fop2_server -c /etc/asterisk/fop2 --test
I get the following output:
Flash Operator Panel 2 - Valid License (1)
Can't exec "/etc/asterisk/fop2/amipasswd.sh": Permission denied at script/fop2_server.pl line 579, <$CONFIG> line 271.
Can't exec "/etc/asterisk/fop2/autoconfig-users-freepbx.sh": Permission denied at script/fop2_server.pl line 579, <$CONFIG> line 271.
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x24909a0/FOP2/AMI2.pm line 311
Failed to connect to asterisk - localhost:5038
Error Message: Timed out waiting for challenge

Does anyone have advice on how to correct this?

nicolas

Try this command

chmod a+x /etc/asterisk/fop2/*.sh

And then test it with:

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

In any case, is there any particular reason to use /etc/asterisk/fop2 for the fop2 config directory? What FOP2 version do you have installed?

Jeffrey Smith

I ran:
chmod a+x /etc/asterisk/fop2/*.sh

Now testing with:
/usr/local/fop2/fop2_server -c /etc/asterisk/fop2 --test
returns:
Flash Operator Panel 2 - Valid License (1)
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x1baa9a0/FOP2/AMI2.pm line 311
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x1baa9a0/FOP2/AMI2.pm line 311
Failed to connect to asterisk - localhost:5038
Error Message: Timed out waiting for challenge

Users still cannot log in.

Checking version with:
/usr/local/fop2/fop2_server -v
returns:
fop2_server version 2.27

I have no particular reason for using /etc/asterisk/fop2. I assume that is where the original installation put the files or instructed me to put the files.

nicolas

The "make install" script in FOP2 puts everything in /usr/local/fop2 by default, since the first release. /etc/asterisk/fop2 is used only in Elastix RPM packages and now deprecated FreePBX rpm package. My suggestion is to use the standard location. What is the output from this command:

cat /etc/sysconfig/fop2

?

As for the error when you run --test, it seems you do not have the Asterisk Manager enabled, you will have to enable it by modifying the file /etc/asterisk/manager.conf. Be sure it is enabled there, then restart Asterisk, then try --test in fop2.

Jeffrey Smith

Running:
cat /etc/sysconfig/fop2
Returns:
OPTIONS="-d -c /etc/asterisk/fop2"

Running:
cat /etc/asterisk/manager.conf
Shows "enabled = yes" (see full contents below)

Rebooted server, but --test returns the same errors:
Flash Operator Panel 2 - Valid License (1)
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x1692ad0/FOP2/AMI2.pm line 311
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x1692ad0/FOP2/AMI2.pm line 311
Failed to connect to asterisk - localhost:5038
Error Message: Timed out waiting for challenge

Could the deny/permit settings in manager.conf be a problem?


cat /etc/asterisk/manager.conf
;
; AMI - Asterisk Manager interface
;
; FreePBX needs this to be enabled. Note that if you enable it on a different IP, you need
; to assure that this can't be reached from un-authorized hosts with the ACL settings (permit/deny).
; Also, remember to configure non-default port or IP-addresses in amportal.conf.
;
; The AMI connection is used both by the portal and the operator's panel in FreePBX.
;
; FreePBX assumes an AMI connection to localhost:5038 by default.
;
[general]
enabled = yes
port = 5038
bindaddr = 0.0.0.0
displayconnects=no ;only effects 1.6+

[admin]
secret = amp111
deny=0.0.0.0/0.0.0.0
permit=127.0.0.1/255.255.255.0
read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate,message
write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate,message
writetimeout = 5000

#include manager_additional.conf
#include manager_custom.conf

nicolas

Try this:

ping localhost

What is the output ?

Jeffrey Smith

Running:
ping localhost
Returns:
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.048 ms

nicolas

edit /etc/asterisk/fop2/fop2.cfg and set

manager_host=127.0.0.1

instead of localhost. Then try again. Also, be SURE you run fop2_server as root or via sudo.

Jeffrey Smith

After changing manager_host from localhost to 127.0.0.1 I am still getting the same error (see below).
I am logged in as root when I run the test.

Flash Operator Panel 2 - Valid License (1)
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x1519ad0/FOP2/AMI2.pm line 311
EV: error in callback (ignoring): Unknown warnings category 'FOP2::AMI2' at /loader/0x1519ad0/FOP2/AMI2.pm line 311
Failed to connect to asterisk - 127.0.0.1:5038
Error Message: Timed out waiting for challenge

nicolas

Hi,, the erro ris quite clear. FOP2 is unable to connect to port 5038 on your server. That is the default port for Asterisk AMI. So you might have some firewall rules preventing that connection, or AMI is not enabled in Asterisk. You will need to fix that, the problem is not with FOP2. What is the output from this:

netstat -lnp | grep 5038

?

And this:

iptables -vnL

?

Jeffrey Smith

I'm sure that the problem was created by something in the update to FreePBX/Asterisk and isn't a error in FOP2. I do appreciate you taking time to help me debug it. There is a new firewall component in FreePBX, but disabling it doesn't seem to help with the error I am getting.

Running:
netstat -lnp | grep 5038
Returns:
tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 3461/asterisk

Running:
iptables -vnL
Returns over 200 lines. Is there something specific in that that I should pull out or do you want it all?

nicolas

Perhaps that firewall component in FreePBX is denying the connection to port tcp/5038 to FOP2, is hard to tell just from the forum post. Try to catch me on the live help, maybe we can remote into your system to check all those firewall rules and see if they might be causing that issue or if its something else. You can always try by disabling the firewall and running /usr/local/fop2/fop2_server --test after disabling it.

It might also be a syntax error in fop2.cfg, like having the file saved in DOS format (not unix format). Having an extra space somewhere, etc.

Best regards,