PHP Fatal error: Uncaught mysqli_sql_exception

  • dimal

    (@dimalifragis)


    3 months, 1 week ago

    Hi,

    Today we had a large scale attack and there are several of those in the error.log (for some reason nothing was logged in the enabled debug.log):

    [02-May-2024 14:44:01 Europe/Athens] PHP Fatal error: Uncaught mysqli_sql_exception: Resource temporarily unavailable in /home/public_html/wp-content/plugins/ninjafirewall/lib/firewall.php:439
    Stack trace:
    #0 /home/public_html/wp-content/plugins/ninjafirewall/lib/firewall.php(439): mysqli_real_connect()
    #1 /home/public_html/wp-content/plugins/ninjafirewall/lib/firewall.php(93): nfw_connect()
    #2 /home/public_html/wp-content/nfwlog/ninjafirewall.php(10): include_once(‘/home/public_html/…’)
    #3 {main}
    thrown in /home/public_html/wp-content/plugins/ninjafirewall/lib/firewall.php on line 439

    Apparently the sql was accepting a huge ammount of connections and refused to serve more for a while. We had to mitigate it, changing our IP. It came from a “cloud” platform of a well known company.

    Not sure if the exception should be more kindly treated or not. Also not an issue for me, JFYI to maybe help make the plugin better.

    Thanks

Viewing 1 replies (of 1 total)
  • Plugin Author nintechnet

    (@nintechnet)

    3 months, 1 week ago

    The plugin makes one single connection to the DB, but it was not reachable because of the attack, hence the fatal error. The call to mysqli_real_connect() is silenced with error control operator @, just like WordPress does. I don’t know if we can/need to change anything, because there’s no way the site can recover from that. Even without NinjaFirewall, WordPress couldn’t load and would throw the same error.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.