Field ‘attackLogTime’ doesn’t have a default value

  • Resolved bighippo999

    (@bighippo999)


    2 years, 11 months ago

    Hi,

    I’m getting the following error in nginx errors logs:

    2021/05/25 19:38:22 [error] 43013#43013: *1951552 FastCGI sent in stderr: “PHP message: WordPress database error Field ‘attackLogTime’ doesn’t have a default value for query INSERT INTO{blanked}_wfhits(ctime,statusCode,isGoogle,IP,userID,URL,referer,UA,jsRun,action,id) VALUES (‘1621967899.091028’, ‘200’, ‘0’, ‘\0\0\0\0\0\0\0\0\0\0{blanked}’, ‘282’, ‘{blanked}/xmlrpc.php’, ”, ‘Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0’, ”, ‘loginFailValidUsername’, ‘0’) made by wfModel::insert” while reading upstream, client: {blanked}, server: {blanked}, request: “POST /xmlrpc.php HTTP/1.1”, upstream: “fastcgi://unix:/var/run/php/php-fpm.sock:”, host: “{blanked}”

    I thought this may have occurred after we migrate the entire database to a new server, so I’ve just:
    1) Took a backup of the Wordfence settings.
    2) Enabled the delete tables on disable.
    3) Update .user.ini to stop loading wordfence.
    4) Disabled the plugin.
    5) Delete the plugin.
    6) Confirmed the tables were removed (all except the 2fa ones).
    7) Re-installed Wordfence.
    8) Import the backed up settings.
    9) Update .user.ini to load it again.

    The tables were recreate and it’s correct ‘attackLogTime’ (and ‘ctime’) still have no default value. The above INSERT is still erroring because of the ‘attackLogTime’.

    Any chance this can be looked at? It’s making it hard tracking down other real errors.
    Cheers,

    • This topic was modified 2 years, 11 months ago by bighippo999. Reason: code tag didn't work, trying b-quote
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support WFAdam

    (@wfadam)

    2 years, 11 months ago

    Hello @bighippo999 and thanks for reaching out to us!

    My first recommendation would have been to delete the tables, as you already have done.

    Since that didn’t fix it, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    What sort of server API was the server on previously, then what API did you move to? You mentioned NGINX but I like to verify. If you know the answer to that, it could be helpful.

    Thanks again!

    Thread Starter bighippo999

    (@bighippo999)

    2 years, 11 months ago

    Hi @wfadam

    🙂

    Report sent.

    API? The Database server was previously it’s own server running MariaDB (maybe 10.4 can’t remember) on Ubuntu 18.04. And web servers nginx and php7.4-fpm on Ubuntu 18.04. As part of maintenance we’ve built up a new server on Ubuntu 20.04 and migrate everything to that. MariaDB 10.5 (I think), still nginx and php7.4-fpm. Additional web servers can be brought online and will use this first server for DB and NFS but at present since it’s quiet everything is on one server but it’s got more base resources CPU,RAM etc than ever before (that’s not really important lol).

    When we migrate from the old DB server to the new each database was export and import then new users were create with new passwords and finally the wp-config.php DB info was update.
    I didn’t expect there to be any issue with the _wfhits table after export/import, but run through the disable/delete tables just in case there had been to let the plugin recreate the tables fixing any issues. Since the problem still exists it’s wasn’t an issue caused by moving the DB or sites (phew lol).

    Cheers,

    Plugin Support WFAdam

    (@wfadam)

    2 years, 10 months ago

    Sorry for the delay @bighippo999 !

    Could you send the diagnostic once again, I believe it to be buried in our inbox somewhere.

    Thanks for your patience!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Field ‘attackLogTime’ doesn’t have a default value’ is closed to new replies.