Service stops for no reason (fixed)
-
-
What fop2 version are you running?
/usr/local/fop2/fop2_server -v
If you want to see if fop2 is crashing or similar, you must run it in debug mode, one way is to use gnu screen and output to screen, or use the -l command line option to output debug.
With screen:
service fop2 stop
cd /usr/local/fop2
screen
./fop2_server -X 511
ctrl-a dThat will run fop2 inside a screen session with full debug output, when you notice fop2 is not running anymore, you attach to that screen with the command
screen -r
You will see the last log lines and probable error there.
It is also helpful to know if you configured buttons manually or via autoconfiguration, as a misconfiguration can lead to unexpected crashes under certain situations.
And last, use always the latest version, if you are using any previous version than 2.26, then upgrade.
Best regards,
-
fop2_server version 2.25
Flash Operator Panel 2 - White Label Version.
** COLLECT INCLUDES fop2.cfg , tipo server
** READ SERVER CONFIG
** READ SERVER CONFIG - archivo fop2.cfg
** READ SERVER calling COLLECT INCLUDES archivo buttons_as2.cfg context AS2!buttons** COLLECT INCLUDES buttons_as2.cfg , tipo AS2!buttons
** /usr/local/fop2/buttons_as2.cfg not readable... skipping
** READ SERVER calling COLLECT INCLUDES archivo rabat.cfg context RABAT!buttons
** COLLECT INCLUDES rabat.cfg , tipo RABAT!buttons
** READ SERVER calling COLLECT INCLUDES archivo santexia.cfg context SANTEXIA!buttons
** COLLECT INCLUDES santexia.cfg , tipo SANTEXIA!buttons
** READ SERVER calling COLLECT INCLUDES archivo buttons_santexia.cfg context CASA!buttons
** COLLECT INCLUDES buttons_santexia.cfg , tipo CASA!buttons
** READ SERVER calling COLLECT INCLUDES archivo buttons.cfg context GENERAL!buttons
** COLLECT INCLUDES buttons.cfg , tipo GENERAL!buttons
** READ SERVER calling collect_includes rabat.cfg
** COLLECT INCLUDES rabat.cfg , tipo RABAT!buttons
** rabat.cfg already included
** READ SERVER calling collect_includes santexia.cfg
** COLLECT INCLUDES santexia.cfg , tipo SANTEXIA!buttons
** santexia.cfg already included
** READ SERVER calling collect_includes buttons_santexia.cfg
** COLLECT INCLUDES buttons_santexia.cfg , tipo CASA!buttons
** buttons_santexia.cfg already included
** READ SERVER calling collect_includes buttons.cfg
** COLLECT INCLUDES buttons.cfg , tipo GENERAL!buttons
** buttons.cfg already included
** READ BUTTONS CONFIG rabat.cfg para contexto RABAT
** READ BUTTONS CONFIG santexia.cfg para contexto SANTEXIA
** READ BUTTONS CONFIG buttons_santexia.cfg para contexto CASA
** READ BUTTONS CONFIG buttons.cfg para contexto GENERAL** GENERA CONFIG START
** GENERA CONFIG - GENERAL
** GENERA CONFIG - CASA
** GENERA CONFIG - RABAT
** GENERA CONFIG - SANTEXIA
** GENERA CONFIG - AS2
** GENERA CONFIG ENDCan't listen to port 4445
-
You cannot start it because it is already running or you have another application binding to port 4445, but that happens just after starting, it is not a crash after working for some time.
Do you have fop1 running? Stop it and disable it, or change its listenting port so fop2 can bind to 4445.
netstat -lnp | grep 444
If you see 4445 taken by perl, then it is fop1, stop it:
/usr/sbin/amportal stop_fop
disable it editing /etc/amportal.conf and set FOPRUN=false
or better yet, if you have a recent FreePBX, uninstall the FOP Framework.
-
I have been using this for years they are not set to the same port and when it crashes it does not allow
Us to login yet it is already running I wi remove foo1 but that was set to a different port many years
Ago when we bought fip2. You also seem to have new version should we aprudadeThanks for the help
-
If you upgraded FreePBX or some of its modules FOP1 will be back to the default port unless you disable it, or change its port back. I recommend to disable it to avoid having issues if you upgrade or install some new freepbx version again.
You might want to upgrade to the latest fop2 version as it works with the latest browsers using websockets, and it also has some new features, but you can continue using your version if you are happy with it.
-
it won't let me stop it but I did set it to sales
[trixbox1.localdomain fop2]# netstat -lnp | grep 444
tcp 0 0 0.0.0.0:4445 0.0.0.0:* LISTEN 32230/perl
[trixbox1.localdomain fop2]# service fop2 stop
Shutting down Flash Operator Panel 2: [FAILED]
[trixbox1.localdomain fop2]# -
You have to stop FOP1, NOT FOP2.
/usr/sbin/amportal stop_fop
edit /etc/amportal.conf and set
FOPRUN=false
Then start fop2
service fop2 start
And if you can , uninstall the fop framework from freepbx using the module manager to avoid issues on your next freepbx upgrade.
-
-
contact me via the live help, you are not following the instructions correctly. The problem is REALLY simple, you have to stop whatever you have listening in port 4445, after that fop2 will work.
I am on the live help, this post is of no use because I already told you what to do , and it seems you are missing a command at some point.
-
AS i said the service works fine for a while then we no longer can login to FOP2. When we try to restart the service it tell sme that the port is already in use when i try to stop the service it won't stop. I did try you on chat but you were off line before will try you tomorow
-
If you say the service stops, I understand is because fop2_server is not running. So if you cannot login, check if its running with the command
pgrep fop2
If that command returns empty, then it is in fact not running. But if it is not running, you should not get the "Cannot listen to port 4445"
If the service is stopped, then do what I typed in the 1st reply EXACTLY to start fop2 and capturing output, so you can catch the error.
Again, I am on the live help if you still cannot follow the directions I wrote.
Best regards,
-
To avoid other people hijacking this post, and give a response to the "NO REASON" of the subject.
The REASON was that this user configuration involved multiple server monitoring (something he never stated in the post), and a firewall was set by him to prevent connections to the AMI port from the fop2 server to that 2nd server he had configured in fop2.cfg
So the NO REASON was actually someone that changed firewall rules and breaking his setup.
Doing exactly the commands I stated on the FIRST reply on this post via live help, the error popped out really clearly and was easily fixed then.
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