Fatal memory error and database now inaccessible

  • thewebwriter

    (@thewebwriter)


    15 years, 7 months ago

    Greetings,
    My client’s host moved our site last week due to speed and other issues.
    This morning as I was reactivating a couple plugins, I ran into this error, and then was unable to do anything with wp-admin
    Fatal Error Allowed memory size of 33554432 bytes exhausted (tried to allocate 491520 bytes) …. wp-admin/menu.php on line 235

    After searching wp.org support forums, I tried editing wp-config.php with this line and ftp’d it up:
    define(‘WP_MEMORY_LIMIT’, ’32M’);

    At which point, the site is now totally inaccessible, with message “Cannot access database” (I fear I put that define line in the wrong place in wp-config – ? – but I didn’t change anything else in the file)

    I haven’t been able to get any attention from our host.

    I’d really appreciate any help.

    Thanks.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Samuel B

    (@samboll)

    15 years, 7 months ago

    you can put that inwp-config.php anywhere before it says “stop editing”
    however 32M wouldn’t be enough – more like 128M

    you need to ftp to site or use host’s file manager to rename the /plugins folder
    this will deactivate them and let you in
    rename folder back to activate plugins

    Thread Starter thewebwriter

    (@thewebwriter)

    15 years, 7 months ago

    Thanks, Samuel. I must say I’m worried about “breaking something” and something else going wrong.

    So, do I understand:
    1. rename plugins folder (to anything) and I should be able to get past the “cannot access database” notice and be able to access wp-admin panel?
    2. then try adding that line again in wp-config
    3. then rename plugins folder back to plugin and all should be well?

    Samuel B

    (@samboll)

    15 years, 7 months ago

    correct

    Thread Starter thewebwriter

    (@thewebwriter)

    15 years, 7 months ago

    Thank you again – very much. I sent this on to my host support and then waited a while longer so I wouldn’t interfere if they were working on it too and they just wrote that everything is “back to normal” (tho I’ll definitely be a bit gun shy for a while now).

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

The topic ‘Fatal memory error and database now inaccessible’ is closed to new replies.