<![CDATA[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/perl

which 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

]]>http://localhost:4567/topic/705/fop2-suddenly-stopped-workingRSS for NodeTue, 27 Oct 2026 05:46:39 GMTTue, 05 Apr 2011 03:04:20 GMT60<![CDATA[Reply to FOP2 suddenly stopped working on Tue, 05 Apr 2011 11:39:08 GMT]]>Thanks,

I had already managed to set the FOPRUN=false but had not stopped it afterwards!!!

So that fixed the issue

😄

]]>http://localhost:4567/post/3092http://localhost:4567/post/3092Tue, 05 Apr 2011 11:39:08 GMT<![CDATA[Reply to FOP2 suddenly stopped working on Tue, 05 Apr 2011 10:45:28 GMT]]>The update re-enabled or changed fop1 port back to 4445, preventing FOP2 from starting. You can disable fop1 by setting

FOPRUN=false

in /etc/amportal.conf . So it does not start on the next reboot. Then stop the current running fop1:

/usr/sbin/amportal stop_fop

and start fop2

service fop2 start
]]>http://localhost:4567/post/3091http://localhost:4567/post/3091Tue, 05 Apr 2011 10:45:28 GMT