Jetpack 10.5 Throws Error – failed to open stream: No such file or directory

Hi,

The same thing has just happened to my site. I have restored a backup copy and will be eager to see how to fix this issue as well

• This reply was modified 3 years, 1 month ago by aliree. Reason: forgot to tick email updates

Same here, every single install is throwing critical errors on this update. Worse still it is one of those plugins that notify the user (my clients) to update from the dashboard, which then means I have to spend my time fixing it up.

rolling back / reversing to 10.4 did not fix the issue either.

Howdy y’all!

I’m sorry for the trouble. We have seen that _during the upgrade_ to 10.5, this error is being thrown.

Without going into too much detail, basically, WordPress updates Jetpack and during that same bit of work, it tries to call something from the older version of Jetpack, so it errors out.

What we’ve seen is besides this fatal error when the upgrade is happening (just after it actually happens), everything is working fine.

In a sense, a hiccup that is unacceptably noisy and annoying, but only a hiccup.

Are y’all seeing something different than that? Is this fatal persisting on your site beyond the upgrade itself?

To be clear, the fact that this is happening at all does not meet our standards for the project or myself personally, but I want to be sure that we’re seeing the same thing y’all are and not indicative of a larger issue.

Thank you!

Hi Brandon, Thanks for getting back to us. So You are saying it is okay to receive this “hiccup” and we should upgrade to this version of Jetpack?

Is this error being fixed in a future version where it does not want to call on an older version as you mention? I rather wait for that version to be honest here.

I am going to wait until the next update which will hopefully rectify this issue. Every time the error throws, it notifies my clients, then I have to deal with that stuff as well.

Hi there

So You are saying it is okay to receive this “hiccup” and we should upgrade to this version of Jetpack?

Yes, although you will see the error in your dashboard and your error logs, it shouldn’t cause any actual issues on your site, and once you refresh you should no longer see the error (although it will remain in your error logs).

If you’re still seeing the error occurring after the update is complete, please let us know.

If you prefer to wait for the next update, we will ensure that it does not cause this error.

Brandon, Dan, I tried updating this past weekend and got an email regarding the fatal error, times two for two different sites. On a third site, all seems to work fine. If it matters, both are running suffusion, and I had updated both sites to wp 5.8.3 before updating any plugins. The following are samples of two different types of warnings trying to login(unsuccessfully) to both sites.

Warning: “continue” targeting switch is equivalent to “break”. Did you mean to use “continue 2”? in /nfs/c06/h01/mnt/154861/domains/interns.athensown.net/html/wp-content/themes/suffusion/functions/media.php on line 666

Warning: Cannot modify header information – headers already sent by (output started at /nfs/c06/h01/mnt/154861/domains/interns.athensown.net/html/wp-content/themes/suffusion/functions/media.php:666) in /nfs/c06/h01/mnt/154861/domains/interns.athensown.net/html/wp-login.php on line 400

The following email notification was received soon thereafter; unfortunately I did not respond in time and the recovery link has expired.

Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Jetpack.

First, visit your website (https://athensown.biz/) and check for any visible issues. Next, visit the page where the error was caught (https://athensown.biz/wp-admin/update.php?action=update-selected&plugins=antispam-bee%2Fantispam_bee.php%2Cbbpress%2Fbbpress.php%2Cconnections%2Fconnections.php%2Cformidable%2Fformidable.php%2Cjetpack%2Fjetpack.php%2Cmembers%2Fmembers.php%2Cwoocommerce-delivery-notes%2Fwoocommerce-delivery-notes.php%2Creally-simple-ssl%2Frlrsssl-really-simple-ssl.php%2Csoliloquy-lite%2Fsoliloquy-lite.php%2Csubscribe-to-comments-reloaded%2Fsubscribe-to-comments-reloaded.php&_wpnonce=a7f5925001) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

https://athensown.biz/wp-login.php?action=enter_recovery_mode&rm_token=RPpZmH07jiYEQ1sanBfByY&rm_key=Odnp49qwvp094yhPhcAkS9

To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 5.8.3
Current theme: SuffusionChild (version )
Current plugin: Jetpack (version 10.5)
PHP version 7.3.11

Error Details
=============
An error of type E_COMPILE_ERROR was caused in line 30 of the file /nfs/c06/h01/mnt/154861/domains/athensown.biz/html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/autoload_functions.php. Error message: require_once(): Failed opening required ‘/nfs/c06/h01/mnt/154861/domains/athensown.biz/html/wp-content/plugins/jetpack/vendor/automattic/jetpack-roles/src/class-roles.php’ (include_path=’.:/usr/local/php-7.3.11/share/pear’)

Thanks, Constantine

• This reply was modified 3 years, 1 month ago by athensown.

@athensown Thanks so much for the info!

If anyone continues to see the error, please let us know, but it should completely clear after the first time it happens, and it will not be present in future updates.