Error log full full of jetpack errors

  • Resolved jacf182

    (@jacf182)


    3 years, 7 months ago

    My disk had a big log file that had been accumulated for several weeks and my site was inaccessible. I had to ask my host support to truncate the log file in order to be able to use the site again.

    Here’s a view of what the log file says:

    [Thu Jul 29 09:23:27.639187 2021] [fcgid:warn] [pid 25470:tid 140339390179072] [client 114.119.154.13:55670] mod_fcgid: stderr: PHP Fatal error:  Uncaught Error: Class 'Automattic\\Jetpack\\Sync\\Modules\\Module' not found in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/modules/class-callables.php:18
[Thu Jul 29 09:23:27.639232 2021] [fcgid:warn] [pid 25470:tid 140339390179072] [client 114.119.154.13:55670] mod_fcgid: stderr: Stack trace:
[Thu Jul 29 09:23:27.639236 2021] [fcgid:warn] [pid 25470:tid 140339390179072] [client 114.119.154.13:55670] mod_fcgid: stderr: #0 {main}
[Thu Jul 29 09:23:27.639241 2021] [fcgid:warn] [pid 25470:tid 140339390179072] [client 114.119.154.13:55670] mod_fcgid: stderr:   thrown in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/modules/class-callables.php on line 18
[Thu Jul 29 09:28:47.666168 2021] [fcgid:warn] [pid 17308:tid 140340161914624] [client 114.119.154.128:4394] mod_fcgid: stderr: PHP Warning:  require_once(/home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/mu-plugins/keyring/keyring.php): failed to open stream: No such file or directory in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/modules/publicize.php on line 47
[Thu Jul 29 09:28:47.666220 2021] [fcgid:warn] [pid 17308:tid 140340161914624] [client 114.119.154.128:4394] mod_fcgid: stderr: PHP Fatal error:  require_once(): Failed opening required '/home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/mu-plugins/keyring/keyring.php' (include_path='.:') in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/modules/publicize.php on line 47
[Thu Jul 29 09:45:57.987131 2021] [fcgid:warn] [pid 25470:tid 140339365000960] [client 114.119.131.116:12030] mod_fcgid: stderr: PHP Fatal error:  Uncaught Error: Class 'WPCOM_JSON_API_Update_Post_v1_2_Endpoint' not found in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/json-endpoints/class.wpcom-json-api-update-post-v1-2-endpoint.php:3
[Thu Jul 29 09:45:57.987184 2021] [fcgid:warn] [pid 25470:tid 140339365000960] [client 114.119.131.116:12030] mod_fcgid: stderr: Stack trace:
[Thu Jul 29 09:45:57.987188 2021] [fcgid:warn] [pid 25470:tid 140339365000960] [client 114.119.131.116:12030] mod_fcgid: stderr: #0 {main}
[Thu Jul 29 09:45:57.987191 2021] [fcgid:warn] [pid 25470:tid 140339365000960] [client 114.119.131.116:12030] mod_fcgid: stderr:   thrown in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/json-endpoints/class.wpcom-json-api-update-post-v1-2-endpoint.php on line 3
[Thu Jul 29 10:33:13.629916 2021] [fcgid:warn] [pid 25470:tid 140340284921600] [client 114.119.154.181:58856] mod_fcgid: stderr: PHP Fatal error:  Uncaught Error: Call to undefined function add_action() in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/3rd-party/bbpress.php:8
[Thu Jul 29 10:33:13.629961 2021] [fcgid:warn] [pid 25470:tid 140340284921600] [client 114.119.154.181:58856] mod_fcgid: stderr: Stack trace:
[Thu Jul 29 10:33:13.629966 2021] [fcgid:warn] [pid 25470:tid 140340284921600] [client 114.119.154.181:58856] mod_fcgid: stderr: #0 {main}
[Thu Jul 29 10:33:13.629970 2021] [fcgid:warn] [pid 25470:tid 140340284921600] [client 114.119.154.181:58856] mod_fcgid: stderr:   thrown in /home/uesma/uesma.edu.ec/wp-content/plugins/jetpack/3rd-party/bbpress.php on line 8
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support MadHatter (a11n)

    (@madhattersez)

    Hello, there.

    Happy to hear your host was able to get the site up and running again!

    As far as those errors go, have they since stopped?

    Regardless, I would recommend making sure that all of your plugins, theme, PHP version, and core of WordPress are all updated just in case this was some sort of conflict between Jetpack and another plugin or feature of your site during an update.

    Anonymous User 18700194

    (@anonymized-18700194)

    Hi there,

    It has been more than one week since we have heard from you, so I’m marking this topic as resolved.

    But If you have any further questions or need some more help, you’re welcome to reply here or open another thread.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Error log full full of jetpack errors’ is closed to new replies.

Tags