FOP2 server requires constant restarts

bgouldfop2bgouldfop2
in Support
The latest update of my licensed FOP seems to broken its stability. FOP2 server is requiring constant restarts to show ANY controls other than logout on the status screen. "service fop2 restart" stops and starts the service and all the buttons and controls appear. No error reported, such as connection unavailable, when navigating to the fop2 web page just no visible content in the form of extensions, trunks, queues and so forth.

I wonder if this is related to DND status is showing on most phones as DND when in reality that is not the case in FREEPBX or the phones themselves.

Comments

  • nicolasnicolas
    If all buttons shows as DND and they are not, then there is an obvious misconfiguration somewhere. I cannot tell you what is wrong just from your post, you will have to catch me on the live help so we can review your installation.

    One thing that might help is gather more information about your config. What is the output from:

    /usr/local/fop2/autoconfig-buttons-freepbx.sh | grep -i astdb

    ? Actually the whole content is important, but it will probably disclose sensitive information about your system that you do not want ot make public, that is why it is better to handle this via live help if possible.

    Best regards,
  • FreerPBXerFreerPBXer
    We're seeing the same thing: Suddenly all the extension buttons in the web gui disappear; they don't show as busy, they are just gone. All that shows is the top nav bar. I'll get a screen cap the next time it happens.

    Restarting the FOP2 service fixes the problem every time.
  • nicolasnicolas
    A screenshot won't help much. The description is quite clear in itself. What is needed is try to determine what causes the issue. Only then we can work on a fix. If we cannot reproduce the problem, we won't be able to trace the cause and work on a fix.

    As a start, it is important to know what freepbx version are you using, what asterisk version and what fop2 *and* fop2admin versions.
  • bgouldfop2bgouldfop2
    admin, your request for more details make perfect sense. I'm running 5.211.65-4 from PBX DISTRO upgraded via the freepbx updates service. so thats decoded as Centos 6.5 (Final) and Freepbx 2.11

    fopadmin 1.2.15
    fop2 2.27

    the poster "FreerPBXer" described our symptom exactly
  • nicolasnicolas
    admin, your request for more details make perfect sense. I'm running 5.211.65-4 from PBX DISTRO upgraded via the freepbx updates service. so thats decoded as Centos 6.5 (Final) and Freepbx 2.11

    fopadmin 1.2.15
    fop2 2.27

    the poster "FreerPBXer" described our symptom exactly

    Thanks. So what did you do in the FreePBX GUI? Uploaded a recording file ? If it happens to you often, then start fop2 in debug mode and look at the last part of the log file when the issue happens. You can start fop2 in debug mode by settings the options line in /etc/sysconfig/fop2 to be

    OPTIONS="-d -X 511 -l /var/log"
  • bgouldfop2bgouldfop2
    Okay, I'll do use the debug tools soon and let you know what happens. As far as I can tell the only thing I did in FREEPBX was to enable/disable some of the extensions and attach them to named groups, sort by ext number, submit, apply and verify FOP2 used the new information.

    Assuming this is related, the DND indicators do not match the station statuses and a new kind of mis information was discovered today. Caller id NAMES do not transfer with the call as shown on FOP2 screen. Yes, asterisk did transfer both the Name and Number from the receptionist to the destination phones. The name that showed up in FOP2 was the name of the receptionist that did the transfer but the NUMBER of the incoming caller.
  • nicolasnicolas
    Okay, I'll do use the debug tools soon and let you know what happens. As far as I can tell the only thing I did in FREEPBX was to enable/disable some of the extensions and attach them to named groups, sort by ext number, submit, apply and verify FOP2 used the new information.

    Assuming this is related, the DND indicators do not match the station statuses and a new kind of mis information was discovered today. Caller id NAMES do not transfer with the call as shown on FOP2 screen. Yes, asterisk did transfer both the Name and Number from the receptionist to the destination phones. The name that showed up in FOP2 was the name of the receptionist that did the transfer but the NUMBER of the incoming caller.

    Callerid is not related at all. What you see in FOP2 is what asterisk advertises via AMI. Anything you see there is sent/set by Asterisk. So, if you see some unexpected callerid after a transfer, that callerid was set by Asterisk and informed in AMI events (the ones fop2 uses). SIP dialog is a totally different thing and it is what make your phone display work. But if you see an inconsistency in the callerid is because asterisk informed it that way. So, the fix is in your asterisk or asterisk config, not in fop2.
  • bgouldfop2bgouldfop2
    That makes sense that FOP2 can only display what it receives. I dont have time to debug asterisk code again, fun but not profitable, so your answer may also explain DND indicators not matching the station status.
  • nicolasnicolas
    That makes sense that FOP2 can only display what it receives. I dont have time to debug asterisk code again, fun but not profitable, so your answer may also explain DND indicators not matching the station status.

    Regarding DND there is a common misconception. Phone DND status cannot be monitored by Asterisk (nor FOP2 or any other tool that connects to Asterisk itself). Only if the phone button is programmed to dial a special feature code to Asterisk, or if you set yourself in DND using that feature code directly (like FreePBX *78 / *79) you can then monitor that state with FOP2.

    So, phone DND button cannot be monitored, but setting yourself in dnd by featurecode can.
  • bgouldfop2bgouldfop2
    Okay, Time to regroup. I'm not trying to monitor the phone DND status, just the asterisk status. It does follow the status if I use the DND button to dial *78/*79. On the other hand several extension indicate a DND state in FOP2 but when I send a call to those extension asterisk says the extension is free and delivers the call. Dialing *78 and then *79 on those extensions sets and clears the phone indicator and the FOP2 indicator.

    Restarting the FOP2 service re-indicates the extension is in DND but asterisk delivers calls all the same.
  • nicolasnicolas
    FOP2 does nothing in particular but sets a couple of astdb entries in its default configuration. One for its own status display, another one for FreePBX based systems that rely on the DND/xxxx entry so the dialplan will deliver calls to them or not.

    astdb in itself does nothing, you have to write your own dialplan macros to act according to them. Not sure if you are using FreePBX or not, or in what way, but it seems your dialplan is not checking the DND/xxx database entry. The dialplan is not something fop2 cares about. Up to that point, it is asterisk and your dialplan config that should be checked.

    Take into account that fop2 can also be altered to not set the DND astdb entry but issue a queue member pause instead. Version 2.27 has two plugins that change behavior, you can have one or the other, but not both.
  • bgouldfop2bgouldfop2
    I'm running FreePBX 2.11, Asterisk 11.

    I issue these commands to inform asterisk and fop2 about my intentions:
    database put fop2state SIP/30 "Do not Disturb"
    database put DND 30 YES

    Asterisk responds properly by refusing calls to extension 30 and directly routes calls to VM.
    FOP2 does not update the DND indicator on the status page.

    IF I do:
    database del fop2state SIP/30
    database del DND 30

    Again asterisk responds correctly and resumes sending calls to extension 30.
    FOP2 does not change the DND indicator.

    Service FOP2 restart updates the display indicators.

    At this point I've manually removed all fop2state/SIP/xxx entries and the display screen is clear of DND indicators. I'll let it run unmolested for a day and see what happens.
  • nicolasnicolas
    Appart from the astdb values that are for persistent state and to indicate FreePBX dialplan from the DND value, you need a way to indicate manager application of those changes. AMI does not show any events when astdb entries are stored, if you search in the forum you will see several post talking about how to change the fop2 display in realtime. That is done using manager userevents.

    I do not event know why we are discussing this on this topic that has nothing to do with dnd indications? In any case, here is the post you need:

    View Post 1405#p5495
  • bgouldfop2bgouldfop2
    Ahh, the problem with forums is the lack of context sometimes and mission creep. Thank you for working through it
  • ScotttTneusScotttTneus
    Regarding the fop2 debug mode. I am having the same issue on our system (fop2 stops working, service fop2 restart fixes the problem).
    These are my system specs;
    Asterisk: 1.4.22-4
    Linux: 2.6.18-128.1.10.e15
    Trixbox: 2.6.2.3
    FOP framework: 2.5.0.4
    FOP2 Admin: 1.2.13


    Is this debug line edit in fop2 sysconfig location valid for my system also? Also, once it fails again, where would the log files be located? i am fairly new to trixbox & freepbx. Also not very Linux savy (Thank God for Google!).

    Thanks
  • nicolasnicolas
    You did not say what fop2 version are you running, but it seems it is not the latest one, it might be 2.24 or 2.26. The log files will be /var/log/error.log and /var/log/output.log . If fop2 crashes, the relevant info will be displayed at the end of /var/log/error.log

    You should consider updating fop2 (and also asterisk, your version is now outdated).

    Best regards,
  • ScotttTneusScotttTneus
    Sorry, My fop2 version is: 2.26

    How do I update the fop2 version? I looked through the "packages/module" updates and do not see it.
    These are the upgrades I see;
    two - Astra Telecom XML scripts upgrades. (v2.1.1-1 & v2.3.0-1) (not sure if I need to upgrade these)
    two - tbm-GUIcore - The base of the Trixbox GUI modules (v2.6.2.3-1 & v2.6.2.5-1) (probably should upgrade)

    I will edit the fop config to add the debug code and wait for it to fail again then check the logs.

    Thanks for your help
  • nicolasnicolas
    to upgrade fop2 you must do it from the server command line. Just download the latest .tar.gz from www.fop2.com/download.php, then extract it and run "make". Remember that upgrades are free for one year, after that year there is a $20 upgrade cost (annual software maintenance from www.fop2.com/buy.php).

    Best regards,
  • ScotttTneusScotttTneus
    fop2 service finaly failed and this is what i am getting in the debug log file.

    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018.
    Use of uninitialized value in concatenation (.) or string at script/fop2_server.pl line 7018. (thi line goes on for 100's, then)
    Payload is too big. Deny big message (3170943617) or increase max_payload_size (65536) at script/fop2_server.pl line 1712.


    Any idea of what is causing this?
  • nicolasnicolas
    The error of payload to big is in the websocket protocol, you will avoid that problem if you disable websockets in /var/www/html/fop2/js/presence.js or by using the latest 2.27 version. You do not say if you updated fop2 or not already? In any case, the payload size seems *too* big for a normal fop2 packet. Did you upgrade to 2.27?
  • ScotttTneusScotttTneus
    I did disable the websocket. Thank you. I have not done the upgrade yet. But most likely will with in the next couple weeks.
  • nicolasnicolas
    If you saw the payload too big error, then websockets was NOT disabled, as it is an exclusive error of a browser connecting over websockets. Take into account that the presence.js file can be cached in the browser , so the setting won't do any effect until the browser reloads that file from the server.

    Best regards,
  • ScotttTneusScotttTneus
    Ah, So end users will have to clear their cache. okay. Thanks.
Sign In or Register to comment.

© Asternic Corp 2024