Skip to:
Content
Pages
Categories
Search
Top
Bottom

Segmentation fault after update to 2.0.1


  • grayson_marik
    Participant

    @grayson_marik

    Hello,
    I have been trying to update from 1.9.2 to 2.0.1 for a while now. Whenever i install the new version and click on activate, the site simply crashes and is not available again, until i rename the buddypress folder.
    Interesting is, if i install buddypress 1.9.2 again, this activation works flawless.

    So far i have not been able to track the error down. in apaches error log, no php errors are shown, prior to the crash ( yes, pohp loggiin is on and working and stores into apaches error log). it simply starts:
    [Fri Jun 20 16:16:51.729370 2014] [core:notice] [pid 27371] AH00052: child pid 27377 exit signal Segmentation fault (11)

    This happens on every refresh then.

    I am completely clueless, any idea?

    Some system info:

    Server: OS Linux Software Apache/2.4.9 (Ubuntu) Version 32Bit
    WordPress: VER 3.9.1
    Mem: WP 128M (def) Usage 11% 14.16M of PHP Limit 128M
    System: PHP 5.5.12-2+deb.sury.org~precise+1 Active Plugins 16 Zend 2.5.0
    Database: SQL 5.5.37 Build 5.5.37-0ubuntu0.12.04.1 Charset utf8

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

  • r-a-y
    Keymaster

    @r-a-y

    BuddyPress 2.0 runs two migration scripts:
    https://buddypress.trac.wordpress.org/browser/tags/2.0/bp-core/bp-core-update.php#L349

    One that moves the last activity entries from user meta to the BP activity table. This migration might be what is causing your site to stall. Do you have a large userbase?

    Second, a script is made to create a wp_signups table and move old unactivated signups to this new table. Do you have a lot of unactivated users?

    Your memory doesn’t appear to be hitting its limit, so it’s not a memory problem.

    You might want to do some Googling. Here’s a quick result that I came across:
    http://www.omh.cc/blog/2008/mar/6/fixing-apache-segmentation-faults-caused-php/

    Hope that helps. Would be great to figure out what is wrong.


    grayson_marik
    Participant

    @grayson_marik

    Well, currently I have 20 unconfirmed users and my user base is around 2000 users atm. I will check it out later today, thank you so far.


    grayson_marik
    Participant

    @grayson_marik

    well, debugging was no success, also the check for the things you suggested not. I deleted all pending sign ups and all activity… still the same


    grayson_marik
    Participant

    @grayson_marik

    Hmm seems like the database stuff works in the update script, because i have no activities in usermeta any more. what happens after the db update script? and where the heck is the bb version number to be found in the database?


    lukewarmmizer
    Participant

    @lukewarmmizer

    Curious if you had any more luck with this? I am having the same problem, but with CentOS 5.10, Nginx 1.6, and spawn-fcgi. The site will sometimes work, and sometimes not. Removing the buddypress folder from the plugins directory will cause the site to start loading again, but putting it back breaks it. The only errors are:

    /var/log/messages
    Jul 29 01:13:13 web1 kernel: php-cgi[4904]: segfault at 000000000000002c rip 00000000005bc7f8 rsp 00007fff8d7752f0 error 4

    /var/log/nginx/error.log
    2014/07/29 01:17:59 [error] 2474#0: *783 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.10.133.128, server: *.rovair.com, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:53217", host: "www.example.com", referrer: "https://www.example.com/wp-admin/"


    lukewarmmizer
    Participant

    @lukewarmmizer

    FWIW – I just downgraded from PHP 5.5 to PHP 5.4 and it works again. Not sure what is causing the incompatibility however, other than the errors posted above.


    grayson_marik
    Participant

    @grayson_marik

    Unfortunately downgrading to PHP 5.4 is not an option, as I use some of the fancy PHP 5.5 syntax enhancements on other areas of the page.

    Seems like I’ll have to wait for either a major PHP update that solves this miracle or a BuddyPress update that does.

    Strange though, that the error is reproducible but untraceable … Ah well, maybe I am simply too bad as server admin 😉

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Segmentation fault after update to 2.0.1’ is closed to new replies.
Skip to toolbar