Title: After PHP Upgrade – PHP Fatal error
Last modified: August 31, 2016

---

# After PHP Upgrade – PHP Fatal error

 *  [Theunknown1](https://wordpress.org/support/users/deexgnome/)
 * (@deexgnome)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/after-php-upgrade-php-fatal-error/)
 * Hi, i did today a Upgrade to a newer PHP5 Version,
 * since the upgrade i become the error message
 * `2016/01/26 13:29:59 [error] 19432#19432: *9546 FastCGI sent in stderr: "PHP 
   message: PHP Fatal error: Class 'Memcache' not found in /var/www/clients/client1/
   web12/wow/assets/plugins/w3-total-cache/lib/W3/Cache/Memcached.php on line 38"
   while reading response header from upstream, client:...`
 * I checked if Memcache is installed and running, all seems to be normal.
 * [https://wordpress.org/plugins/w3-total-cache/](https://wordpress.org/plugins/w3-total-cache/)

Viewing 1 replies (of 1 total)

 *  Thread Starter [Theunknown1](https://wordpress.org/support/users/deexgnome/)
 * (@deexgnome)
 * [10 years, 4 months ago](https://wordpress.org/support/topic/after-php-upgrade-php-fatal-error/#post-6989356)
 * Okay likely a issue with the Update of PHP..

Viewing 1 replies (of 1 total)

The topic ‘After PHP Upgrade – PHP Fatal error’ is closed to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [Theunknown1](https://wordpress.org/support/users/deexgnome/)
 * Last activity: [10 years, 4 months ago](https://wordpress.org/support/topic/after-php-upgrade-php-fatal-error/#post-6989356)
 * Status: not resolved