Jetpack update fatal memory error – workaround

When trying to update Jetpack to 3.5 on WordPress 4.2, I got a fatal memory error on all of my sites, using both the Genesis framework plus child theme and one site using the standard twentyfourteen theme. I tried disabling all plugins, still no success. I made the php_value memory_limit 256M in htaccess and setting max memory in wp_config. No joy. The problem seems to be in the new update process in WP not working with my server. Dedicated server, BSD Unix. These problems are new with this update.

Previously, when going to the update button in the admin section, you could select what you wanted to update and WP would handle maintenance mode and deactivation, installation and reactivation. Now it just throws the error. Updating WP worked fine.

I installed a maintenance mode plugin, then manually put the site in maintenance mode, go to the plugin page and manually deactivate the plugin, then update from the plugin page. Reactivate and Success! Worked on all of my sites. I also noted, updating other plugins took far longer if you don’t manually deactivate, but deactivating first makes it much faster.

Hope this helps anyone running into this.