WordPress.org

Ready to get started?Download WordPress

Forums

Upgrade to 3.2.1 and now intermittent 500 errors (7 posts)

  1. mherzber
    Member
    Posted 2 years ago #

    So I did the update to 3.2.1 and I was getting a lot of blank screens and 500 errors. I went to my error logs and I had the allocated memory issue that people were talking about. So I upped to 128M and those errors went away. I am still getting the intermittent blank screens and 500 errors. The next obvious step is plugins or theme. My theme is a solid child theme of the genesis framework so I assume that is solid. As far as the plugins, like I said the error is sometimes not all the time. So I cant do a one by one turnoff plugins and see what happens. The new error however that has been cropping up recently and around since when I upped the memory to php is

    [notice] child pid 22307 exit signal Segmentation fault (11)

    and I am still getting the blank screen and 500 error.

    So I am not sure what to do to fix this issue or if that error from the log would even be related. Any help is much appreciated

  2. mherzber
    Member
    Posted 2 years ago #

    Just to add I do meet the php and mysql requirements and I tried a manual update as well

  3. esmi
    Forum Moderator
    Posted 2 years ago #

    Try:

    - switching to the Twenty Eleven theme to rule out any theme-specific problems.

    - resetting the plugins folder by FTP or PhpMyAdmin.

    Then monitor the site for errors and see what happens.

  4. mherzber
    Member
    Posted 2 years ago #

    I did both those and still having the blank screen issues. The main error that can be reproduced on server is [notice] child pid 22307 exit signal Segmentation fault (11)

  5. mherzber
    Member
    Posted 2 years ago #

    I am now getting

    [Tue Aug 02 22:51:03 2011] [notice] child pid 15707 exit signal Segmentation fault (11)

  6. Cathy Tibbles
    Member
    Posted 2 years ago #

    What host do you use?

  7. Kurt Payne
    Member
    Posted 2 years ago #

    Is your host using any opcode caches (APC, eAccelerator, xcache, etc.) or Zend Extensions (zend optimizer, xdebug, xhprof, ioncube, etc.) or the suhosin patch? If you set up a phpinfo page, you should be able to do a search in your browser to find out if any of these things are present.

Topic Closed

This topic has been closed to new replies.

About this Topic