PHP ERROR causing pfsense crash



  • Notifications in this message: 1
    ================================
    
    15:40:25 PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 4238, Message: Uncaught Error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc:4238
    Stack trace:
    #0 /usr/local/pkg/pfblockerng/pfblockerng.inc(4151): pfb_dnsbl_lastevent('', 'v10.vortex-win....', '')
    #1 /usr/local/pkg/pfblockerng/pfblockerng.inc(3978): pfb_log_event('DNSBL-HTTPS', 'v10.vortex-win....', '192.168.[xxx.xxx redacted]', 'Unknown')
    #2 /usr/local/pkg/pfblockerng/pfblockerng.inc(406): pfb_daemon_dnsbl()
    #3 {main}
      thrown
    

    I receive the above error via email shortly before pfsense crashes. Upon crash, all LAN/WAN is inaccessable, and SSH and console are also unresponsive. Pfsense can only be recovered by hard reset.

    I am currently running 2.4.4-RELEASE-p2 and pfBlockerNG-devel 2.2.5_22. However, this error has happened every couple weeks for a few months, and would have happened with earlier versions of pfblockerNG-devel as well.

    I haven't been able to find any similar situations through searching the webs. Any help and suggestions would be greatly appreciated!


  • Moderator

    Do you have enough free hard drive space in this box? Memory? Do you have any other errors in the pfSense system.log?



  • Hi BBcan177, I appreciate the reply, I have been a big fan of your work for some time.

    I have plenty of hard drive space (6% of 12GiB) and memory (25% of 4GiB). Please see dashboard screenshot.
    dashboard.png
    I don't see other obviously related errors in the log, I do have these, but I'm not sure if they are related.

    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80680430, 0) error 1
    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806804e0, 0) error 1
    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80680590, 0) error 1
    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff806a7460, 0) error 1
    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff806a7510, 0) error 1
    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff806a75c0, 0) error 1
    Mar 26 16:47:38	kernel		module_register_init: MOD_LOAD (vesa, 0xffffffff81209800, 0) error 19
    


  • I am still having this issue every 2-3 weeks. It is very frustrating as it can only be recovered by manual hard reset. This is the most recent notification I received today:

    Notifications in this message: 1
    ================================
    
    1:45:29 PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 4238, Message: Uncaught Error: Call to a member function bindValue() on boolean in /usr/local/pkg/pfblockerng/pfblockerng.inc:4238
    Stack trace:
    #0 /usr/local/pkg/pfblockerng/pfblockerng.inc(4151): pfb_dnsbl_lastevent('', 'settings-win.da...', '')
    #1 /usr/local/pkg/pfblockerng/pfblockerng.inc(3978): pfb_log_event('DNSBL-HTTPS', 'settings-win.da...', '192.168.[xxx.xxx redacted- different LAN IP as previous]', 'Unknown')
    #2 /usr/local/pkg/pfblockerng/pfblockerng.inc(406): pfb_daemon_dnsbl()
    #3 {main}
      thrown
    

    Any assistance would be greatly appreciated!


  • Moderator

    @Risfold
    I have made a few revisions to the code to address this issue.
    Changes here:
    https://gist.github.com/BBcan177/fd7aa11babc3280ab593cacb86a60257/revisions

    To test, please run the following command to download this patched file:

    fetch -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/fd7aa11babc3280ab593cacb86a60257/raw"
    

    Follow that with a restart of the "pfb_dnsbl" service.

    Let me know if the error repeats. Thanks!



  • @BBcan177 thank you very much for looking at this. I will implement the patched file and report back if the error recurs. I'll also respond in 3-4 weeks if there is still no issue.


Log in to reply