Unexplained log entry in error.log

  • There is a repeating log entry in the apache error.log file:
    ====
    [Wed Feb 10 08:49:13 2016] [error] [client 192.0.116.176] WordPress database error Table ‘[redacted]’ doesn’t exist for query SELECT option_value FROM wp_sample_option
    WHERE option_name = ‘[redacted]’ LIMIT 1 made by wp_xmlrpc_server->serve_request,
    IXR_Server->IXR_Server, IXR_Server->__construct, IXR_Server->serve, IXR_Server->call,
    IXR_Server->multiCall, IXR_Server->call, call_user_func, Jetpack_XMLRPC_Server->json_api,
    WPCOM_JSON_API->serve, WPCOM_JSON_API->process_request, call_user_func_array, WPCOM_JSON_API_GET_Site_Endpoint->callback,
    WPCOM_JSON_API_GET_Site_Endpoint->build_current_site_response, get_site_url,
    switch_to_blog, WP_Roles->reinit, get_option
    ====

    1) What does this related to?

    2) How to remove it?

    (Everything seems to be normal otherwise. Blog:
    https://blogs.strategygroup.net/wp2/economy/ )

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Jose Castaneda

    (@jcastaneda)

    THEME COFFEE MONKEY

    Hi there!

    Does this happen if you deactivate all your plugins?

    Thread Starter theneteconomy

    (@theneteconomy)

    Hi –

    Can’t tell. Noticed the issue only after the plugins were installed and configured.

    You redacted the table name, but the error message is telling you that the table doesn’t exist:

    WordPress database error Table '[redacted]' doesn't exist

    Use whatever database admin UI your host provides, e.g., phpMyAdmin, to see if that table indeed does not exist. If so, you’ve found the cause of the problem. The fix would be to identify the source of the table–probably it will be clear from the table name–and then figure out why it was not created. One potential reason is that the database user you set up for WordPress doesn’t have the correct permissions to create tables, so that when you installed the corresponding plugin, it wasn’t able to create the table.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Unexplained log entry in error.log’ is closed to new replies.