Haproxy trouble after upgrade of pfsense 2.2.4 to 2.2.5-RELEASE



  • Hi,

    yesterday (2015-11-19) we upgraded pfsense from version 2.2.4 to 2.2.5-RELEASE. The upgrade itself was successful and pfsense worked well until today. About an hour ago, the administration frontend wasn't available anymore. Our ops restarded the webgui, lighttpd and php-fpm, which enabled us to log into the administration frontend again.

    Since then, we're receiving this error message in the haproxy-widget on the dashboard:
    Warning: stream_socket_client(): unable to connect to unix:///tmp/haproxy.socket (Connection refused) in /usr/local/pkg/haproxy_socketinfo.inc on line 43

    Does this error originate in the gui-restart, i.e. will this error most presumably disappear if we restart pfsense, or are we talking about bigger trouble here?
    The haproxy stats in the services area show very typical data.

    Best regards
    Thomas



  • Is haproxy process still running? Stats page works?
    If its not running that could cause the dashboard error..

    Try to save a setting in the package and 'apply'. That might tell if there is a configuration issue.



  • Hi PiBa,

    when I add the widget now, it will show up, displaying the correct values. After the next page reload, it's gone again.
    If I open the settings dialog and save them, as you suggested, I get a CSRF-error:

    CSRF check failed. Your form session may have expired, or you may not have cookies enabled.

    Debug:

    Cookies are allowed though and I also reloaded the web-page.



  • Hi Treuss,
    After adding a widget you must first save the new dashboard layout, before modifying the settings of the newly added widget.
    Regards,
    PiBa-NL



  • Hi PiBa,

    thanks for the hint. I totally overlooked this.

    However, saving the widget-layout and afterwards the widget's settings doesn't help either. We're still receiving this warning.
    The line the warning relates to is:
    43: $socket = stream_socket_client('unix:///tmp/haproxy.socket', $errno, $errstr);

    /tmp/haproxy.socket does exist and looks exactly the same as on another instance of pfsense in our networks.

    Thanks for your help and best regards
    treuss

    @PiBa:

    Hi Treuss,
    After adding a widget you must first save the new dashboard layout, before modifying the settings of the newly added widget.
    Regards,
    PiBa-NL



  • Hi treuss,

    Then im afraid i have to ask the same questions again:
    -Is haproxy process still running?
    -Stats page works?
    -If its not running that could cause the dashboard error..

    Try to save a setting in the package and 'apply'. That might tell if there is a configuration issue.

    p.s. If you have configured a carp interface to monitor it will shutdown haproxy on the backup node. Might explain the error there..

    Regards,
    PiBa-NL


Log in to reply