Huge WSAL metadata table not being cleaned

  • Resolved chrisbfinternet

    (@chrisbfinternet)


    9 years, 1 month ago

    Hi there,

    This is more of an “FYI” to the developers than anything else, but maybe there’s a better solution than the one we’ve found:

    • We use WSAL on maybe 50+ websites, we install it by default because it’s so useful
    • We don’t change any settings, just leave it as default
    • Yesterday we noticed wsal_metadata was huge on some sites – 3m+ rows (some of our sites are quite active!)
    • Not all sites are affected, but the ones that are show “Next Scheduled Cleanup is in 9 months” (or some other time long in the future)

    So it would seem that by default SOME sites aren’t running the clean up.

    The fix we’re finding is to delete the plugin (checking “Remove Data on Uninstall”) and reinstall. These steps alone change the message “Next Scheduled Cleanup is in 5 minutes” and everything’s okay.

    Maybe the cron isn’t being set up correctly. Is there a better fix than to delete & reinstall? Ideally something we can run from WP-CLI.

    Cheers,
    Chris

    https://www.ads-software.com/plugins/wp-security-audit-log/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author WPWhiteSecurity

    (@wpwhitesecurity)

    Hello chrisbfinternet,

    Thanks a lot for showing interest in our plugin and for the detailed feedback. I have a few questions regarding your scenario:

    1. In the early versions of the plugin we did have some problems related to scheduling, but they have been fixed quite some time ago. Could it be that the instances you are noticing are old versions of the plugins that have been updated?

    2. Do you still have a similar case? If so would it be possible to check the wp_wsal_options table prior to deleting the table?

    The archiving options are stored in the wp_wsal_options table and with what you are recommending you are deleting the table and recreating it from scratch.

    Looking forward to hearing from you.

    Thread Starter chrisbfinternet

    (@chrisbfinternet)

    Hi there,

    We had another one today. It started life with an old version of the plugin, but was maintained with upgrades.

    The fix outlined above did the trick (and has worked 100% since) but here is the contents of the wp_wsal_options table prior to deleting:

    (1, 'wsal-pruning-date', '1 month'),
(2, 'wsal-pruning-limit-e', ''),
(3, 'wsal-pruning-limit', '5000'),
(4, 'wsal-promo-send-id', '1'),
(5, 'wsal-pruning-date-e', '1'),
(6, 'wsal-disable-widgets', ''),
(7, 'wsal-plugin-viewers', ''),
(8, 'wsal-plugin-editors', ''),
(9, 'wsal-excluded-users', ''),
(10, 'wsal-excluded-roles', ''),
(11, 'wsal-excluded-custom', ''),
(12, 'wsal-excluded-ip', ''),
(13, 'wsal-restrict-admins', ''),
(14, 'wsal-disable-refresh', ''),
(15, 'wsal-use-proxy-ip', ''),
(16, 'wsal-filter-internal-ip', ''),
(17, 'wsal-hide-plugin', ''),
(18, 'wsal-delete-data', ''),
(19, 'wsal-datetime-format', '0'),
(20, 'wsal-wp-backend', ''),
(21, 'wsal-columns', '{"alert_code":"1","type":"1","date":"1","username":"1","source_ip":"1","message":"1"}'),
(22, 'wsal-dev-options', '');

    Before deleting, the settings page did state “Next Scheduled Cleanup is in 1 min (or Run Manually)” but it clearly wasn’t running, and didn’t clean the table when I ran manually (it just crashed out, whitescreen).

    Plugin Author WPWhiteSecurity

    (@wpwhitesecurity)

    Thank you for sending in more details. We will surely look into this and issue a fix with the next update.

    Will keep you posted.

    We’re experiencing a similar issue. I haven’t tried deleting the content as I’d rather the cleanup worked and I was able to keep 1 month of data, but our table has grown to 850,000 rows and that’s an issue for BackupBuddy, so I need to do something.

    I experience the same issue with the ‘Next Scheduled Cleanup’ which seems to be increasing in time and doesn’t seem to run. Attempting to run the cleanup manually also crashes with a white screen.

    @itsnotrocketsurgery: This is not your topic & has been resolved. If you require assistance then, as per the Forum Welcome, please post your own topic.

    Plugin Author WPWhiteSecurity

    (@wpwhitesecurity)

    Hello @itsnotrocketsurgery, as @esmi explained this is not your topic and has indeed been resolved. So if you are still encountering this issue it might be that you are not using the latest version of the plugin.

    Else, please open a new ticket. Thank you very much.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Huge WSAL metadata table not being cleaned’ is closed to new replies.