FOP2 suddenly stopped working
-
Hi FOP2 has been working great for months then today suddenly it stops, ran yum updates and freepbx updates (Using Elastix 2)
Getting this:
[root@elastixv2 fop2]# /usr/local/fop2/fop2_server --test
/usr/local/fop2/autoconfig-buttons-freepbx.sh: line 15: [: too many arguments
Connection to manager OK!but its saying that its connection to the manager is OK
and this
[root@elastixv2 fop2]# netstat -lnp | grep 444
tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 3044/perlwhich i fear is the problem as 4445 should be fop2 not perl but if that is the case how did this change happen and how can i correct it? this happened before any updates were done too
Thanks
Robert -
The update re-enabled or changed fop1 port back to 4445, preventing FOP2 from starting. You can disable fop1 by setting
FOPRUN=falsein /etc/amportal.conf . So it does not start on the next reboot. Then stop the current running fop1:
/usr/sbin/amportal stop_fopand start fop2
service fop2 start -
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login
