Upgraded 2.2.6 to 2.3 - crash report



  • I get a crash on dashboard

    seems to be something with nic´s ?

    i have one regular wan nic and one internal nic with a 4vlans

    ideas on what could cause this?

    running atom 1.86mhz

    amd64
    10.3-RELEASE
    FreeBSD 10.3-RELEASE #6 05adf0a(RELENG_2_3_0): Mon Apr 11 18:52:07 CDT 2016    root@ce23-amd64-builder:/builder/pfsense-230/tmp/obj/builder/pfsense-230/tmp/FreeBSD-src/sys/pfSense

    Crash report details:

    PHP Errors:
    [14-Apr-2016 06:32:26 Etc/UTC] PHP Stack trace:
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  1. {main}() /etc/rc.filter_configure_sync:0
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  2. filter_configure_sync() /etc/rc.filter_configure_sync:37
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  3. filter_generate_optcfg_array() /etc/inc/filter.inc:277
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  4. get_configured_interface_with_descr() /etc/inc/filter.inc:1107
    [14-Apr-2016 06:32:26 Etc/UTC] PHP Stack trace:
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  1. {main}() /etc/rc.filter_configure_sync:0
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  2. filter_configure_sync() /etc/rc.filter_configure_sync:37
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  3. filter_generate_gateways() /etc/inc/filter.inc:288
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  4. return_gateways_array() /etc/inc/filter.inc:880
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  5. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593
    [14-Apr-2016 06:32:26 Etc/UTC] PHP Stack trace:
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  1. {main}() /etc/rc.filter_configure_sync:0
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  2. filter_configure_sync() /etc/rc.filter_configure_sync:37
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  3. filter_generate_gateways() /etc/inc/filter.inc:288
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  4. return_gateway_groups_array() /etc/inc/filter.inc:881
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  5. return_gateways_status() /etc/inc/gwlb.inc:891
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  6. return_gateways_array() /etc/inc/gwlb.inc:418
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  7. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593
    [14-Apr-2016 06:32:26 Etc/UTC] PHP Stack trace:
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  1. {main}() /etc/rc.filter_configure_sync:0
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  2. filter_configure_sync() /etc/rc.filter_configure_sync:37
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  3. filter_generate_gateways() /etc/inc/filter.inc:288
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  4. return_gateway_groups_array() /etc/inc/filter.inc:881
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  5. return_gateways_status() /etc/inc/gwlb.inc:891
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  6. get_dpinger_status() /etc/inc/gwlb.inc:421
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  7. return_gateways_array() /etc/inc/gwlb.inc:369
    [14-Apr-2016 06:32:26 Etc/UTC] PHP  8. get_configured_interface_with_descr() /etc/inc/gwlb.inc:593
    [14-Apr-2016 06:32:26 Etc/UTC] PHP Stack trace:



  • I've got the same error after the update. Did you find a solution to this problem?



  • There have been a few threads with this style of traceback, like:
    https://forum.pfsense.org/index.php?topic=105760.0
    https://forum.pfsense.org/index.php?topic=104273.0

    If you can reproduce how to make this happen, or point out the special thing you have on your system that is the edge case that causes this (special network connection type, unusual settings on something…) then you win a prize :)



  • I solved my prb by removing all widgets and then adding them again

    /d



  • I have this problem too, i remove widget and reinstall but not solved



  • @phil.davis:

    There have been a few threads with this style of traceback, like:
    https://forum.pfsense.org/index.php?topic=105760.0
    https://forum.pfsense.org/index.php?topic=104273.0

    If you can reproduce how to make this happen, or point out the special thing you have on your system that is the edge case that causes this (special network connection type, unusual settings on something…) then you win a prize :)

    It seams that the error does not occur anymore, but I don't exacly know what fixed it. I think it was after I solved the problem with my squid installation using the information from these threads:
    https://forum.pfsense.org/index.php?topic=109128
    https://forum.pfsense.org/index.php?topic=105399