• Resolved cwolff

    (@cwolff)


    Hi, getting many of these errors in the logs when a new Scan is initiated:

    [03-Oct-2018 18:28:58 UTC] WordPress database error DROP command denied to user ‘jis-cms’@’170.190.30.31’ for table ‘wp_wfhoover’ for query truncate table wp_wfHoover made by do_action(‘wp_ajax_wordfence_killScan’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::ajaxReceiver, wordfence::ajax_killScan_callback, wfUtils::clearScanLock, wfDB->truncate, wfDB->queryWrite

    The user in question does have DROP.

    Thanks for any help offered.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @cwolff,
    It should not possible for this specific error message to occur if the user is allowed to DROP. I would recommend you check to make sure you don’t have duplicate tables and that you are connecting to the right database.

    This query runs after the scan and cleans up scan data. Until you’ve figured it out you may need to truncate the wfhoover table manually to prevent it from getting very big.

    wfdave

    (@wfdave)

    Hi @cwolff,

    We haven’t heard back from you in a while. I’ve gone ahead and marked this thread as resolved. Please feel free to open another thread if you’re still having issues with Wordfence.

    Thanks!

    Thread Starter cwolff

    (@cwolff)

    Thank you wfdave.

    As suggested, giving the user “DROP” fixed the issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘WordPress database error DROP command denied to user’ is closed to new replies.