critical database error

  • Resolved freshuk

    (@freshuk)


    2 years, 9 months ago

    hello
    since few days ago, i am having those errors in the log, related to decalog.
    few hundreds times a day, i can’t seem to understand when exactly.
    ?? Critical [0] A database error was detected during the page rendering: “Table XXXXXXXXXXXXX.wp_decalog_fd50e8dfb3e24da5845d285a21e18833 doesnt exist“ in the query “SELECT COUNT(*) as CNT FROMwp_decalog_fd50e8dfb3e24da5845d285a21e18833`;“.

    the token after wp_decalog_x changes in each error, but the error is the same.
    any idea? i think it started since i installed other perfops plugins such as sessions, api traffic, ip locator and opcache manager. will try to disable them and see if it solves the issue.

    thank you !

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Hello @freshuk !
    Do you still have this error? Are you sure there’s many “random tokens” or just some (2 or 3)?

    Thread Starter freshuk

    (@freshuk)

    yes i am still having this one a lot
    https://snipboard.io/KZg21N.jpg
    and yes it seems there are 2 or 3 different tokens

    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    Some DecaLog tables have been deleted outside the current DecaLog process.
    It can be a manual operation maintenance or another plugin.

    Normally each DecaLog logger have an id (you can find it in the url when you modify it, or via wp-cli). This ID is what you call a token. I suggest you to identify the loggers having as id the token you see in the error and suppress/recreate them.

    Thread Starter freshuk

    (@freshuk)

    Thanks, makes sence ??
    How do i recreate them without cli access?

    Plugin Author Pierre Lannoy

    (@pierrelannoy)

    DecaLog will recreate it when you will recreate the corresponding loggers.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘critical database error’ is closed to new replies.