• Resolved wordpressuser101

    (@wordpressuser101)


    Hi,

    I am currently experiencing a problem with my WordPress installation when I try to update the plugins or WordPress (4.8) to version (4.8.1). In fact, I use Apache to run my installation and I get an error saying: “… exit signal Segmentation fault (11)..”. After some debugging, it seems to be related to php_ssh2_fopen_wraper_parse_path from /usr/lib/php5/20121212/ssh2.so. All the current version is up to date for the OS distribution. Here is my configuration versions:

    # php -v
    PHP 5.5.9-1ubuntu4.22

    # lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 14.04.5 LTS
    Release: 14.04
    Codename: trusty

    # apachectl -V
    Server version: Apache/2.4.7 (Ubuntu)

    And here is the debugging info:

    (gdb) bt
    #0 __strstr_sse2_unaligned () at ../sysdeps/x86_64/multiarch/strstr-sse2-unaligned.S:22
    #1 0x00007f2ac746e2d8 in php_ssh2_fopen_wraper_parse_path () from /usr/lib/php5/20121212/ssh2.so
    #2 0x00007f2ac747225c in ?? () from /usr/lib/php5/20121212/ssh2.so
    #3 0x00007f2acea27e07 in _php_stream_stat_path () from /usr/lib/apache2/modules/libphp5.so
    #4 0x00007f2ace9a3a95 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #5 0x00007f2ace9a5d8b in zif_file_exists () from /usr/lib/apache2/modules/libphp5.so
    #6 0x00007f2ace8dc8c6 in phar_file_exists () from /usr/lib/apache2/modules/libphp5.so
    #7 0x00007f2acea5defb in dtrace_execute_internal () from /usr/lib/apache2/modules/libphp5.so
    #8 0x00007f2aceb1d2f0 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #9 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #10 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #11 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #12 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #13 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #14 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #15 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #16 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #17 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #18 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #19 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #20 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #21 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #22 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #23 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #24 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #25 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #26 0x00007f2acea600f1 in zend_call_function () from /usr/lib/apache2/modules/libphp5.so
    #27 0x00007f2ace993132 in zif_call_user_func_array () from /usr/lib/apache2/modules/libphp5.so
    #28 0x00007f2acea5defb in dtrace_execute_internal () from /usr/lib/apache2/modules/libphp5.so
    #29 0x00007f2aceb1d2f0 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #30 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #31 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #32 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #33 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #34 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #35 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #36 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #37 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #38 0x00007f2aceb1d940 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #39 0x00007f2acea97c28 in execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #40 0x00007f2acea5ddf9 in dtrace_execute_ex () from /usr/lib/apache2/modules/libphp5.so
    #41 0x00007f2acea6f480 in zend_execute_scripts () from /usr/lib/apache2/modules/libphp5.so
    #42 0x00007f2acea0fce5 in php_execute_script () from /usr/lib/apache2/modules/libphp5.so
    #43 0x00007f2aceb1ef92 in ?? () from /usr/lib/apache2/modules/libphp5.so
    #44 0x00007f2ad3028100 in ap_run_handler (r=0x7f2ad30810a0) at config.c:169
    #45 0x00007f2ad3028649 in ap_invoke_handler (r=r@entry=0x7f2ad30810a0) at config.c:439
    #46 0x00007f2ad303dc1a in ap_process_async_request (r=r@entry=0x7f2ad30810a0) at http_request.c:317
    #47 0x00007f2ad303def4 in ap_process_request (r=r@entry=0x7f2ad30810a0) at http_request.c:363
    #48 0x00007f2ad303a992 in ap_process_http_sync_connection (c=0x7f2ad308a290) at http_core.c:190
    #49 ap_process_http_connection (c=0x7f2ad308a290) at http_core.c:231
    #50 0x00007f2ad3031770 in ap_run_process_connection (c=0x7f2ad308a290) at connection.c:41
    #51 0x00007f2ad3031b58 in ap_process_connection (c=c@entry=0x7f2ad308a290, csd=<optimized out>) at connection.c:202
    #52 0x00007f2acf457767 in child_main (child_num_arg=child_num_arg@entry=7) at prefork.c:704
    #53 0x00007f2acf4579a6 in make_child (s=0x7f2ad3230de0, slot=7) at prefork.c:800
    #54 0x00007f2acf45860e in perform_idle_server_maintenance (p=<optimized out>) at prefork.c:902
    #55 prefork_run (_pconf=<optimized out>, plog=<optimized out>, s=<optimized out>) at prefork.c:1090
    #56 0x00007f2ad300d28e in ap_run_mpm (pconf=0x7f2ad3256028, plog=0x7f2ad322a028, s=0x7f2ad3230de0) at mpm_common.c:96
    #57 0x00007f2ad30062e6 in main (argc=3, argv=0x7fffcab3a218) at main.c:777

    Thanks for your help!

Viewing 5 replies - 1 through 5 (of 5 total)
  • I am seeing what would seem to be the same issue. I am running the same versions of Apache, PHP, Ubuntu & WordPress. (Another ‘feature’ of this issue is that Settings->General page in dashboard will not load unless I comment out the FTP_PUBKEY etc details in wp-config.php).

    ETA: just realised that what I have linked to below is an old bug report. So what follows may not be pertinent:

    I am not certain – but I believe that this time the issue may be with Ubuntu rather than WordPress. There is a bug report re the version of php-ssh2 here: https://bugs.launchpad.net/ubuntu/+source/php-ssh2/+bug/1617294

    (NB: that bug report relates to the 16.04 LTS version of Ubuntu)

    There is also a thread at StackExchange – again it relates specifically to 16.04 and not 14.04. https://askubuntu.com/questions/786102/upgraded-ubuntu-to-16-04-now-wordpress-updates-dont-work/946745#946745

    So as above I had the same issue with the same versions. This is how I have fixed it.

    (Take a snapshot first so that you can revert to the previous version if necessary)

    1. I ran ‘sudo pecl install ssh2-0.13’
    This is the version compatible with PHP 5 according to https://pecl.php.net/package/ssh2

    2. According to the console message on installation: ‘You should add “extension=ssh2.so” to php.ini’

    3. At this point my plugin update error message changed to: ‘Unable to locate WordPress content directory (wp-content)’. I fixed this by adding ‘define(‘FS_METHOD’, ‘direct’);’ in wp-config.php

    Updates now work. I don’t really fully understand these steps which isn’t great –
    I have really only followed a recipe.

    Thread Starter wordpressuser101

    (@wordpressuser101)

    Thanks for the solution, it worked well (just have to change permission). In fact, i think that in step 3, WordPress bypass that at-risk detection and always create files using the ‘direct’ method. I think it can be a security risk in specific situation like “poorly” configured shared host. Anyway, you can always just add the line when you need to update stuff and deleted it after!

    Pleased you got it fixed. Your original question helped me find out how to fix it. I am surprised there are not more installations experiencing this issue. Despite having found a solution for this I would like to understand better why the issue has suddenly arisen. So if anyone else reading this has any ideas …

    Good point about ‘FS_METHOD’, ‘direct’ – thanks for pointing that out since anyone else reading this thread should be aware of possible implications. In my own case I am okay I believe since I am running and managing my own servers and installations. But I understand that as you say it could be an issue for people running on shared hosting.

    Step 1 and 2 worked for me but not Step 3. Then I found this one that works for me: https://core.trac.ww.wp.xz.cn/ticket/35517#comment:23

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

The topic ‘segfault when trying update WordPress/plugin versions’ is closed to new replies.