Title: Firewall / 404 Detection – Database problem
Last modified: November 14, 2018

---

# Firewall / 404 Detection – Database problem

 *  Resolved [lmobile](https://wordpress.org/support/users/lmobile/)
 * (@lmobile)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/)
 * Dear support
 * it is not possible for us to get access to the tab “404 Detection” within aiwops
   firewall tab. We always receive a 500 server error if we try.
 * Also we receive a warning message from our backup tool:
 * > Die Tabelle lweb_aiowps_events hat sehr viele Zeilen (438411) – wir hoffen,
   > dass dein Webhoster dir genügend Ressourcen für einen Dump dieser Tabelle zur
   > Verfügung stellt. Falls nicht, musst du entweder Daten aus dieser Tabelle löschen,
   > oder deinen Hosting-Anbieter bitten, dir mehr Ressourcen zur Verfügung zu stellen.
 * This error causes that database is not backuped anymore at the moment.
 * How to fix that? Thanks for your help Marc
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Ffirewall-404-detection%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Contributor [wpsolutions](https://wordpress.org/support/users/wpsolutions/)
 * (@wpsolutions)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/#post-10881498)
 * Hi,
    Looks like the automatic wp cron process which checks this plugin’s tables
   for size and deletes the oldest rows does not seem to be working on your site.
 * You can try a simple step to see if it works – deactivate and reactivate this
   plugin and then wait a minute or two. If all is working properly that should 
   trigger the “aiowps_hourly_cron_event” which in turn will run the DB cleanup 
   tasks.
    If that doesn’t work I recommend that you trim that table manually using
   PHPMyAdmin or something similar.
 * Also you should check your server error log files to see if there are any useful
   logs which might help you to identify the cause of your issue.
 *  Thread Starter [lmobile](https://wordpress.org/support/users/lmobile/)
 * (@lmobile)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/#post-10882788)
 * Hi
 * thanks for advice. I tried, but still the size stays the same. To the trim the
   table we could easy delete the rows within lweb_aiowps_events? Or do we have 
   to note something else?
 * Thanks for your help Marc
 *  Plugin Contributor [wpsolutions](https://wordpress.org/support/users/wpsolutions/)
 * (@wpsolutions)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/#post-10885779)
 * > To the trim the table we could easy delete the rows within lweb_aiowps_events?
 * Yes if that’s the only table which is extraordinarily large. YOu might also want
   to check the other “aiowps” tables to see if any of those need trimming.
 * Did you check your server logs to see if there might be any logs related to this?
   
   Also you should check if the wp cron tasks are actually running on your site.(
   there are plugins which can help you to check this)
 *  Plugin Contributor [mbrsolution](https://wordpress.org/support/users/mbrsolution/)
 * (@mbrsolution)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/#post-10885877)
 * Hi [@lmobile](https://wordpress.org/support/users/lmobile/), you might like to
   try [WP Control](https://wordpress.org/plugins/wp-crontrol/) plugin.
 *  Thread Starter [lmobile](https://wordpress.org/support/users/lmobile/)
 * (@lmobile)
 * [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/#post-10887535)
 * Dear [@wpsolutions](https://wordpress.org/support/users/wpsolutions/)
 * we cleaned db entry lweb_aiowps_events and option page for 404 entries is now
   accessable again.
 * Thanks [@mbrsolution](https://wordpress.org/support/users/mbrsolution/) we checked
   with WP Control and cron aiowps_hourly_cron_event is active but seems not to 
   be working. We triggered the cron job but db size did not change.
 * Thanks for your help Marc

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Firewall / 404 Detection – Database problem’ is closed to new replies.

 * ![](https://ps.w.org/all-in-one-wp-security-and-firewall/assets/icon-256x256.
   png?rev=2798307)
 * [All-In-One Security (AIOS) – Security and Firewall](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/)
 * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/reviews/)

 * 5 replies
 * 3 participants
 * Last reply from: [lmobile](https://wordpress.org/support/users/lmobile/)
 * Last activity: [7 years, 8 months ago](https://wordpress.org/support/topic/firewall-404-detection/#post-10887535)
 * Status: resolved