Viewing 3 replies - 1 through 3 (of 3 total)
  • Hello, Brandon, & welcome to the WordPress support forum. Do you perchance have access to the server error logs? This might tell us a great deal. Another thing you might consider doing is to *briefly* define wp-debug to false in order to see if there are any errors being thrown there. You’ll likely see them when you go to the site homepage. Please do turn this off as soon as you’ve obtained the information you need, though, as the security hole it creates makes the grand canyon look like a child’s sandbox lol.

    You don’t tell us if this is a single or multisite install. You also don’t provide a site url, which can be of immense help when attempting to help someone troubleshoot these sorts of problems. Nor do you state what type of server you’re running or the version of your OS, which can also help when giving instructions.

    Lastly, you might try running a mysql check/repair utility (it’s usually better to shut down the server first) to repair any corruption of the database that may have occurred.

    Let us know how this goes, won’t you? & feel free to paste error log entries or wp-config entries (minus credentials–please!) for us to have a look at if you’d like.

    Thread Starter brees

    (@brees)

    I believe I have access to all logs- but where do I find the particular logs that will help me?

    Did you intend to say briefly define wp-debug to true? (I think you did.)
    I did so and (unsurprisingly) immediately saw a mysql error. I’m not sure how much is safe to provide here…

    The first portion of the error reads:
    [The MySQL server is running with the –read-only option so it cannot execute this statement]

    The statement that it cannot execute is an INSERT INTO wp_options and involves the option name _transient_doing_cron.

    To answer your other questions:
    1. This is a single install
    2. The site url is http://www.accuquote.com
    3. The server is Linux – 3.13.0-71-generic, running Ubuntu 14.04.3

    I haven’t ran a mysql check/repair yet, but will move onto that if I am unable to find anything to address this issue.

    Thread Starter brees

    (@brees)

    This is solved. It turns out that the configuration for the HA mysql cluster was set up improperly. When the master failed, the slave was not properly promoted. As a result, writing to the DB was unavailable.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Database connection resolves itself; can't login to admin’ is closed to new replies.