Title: Getting some fatal errors
Last modified: April 16, 2018

---

# Getting some fatal errors

 *  [byomes](https://wordpress.org/support/users/byomes/)
 * (@byomes)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/getting-some-fatal-errors/)
 * Debugging mode shows the following error. I’m not sure how to troubleshoot. Cache
   won’t clear and I currently can’t make any copy updates to the site. Plugin +
   theme updates work fine, but cannot deactivate or modify plugins.
 * Warning: rename(/home/site/wwwroot/wp-content/cache/comet-cache/cache,/home/site/
   wwwroot/wp-content/cache/comet-cache/cache-5ad432a1dfda3788424861-tmp): Permission
   denied in /home/site/wwwroot/wp-content/plugins/comet-cache-pro/src/includes/
   traits/Shared/CacheDirUtils.php on line 157
 * Fatal error: Uncaught Exception: Unable to delete files. Rename failure on directory:`/
   home/site/wwwroot/wp-content/cache/comet-cache/cache`. in /home/site/wwwroot/
   wp-content/plugins/comet-cache-pro/src/includes/traits/Shared/CacheDirUtils.php:
   158
    Stack trace: #0 /home/site/wwwroot/wp-content/plugins/comet-cache-pro/src/
   includes/traits/Shared/CacheDirUtils.php(276): WebSharks\CometCache\Pro\Classes\
   AbsBaseAp->deleteFilesFromCacheDir(‘/^.+/ui’, false) #1 /home/site/wwwroot/wp-
   content/plugins/comet-cache-pro/src/includes/traits/Shared/CacheDirUtils.php(
   61): WebSharks\CometCache\Pro\Classes\AbsBaseAp->deleteFilesFromHostCacheDir(‘/
   ^.+/ui’) #2 /home/site/wwwroot/wp-content/plugins/comet-cache-pro/src/includes/
   traits/Plugin/WcpUtils.php(95): WebSharks\CometCache\Pro\Classes\AbsBaseAp->clearFilesFromHostCacheDir(‘/
   ^.+/ui’) #3 /home/site/wwwroot/wp-content/plugins/comet-cache-pro/src/includes/
   traits/Plugin/WcpUtils.php(275): WebSharks\CometCache\Pro\Classes\Plugin->clearCache()#
   4 /home/site/wwwroot/wp-content/plugins/comet-cac in /home/site/wwwroot/wp-content/
   plugins/comet-cache-pro/src/includes/traits/Shared/CacheDirUtils.php on line 
   158
    -  This topic was modified 8 years, 1 month ago by [byomes](https://wordpress.org/support/users/byomes/).
      Reason: additional info
    -  This topic was modified 8 years, 1 month ago by [byomes](https://wordpress.org/support/users/byomes/).
      Reason: additional info
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fgetting-some-fatal-errors%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/getting-some-fatal-errors/#post-10185788)
 * Hey [@byomes](https://wordpress.org/support/users/byomes/),
 * It sounds like Comet Cache is either having permissions issues performing the
   necessary cache cleanup, or your web hosting company is using a Network File 
   System (NFS) that doesn’t play nicely with atomic reads/writes.
 * We have seen this issue in the past and it has always ended up being related 
   to the hosting environment. Can you check with your hosting company to see if
   they have any ideas?
 *  Thread Starter [byomes](https://wordpress.org/support/users/byomes/)
 * (@byomes)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/getting-some-fatal-errors/#post-10186213)
 * Hi Raam,
 * That is strange. We have been using Azure to host WP for couple months now, and
   this is the first time running into this problem. I’m looking at Azure right 
   now and there doesn’t seem to be a noticeable problem. Do you know where I should
   be exactly poking around in Azure?
 *  Thread Starter [byomes](https://wordpress.org/support/users/byomes/)
 * (@byomes)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/getting-some-fatal-errors/#post-10188485)
 * Getting a new error similar to the one I posted before. I still do not know how
   to diagnose the problem. Wish to fix quickly as this problem is preventing updates
   to the site which is hindering the business.
 * [17-Apr-2018 04:31:05 UTC] PHP Warning: rename(/home/site/wwwroot/wp-content/
   cache/comet-cache/cache/https/www-sojospaclub-com/index.html-5ad578898e992184414454-
   tmp,/home/site/wwwroot/wp-content/cache/comet-cache/cache/https/www-sojospaclub-
   com/index.html): No such file or directory in /home/site/wwwroot/wp-content/plugins/
   comet-cache-pro/src/includes/traits/Ac/ObUtils.php on line 452
 * [17-Apr-2018 04:31:05 UTC] PHP Fatal error: Uncaught Exception: Comet Cache: 
   failed to write cache file for: `/`; possible permissions issue (or race condition),
   please check your cache directory: `/home/site/wwwroot/wp-content/cache/comet-
   cache/cache`. in /home/site/wwwroot/wp-content/plugins/comet-cache-pro/src/includes/
   traits/Ac/ObUtils.php:457
    Stack trace: #0 [internal function]: WebSharks\CometCache\
   Pro\Classes\AdvancedCache->outputBufferCallbackHandler(‘<!DOCTYPE html>…’, 9)#
   1 /home/site/wwwroot/wp-includes/functions.php(3729): ob_end_flush() #2 /home/
   site/wwwroot/wp-includes/class-wp-hook.php(286): wp_ob_end_flush_all(”) #3 /home/
   site/wwwroot/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL,
   Array) #4 /home/site/wwwroot/wp-includes/plugin.php(453): WP_Hook->do_action(
   Array) #5 /home/site/wwwroot/wp-includes/load.php(679): do_action(‘shutdown’)#
   6 [internal function]: shutdown_action_hook() #7 {main} thrown in /home/site/
   wwwroot/wp-content/plugins/comet-cache-pro/src/includes/traits/Ac/ObUtils.php
   on line 457
    -  This reply was modified 8 years, 1 month ago by [byomes](https://wordpress.org/support/users/byomes/).
 *  [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * (@raamdev)
 * [8 years, 1 month ago](https://wordpress.org/support/topic/getting-some-fatal-errors/#post-10209862)
 * [@byomes](https://wordpress.org/support/users/byomes/) Comet Cache is a WordPress
   plugin written in PHP and it uses the standard PHP functions to perform filesystem
   operations. These errors are indicating that PHP is having trouble writing and
   renaming files on the filesystem, which indicates a filesystem-level or Operating
   System-level issue.
 * I’ve created a GitHub issue so that we can look into improving the error handling
   on Comet Cache’s side so that we can at least prevent a fatal error from being
   produced: [https://github.com/websharks/comet-cache/issues/927](https://github.com/websharks/comet-cache/issues/927)

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Getting some fatal errors’ is closed to new replies.

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

 * 4 replies
 * 2 participants
 * Last reply from: [Raam Dev](https://wordpress.org/support/users/raamdev/)
 * Last activity: [8 years, 1 month ago](https://wordpress.org/support/topic/getting-some-fatal-errors/#post-10209862)
 * Status: not resolved