Cronjobs status messages
-
I’ve managed to setup everything (Warm Cache and WP Rocket), but the first few hits (and occasionally some others) of the Cronjob to the address that warm up the cache resulted in this (log is sent to me by email):
--2016-03-12 22:30:01-- https://website.com/?warm_cache=DaSdAsSad Resolving website.com (website.com)... 208.113.173.211 Connecting to website.com (website.com)|208.113.173.211|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2016-03-12 22:30:20 ERROR 500: Internal Server Error.
Then one of the hits resulted in:
--2016-03-12 23:00:01-- https://website.com/?warm_cache=DaSdAsSad Resolving website.com (website.com)... 208.113.173.211 Connecting to website.com (website.com)|208.113.173.211|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 5803 (5.7K) [text/html] Saving to: index.html?warm_cache=DaSdAsSad' 0K ..... 100% 43.4M=0s 2016-03-12 23:00:09 (43.4 MB/s) - 'index.html?warm_cache=DaSdAsSad' saved [5803/5803]
Then all the subsequent resulted in:
--2016-03-12 23:30:01-- https://website.com/?warm_cache=DaSdAsSad Resolving website.com (website.com)... 208.113.173.211 Connecting to website.com (website.com)|208.113.173.211|:443... connected. HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable The file is already fully retrieved; nothing to do.
And despite everything, the Warm Cache logs in WordPress seems to report that everything was cached correctly, although 03 from 17 times the cache has been crawled it resulted in 0 pages being cached.
Is all that behavior normal? I’ve never been thru this kind of setup.
PS1: I’ve setup a preload so frequent (every 30 minutes) just for tests.
PS2: For security reasons I’ve changed the real URL, IP and Token in this post.
- The topic ‘Cronjobs status messages’ is closed to new replies.