Fatal database-error

  • iskwew

    (@iskwew)


    18 years, 2 months ago

    Since upgrading to 2.3.x I have been getting an error message, when editing any posts:

    Fatal error: Allowed memory size of 16777216
    bytes exhausted (tried to allocate 354231
    bytes) in /customers/iskwew.com/iskwew.com/httpd.www/b
    logg/wp-includes/wp-db.php on line 123

    My webhotel (One.com) say that they only allocate 16 MB worth of resources to each user, and thats all they can say.

    Is there anything in the setup I can do, which will fix this issue? Oddly enough, everything is posted, even though it is saying it cannot allocate the resources.

    Thanks in advance for any advice on/solution to this problem.

    Iskwew

Viewing 6 replies - 1 through 6 (of 6 total)
  • yogipress

    (@yogipress)

    18 years, 2 months ago

    at the risk of assuming your setup, try adding this to your apache .htaccess file.

    php_value memory_limit 128M

    Thread Starter iskwew

    (@iskwew)

    18 years, 2 months ago

    Thanks for replying!

    What does that do, if the problem is resources allocated by the server?

    yogipress

    (@yogipress)

    18 years, 2 months ago

    hmm mmm-kay, let me back up for a second.

    instead of the apache .htaccess file, try changing the php.ini file. you are looking for the following section:

    ;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 30     ; Maximum execution time of each script, in seconds
max_input_time = 60	; Maximum amount of time each script may spend parsing request data
memory_limit = 8M      ; Maximum amount of memory a script may consume (8MB)

    change the 8M to 28M.
    then give it another go.

    * crosses fingers *

    Thread Starter iskwew

    (@iskwew)

    18 years, 2 months ago

    Poor you, you are going to get stupid questions :o) (I’m pretty clueless).

    Where is the php.ini file located? I can’t find it :o/

    Thread Starter iskwew

    (@iskwew)

    18 years, 2 months ago

    I don’t have php on the domain, it sits on the service provider.

    htaccess I find, but not the php.ini

    yogipress

    (@yogipress)

    18 years, 2 months ago

    there are no stupid questions. you are not clueless. the software just needs more elbow grease in the user experience department. 🙂 ask away…

    let’s try to work with what you have, try the .htaccess fix i mentioned first.

    hope we can find the solution.

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

The topic ‘Fatal database-error’ is closed to new replies.