Possible memory leaks relating to Jetpack

  • Resolved atsballen

    (@atsballen)


    2 years, 9 months ago

    Hello, I woke up this morning to my apache server throwing a fit. After some investigation I realized that it kept running out of memory after only a couple of minutes of uptime.

    Here are some relevant lines from error.log:

    [Thu Jun 30 12:26:14.714918 2022] [php7:error] [pid 287280] [client 162.158.62.127:16832] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /var/www/whitehorseordering.com/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-backup/src/class-package-version.php on line 1, referer: https://whitehorseordering.com/wp-admin/
[Thu Jun 30 12:27:50.067369 2022] [php7:error] [pid 287595] [client 162.158.62.127:17898] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/whitehorseordering.com/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-my-jetpack/src/products/class-scan.php on line 218, referer: https://whitehorseordering.com/wp-admin/customize.php?return=%2Fwp-admin%2F
[Thu Jun 30 12:27:50.072628 2022] [php7:error] [pid 287595] [client 162.158.62.127:17898] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /var/www/whitehorseordering.com/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-backup/src/class-package-version.php on line 1, referer: https://whitehorseordering.com/wp-admin/customize.php?return=%2Fwp-admin%2F
[Thu Jun 30 12:28:40.779488 2022] [php7:error] [pid 287603] [client 162.158.62.127:18876] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /var/www/whitehorseordering.com/wp-content/plugins/elementor/core/app/modules/kit-library/data/kits/endpoints/favorites.php on line 50, referer: https://whitehorseordering.com/wp-admin/customize.php?return=%2Fwp-admin%2F
[Thu Jun 30 12:28:40.784669 2022] [php7:error] [pid 287603] [client 162.158.62.127:18876] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes) in /var/www/whitehorseordering.com/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-backup/src/class-package-version.php on line 1, referer: https://whitehorseordering.com/wp-admin/customize.php?return=%2Fwp-admin%2F

    Wordpress Version: 6.0
    Jetpack Version: 11.0

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hi there, @atsballen,

    Typically, errors like these are because of a lack of memory allocated to PHP on the site. You can read more about increasing the memory allocated to PHP, here:

    https://docs.woothemes.com/document/increasing-the-wordpress-memory-limit/

    You could also ask your host for assistance with this — they should be able to help if you need it.

    While I was checking on your site and Jetpack connection, I also noticed an issue, probably caused by some blocks at your server’s end.

    Can you reach out to your host and ask them if they have any blocks or limits on your XML-RPC.php file??

    It’s also worth checking whether any Jetpack IP addresses are blocked. The full IP range can be found at the bottom of this page:

    https://jetpack.com/support/hosting-faq/

    Hope that’s all clear! Let me know how you get on. Thanks!

    Thread Starter atsballen

    (@atsballen)

    @erania-pinnera Thanks for the response. I’m hosting this instance myself and don’t believe I have any blocks on that file. Are you having trouble accessing it? It’s also worth nothing that the Jetpack plugin is disable at the moment because of the crashing. The WordPress instance has 128MB of memory which should be enough for a site this lightweight. My other sites are all much more resource intensive than this one yet don’t crash. Jetpack also seems to be eating up said memory very fast.

    EDIT: After doing some reading on xmlrpc.php, it seems like an archaic method of interfacing with WordPress and most resources recommend it be disabled. The documentation you linked states that xmlrpc.php support is required, and while I don’t know enough about the inner-workings of WordPress to decide whether or not enabling xmlrpc.php is a wise decision, I’m also skeptical that it’s causing memory leaks. I’d imagine that in the event a required setting wasn’t enable, Jetpack would throw me a warning/error instead of crashing my apache instance.

    • This reply was modified 2 years, 9 months ago by atsballen.

    Hi @atsballen

    I checked the file xmlrpc.php and it is not blocked, but our debug shows that your site is not connecting with Jetpack correctly, as you can see at https://jptools.wordpress.com/debug/?url=https://whitehorseordering.com.

    I see that your site is behind Cloudflare (a CDN and DDoS protection service), which may be contributing to this issue.

    Could you please try pausing Cloudflare as described [here](https://support.cloudflare.com/hc/en-us/articles/203118044#h_8654c523-e31e-4f40-a3c7-0674336a2753), please?

    The steps [here](https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/) will help to ensure that your site is optimized to work well with Cloudflare.

    Let me know if you have any questions.

    My best regards,

    Michelle

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Possible memory leaks relating to Jetpack’ is closed to new replies.