FOP 2.26 suddenly stops
Hello,
We have several installations of FOP 2.26 on FreePBX 2.9: all work well and there were no problems.
Only by a client we are notified that about once a month FOP2 suddenly stops and they are no longer able to login to the web interface. When I connect I note that the service is actually stopped.
I tried to enable debugging, as you have indicated in several posts, but given the rarity of the problem I could not pick up anything interesting.
After a few months, the issue is becoming quite critical.
Do you have any suggestion or solution to the problem?
The version 2.27beta could solve the problem? Since this is a "beta" I can make sure that there are no other instabilities that could worsen the situation of our client?
Thanks
Best regards
Marco
We have several installations of FOP 2.26 on FreePBX 2.9: all work well and there were no problems.
Only by a client we are notified that about once a month FOP2 suddenly stops and they are no longer able to login to the web interface. When I connect I note that the service is actually stopped.
I tried to enable debugging, as you have indicated in several posts, but given the rarity of the problem I could not pick up anything interesting.
After a few months, the issue is becoming quite critical.
Do you have any suggestion or solution to the problem?
The version 2.27beta could solve the problem? Since this is a "beta" I can make sure that there are no other instabilities that could worsen the situation of our client?
Thanks
Best regards
Marco
Comments
OPTIONS="-d (and whatever other options you might have) -X 4 -l /tmp"
Debug level 4 is not verbose, so you can keep it running for several days and it won't produce a large output, in /tmp you wil end up with the output.log file with no useful data, and the error.log file that will contain the actual error for a crash, if what you are experience is indeed a crash. If you see "payload to big", it is the websocket issue I mentioned and is fixed it by disabling it or upgrading.
Best regards,
thanks for the quick response. I will try as soon as possible to enable debugging and eventually to disable websocket.
I would point out also that I noticed something else quite curious: when I restart FOP2 after a crash, I find that the license is disactivated. Thus, I have to reactivate it manually. Is this the normal behavior?
P.S. When it is scheduled the final release of FOP 2.27?
Thanks again
Best regards
Marco
I disabled the websocket and enabled the debug.
For now, all right, we will see in the coming days.
Thanks for the support.