Title: error_log Last modified: March 27, 2023 --- # error_log * Resolved [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/) * Hello support, Could you please take a look at these lines in our error_log: * [27-Mar-2023 08:34:07 UTC] WP_Optimize_Minify_Cache_Functions::cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/1679906047/ header” could not be created. [27-Mar-2023 08:34:07 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ 1679906047/header” could not be created.[27-Mar-2023 09:29:56 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ tmp” could not be created.[27-Mar-2023 09:30:06 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ 1679909406/header” could not be created.[27-Mar-2023 09:40:20 UTC] PHP Warning: chmod(): No such file or directory in /home/website/public_html/wp-content/plugins/ wp-optimize/minify/class-wp-optimize-minify-cache-functions.php on line 23[27- Mar-2023 09:40:41 UTC] WP_Optimize_Minify_Cache_Functions::cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/1679910041/assets” could not be created.[27-Mar-2023 09:40:41 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ 1679910041/header” could not be created.[27-Mar-2023 09:40:41 UTC] PHP Warning: rmdir(/home/website/public_html/wp-content/cache/wpo-minify/tmp): No such file or directory in /home/website/public_html/wp-content/plugins/wp-optimize/cache/ file-based-page-cache-functions.php on line 1126[27-Mar-2023 09:41:03 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ 1679910063/assets” could not be created.[27-Mar-2023 09:41:03 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ 1679910063/header” could not be created.[27-Mar-2023 09:41:03 UTC] PHP Warning: rmdir(/home/website/public_html/wp-content/cache/wpo-minify/tmp): No such file or directory in /home/website/public_html/wp-content/plugins/wp-optimize/cache/ file-based-page-cache-functions.php on line 1126[27-Mar-2023 09:45:37 UTC] WP_Optimize_Minify_Cache_Functions:: cache_path(): The folder “/home/website/public_html/wp-content/cache/wpo-minify/ tmp” could not be created. * There are more of them. Have you got any idea? * Thanks in advance. Viewing 14 replies - 1 through 14 (of 14 total) * Plugin Support [vupdraft](https://wordpress.org/support/users/vupdraft/) * (@vupdraft) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16599837) * Can you goto **Tools > Site Health** in your WordPress dashboard. To check your file permissions settings * To do this goto the  **Info** tab * Then, scroll down to the last section, which should be labeled **Filesystem Permissions** * Here you’ll see a list of crucial WordPress files, including the plugin and theme directories. Ideally, they should all be listed as “Writable”, is this the case for you? If not you will need to adjust the file permissions using this guide: [https://www.malcare.com/blog/wordpress-file-permissions/](https://www.malcare.com/blog/wordpress-file-permissions/) * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16599862) * Yes [@vupdraft](https://wordpress.org/support/users/vupdraft/) I have checked, they are all Writable. * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16601926) * I noticed, when I opened the page WP-Optimize > Cache, it started to Preload, exactly when I openend the page. Like it got triggered by me visiting that page in the Dashboard. * I have set the Minify > Advanced options > Lifetime old cache > 0 days. But I don’t think this could be the cause, why the cache folders could not be created. _0 days_ should not cause an error in the log right? * Plugin Support [vupdraft](https://wordpress.org/support/users/vupdraft/) * (@vupdraft) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16603074) * This shouldn’t be causing the warnings your are seeing. I have asked my colleague to check on this. * Plugin Contributor [Venkat Raj](https://wordpress.org/support/users/webulous/) * (@webulous) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16605547) * [@ms100](https://wordpress.org/support/users/ms100/) I understand that we already asked this, but make sure `wp-content/cache` folder is writable. If your site traffic is low and you set cache life span to 24 hours and cache preload schedule is same as cache life span, visiting your dashboard can trigger the preload process. Change `Minify > Advanced options > Lifetime old cache > ` to 1 days.What OS/ Server are you using? * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16606383) * Thanks for your help [@webulous](https://wordpress.org/support/users/webulous/) The wp-content/cache folder is writable.wp-content/cache/wpo-cache is writable. But within that folder, there are some files that have 0644 permission. For example: * [http://www.mydomain.nl](http://www.mydomain.nl) > 0755 .htaccess > 0644index. php > 0644 * When I open [http://www.mydomain.nl](http://www.mydomain.nl) folder, there are more [files with 0644](https://ibb.co/f0qx33Y): * index.html > 0644 index.html.gz > 0644index.php > 0644mobile.index.html > 0644mobile. index.html.gz > 0644 * We have a server cronjob that runs every 30 minutes. Preload is set to 10 hours. * I changed Minify > Advanced options > Lifetime old cache > to 1 days. (By the way, when I openend WP Optimize page(s), I noticed the cache Preloading started running again) * We have a LiteSpeed shared hosting server. * Plugin Contributor [Venkat Raj](https://wordpress.org/support/users/webulous/) * (@webulous) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16609148) * [@ms100](https://wordpress.org/support/users/ms100/) Preloading a large site is batch process. It will process a batch of URLs in 10 minutes interval. So, if you run cronjob at every 30 minutes, you’ll likely see it is processing whenever you visit site. Your server cronjob should run whenever the cache expires.Regarding the error log statements, do you have enough disk space? * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16609560) * [@webulous](https://wordpress.org/support/users/webulous/) What is the best server cronjob interval for the WP-Optimize plugin? Than I will change it accordingly. _Regarding the error log statements, do you have enough disk space?_Yes, we do have enough [disk space](https://ibb.co/jgWkKjn).Today the plugin gives a new [fatal error](https://ibb.co/yXSVMNB).Maybe the plugin is looking for gzip, but [maybe there is no gzip available](https://ibb.co/TRb1C0j) on our LiteSpeed server( because it uses brotli compression)? * ```wp-block-code Foutdetails Een fout van het type E_ERROR werd veroorzaakt op regelnummer 64 van het bestand /home/mydomain/public_html/wp-content/plugins/wp-optimize/includes/class-wp-optimize-gzip-compression.php. Foutmelding: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, WpOrg\Requests\Utility\CaseInsensitiveDictionary given in /home/mydomain/public_html/wp-content/plugins/wp-optimize/includes/class-wp-optimize-gzip-compression.php:64Stack trace: 0 /home/mydomain/public_html/wp-content/plugins/wp-optimize/includes/class-wp-optimize-gzip-compression.php(120): WP_Optimize_Gzip_Compression->get_headers_information() 1 /home/mydomain/public_html/wp-content/plugins/wp-optimize/includes/class-wp-optimize-admin.php(357): WP_Optimize_Gzip_Compression->is_gzip_compression_enabled() 2 /home/mydomain/public_html/wp-includes/class-wp-hook.php(308): WP_Optimize_Admin->output_cache_gzip_tab() 3 /home/mydomain/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() 4 /home/mydomain/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 5 /home/mydomain/public_html/wp-content/plugins/wp-optimize/includes/class-wp-optimize-admin.php(159): do_action() 6 /home/mydomain/public_html/wp-content/plugins/wp-optimize/includes/class-wp-optimize-admin.php(108): WP_Optimize_Admin->display_admin_page() 7 /home/mydomain/public_html/wp-includes/class-wp-hook.php(308): WP_Optimize_Admin->display_admin() 8 /home/mydomain/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() 9 /home/mydomain/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 10 /home/mydomain/public_html/wp-admin/admin.php(259): do_action() 11 {main} thrown ``` * Plugin Contributor [Venkat Raj](https://wordpress.org/support/users/webulous/) * (@webulous) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16612709) * [@ms100](https://wordpress.org/support/users/ms100/) > What is the best server cronjob interval for the WP-Optimize plugin?I think my choice of words are bad in my previous reply. It doesn’t matter how frequent your server cron run, it only executes WP cron jobs as per its schedule. If You scheduled your preload the same time as your cache expires, i.e. 10 hours as per your comment, then it will run once in 10 hours, even though you scheduled server cron to run once in every 30 minutes.So what you need to check is how large is your site and long does it take to complete preload. 2. Do your server has restrictions on number of files (even though it has space). I have seen such restrictions3. There is a compatibility issue with WP 6.2 which is fixed. Please update to 3.2.14 * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16613899) * [@webulous](https://wordpress.org/support/users/webulous/) Thanks for the clarification. I’m pretty sure the number of files should not be the cause of this issue (_public\ _html/wp-content/cache/wpo-minify/tmp” could not be created._) But I will do further investigation. * I can imagine most LiteSpeed server have the Litespeed Cache plugin installed. I don’t know how well the WPO plugin is tested on LiteSpeed servers. Could the Preload issue possibly have something to do with [this PHP timeout](https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/)? * Could it in any way be a (Brave) webbrowser related issue? I noticed the Brave Browser gives an [unexpected response message](https://ibb.co/K52RHLH) when running Preload. When refreshing the page, the preloading seems to continue. * The plugin update fixed the critical error. That is great! Thanks. * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16614198) * Using the Query Monitor plugin, I found [duplicate query’s](https://ibb.co/txk2zhw). Could that have anything to do with it? Thanks again [@webulous](https://wordpress.org/support/users/webulous/) * Plugin Contributor [Venkat Raj](https://wordpress.org/support/users/webulous/) * (@webulous) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16623668) * [@ms100](https://wordpress.org/support/users/ms100/) Since preload is a long running task, WP-Optimize attempts to close browser connection and run in the background. However some litespeed server configurations prevents the attempt to close browser connection which will result in `unexpected response received` However, large preloads will run in batches and as cron job. That is the reason you see continued preloading. May be you could try the **`Turn off Broken Connection Aborting`** section in the link you have mentioned.[https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/#turn-off-broken-connection-aborting](https://docs.litespeedtech.com/lsws/cp/cpanel/long-run-script/#turn-off-broken-connection-aborting) * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16636573) * Hello [@webulous](https://wordpress.org/support/users/webulous/) I was going to try ‘Turn off Broken Connection Aborting’, but then I found a new warning in the error_log: * [07-Apr-2023 13:31:39 UTC] PHP Warning: stat(): stat failed for /home/mydomain/ public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/wp- content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions.php on line 21 [07-Apr-2023 13:39:52 UTC] PHP Warning: stat(): stat failed for /home/ mydomain/public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/ wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions. php on line 21[07-Apr-2023 13:39:52 UTC] PHP Warning: stat(): stat failed for/ home/mydomain/public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/ wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions. php on line 32[07-Apr-2023 13:40:10 UTC] PHP Warning: stat(): stat failed for/ home/mydomain/public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/ wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions. php on line 21[07-Apr-2023 13:40:10 UTC] PHP Warning: stat(): stat failed for/ home/mydomain/public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/ wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions. php on line 32[07-Apr-2023 16:13:31 UTC] PHP Warning: stat(): stat failed for/ home/mydomain/public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/ wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions. php on line 21[07-Apr-2023 16:13:31 UTC] PHP Warning: stat(): stat failed for/ home/mydomain/public_html/wp-content/cache/wpo-minify/tmp in /home/mydomain/public_html/ wp-content/plugins/wp-optimize/minify/class-wp-optimize-minify-cache-functions. php on line 32 * Does this help you in understanding what is going on? * Thanks again for your support. * Thread Starter [ms100](https://wordpress.org/support/users/ms100/) * (@ms100) * [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16640098) * Hi [@webulous](https://wordpress.org/support/users/webulous/) I have deactivated the Minify function in the plugin. That seems to remove the issues. For now this is ok. Thanks a lot for your support. I will mark as resolved. Viewing 14 replies - 1 through 14 (of 14 total) The topic ‘error_log’ is closed to new replies. * ![](https://ps.w.org/wp-optimize/assets/icon-256x256.png?rev=1552899) * [WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance](https://wordpress.org/plugins/wp-optimize/) * [Frequently Asked Questions](https://wordpress.org/plugins/wp-optimize/#faq) * [Support Threads](https://wordpress.org/support/plugin/wp-optimize/) * [Active Topics](https://wordpress.org/support/plugin/wp-optimize/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wp-optimize/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wp-optimize/reviews/) * 14 replies * 3 participants * Last reply from: [ms100](https://wordpress.org/support/users/ms100/) * Last activity: [3 years, 1 month ago](https://wordpress.org/support/topic/error_log-22/#post-16640098) * Status: resolved