Updated Jetpack to latest version now errors

How is it resolved?

can we change the status of this thread as “[Resolved]” flag might be misleading

Done!

Hi Jeremy,
Is the new release Jetpack 4.7 compatible with PHP 7.1 now?
Regards,
Joseph

@zomidaily It should be, yes. We fixed some bugs, and then ran some tests on different servers running PHP 7.1. We also now run automated tests on PHP 7.1 for each one of the patches that get added to Jetpack.

@zomidaily – Ivan Atanasov here, part of the Senior Technical Support team at SiteGround.

We tested the functionality of the new Jetpack version with PHP 7.1 on our platform using a fresh WordPress installation.
No problems were found.

Hi Jeremy,
I was informed by SiteGround that the problem is caused by Related Posts module. Could you please check again?

Below is the relative part of the PHP process from SiteGround:

8390 25190 stat("/home/vaphual8/staging/2/wp-content/plugins/jetpack/modules/related-posts/jetpack-related-posts.php", {st_mode=S_IFREG|0644, st_size=49962, ...}) = 0
8391 25190 mmap(NULL, 2097152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa01bc00000
8392 25190 fcntl(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, len=1}) = 0
8393 25190 fcntl(3, F_SETLK, {type=F_UNLCK, whence=SEEK_SET, start=0, len=1}) = 0
8394 25190 mkdir("/home/vaphual8/.opcache", 0700) = -1 EEXIST (File exists)
8395 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c", 0700) = -1 EEXIST (File exists)
8396 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home", 0700) = -1 EEXIST (File exists)
8397 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8", 0700) = -1 EEXIST (File exists)
8398 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging", 0700) = -1 EEXIST (File exists)
8399 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2", 0700) = -1 EEXIST (File exists)
8400 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2/wp-content", 0700) = -1 EEXIST (File exists)
8401 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2/wp-content/plugins", 0700) = -1 EEXIST (File exists)
8402 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2/wp-content/plugins/jetpack", 0700) = -1 EEXIST (File exists)
8403 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2/wp-content/plugins/jetpack/modules", 0700) = -1 EEXIST (File exists)
8404 25190 mkdir("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2/wp-content/plugins/jetpack/modules/related-posts", 0700) = -1 EEXIST (File exist s)
8405 25190 open("/home/vaphual8/.opcache/b95da6d72ea733ba3e111d6406344e3c/home/vaphual8/staging/2/wp-content/plugins/jetpack/modules/related-posts/jetpack-related-posts.php.bin", O_RDWR|O_CREAT|O_EXCL, 0600) = 8
8406 25190 flock(8, LOCK_EX) = 0
8407 25190 mmap(NULL, 299008, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fa027efd000
8408 25190 --- SIGSEGV (Segmentation fault) @ 0 (0) ---

Thanks for the extra details.

We haven’t been able to reproduce the issue yet, but we’ll investigate further. I’ll let you know as soon as I have some news!

This could be an issue between OPcache and WordPress’ XML-RPC requests (which Jetpack uses to communicate with WordPress.com).

You can read more about it here:
https://ethitter.com/2017/01/upgrading-to-php-7-1/

@ivanatanasov Could you check if that could be the issue on @ridestoke’s and @zomidaily’s sites (tickets 1989533 and 2019392)?

Thanks!

@jeherve The ticket of interest here is 2019392 where the issue with the Related Posts module running on PHP 7.1 was located.

Following several tests on the environment it was determined:

Jetpack with Related Posts activated + PHP 7.1 -> not working with OPcache disabled in xmlrpc.php.

Jetpack with Related Posts activated + PHP 7.1 -> frontend working with opcache.enable deactivated via a php.ini file. (backend not working)

Jetpack with Related Posts deactivated + PHP 7.1 -> working.

Jetpack with Related Posts activated + PHP 7.0 -> working.

This means that the xmlrpc.php file is not the one responsible for the failure.

As for ticket 1989533, the issue there was determined to be related to a shortcodes function in js_composer, which is called by the Shortcake (Shortcode UI) plugin.

It was creating a PHP memory leak resulting with:

Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 139976171884256 bytes) in /path/to/website/wp-content/plugins/js_composer/include/classes/shortcodes/shortcodes.php on line 31

Thanks a lot for all the details. We’ll run some tests on a test SiteGround site and see if we can get this fixed!

@everyone We’ve worked on a patch to solve this issue. If some of you feel comfortable editing PHP files on your site, could you try to apply this patch and let me know if it helps?
https://github.com/Automattic/jetpack/pull/6565/files

Thanks!

@jeherve – Thank you for your follow up, Jeremy!

The new patch for /jetpack/modules/related-posts/jetpack-related-posts.php is working beautifully on my end. None of the previously reported problems with Related Posts are occurring.

To be sure, I also tested it on an environment that the problem was previously observed on.

Hi Jeremy,
This patch seems to be be working. https://github.com/Automattic/jetpack/blob/7dda6c662df66854c0a787ca45213e75f43f9fb2/modules/related-posts/jetpack-related-posts.php

Is there any plan to release the new version soon?

Is there any plan to release the new version soon?

We’re about to enter the Beta period, and unless we find bugs, we will release a new version that will include this fix in the next couple of weeks!

Hi Jeremy,
Does the new version 4.8 include the fix?