• 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.

    https://www.ads-software.com/plugins/warm-cache/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter prccp

    (@prccp)

    So I changed the command for the cron job from:

    wget "https://website.com/?warm_cache=DaSdAsSad"

    To:

    wget -O - "https://website.com/?warm_cache=DaSdAsSad" >/dev/null

    Now I can see all e-mails resulting in:

    --2016-03-14 10:00:01--  https://website.com/?warm_cache=DaSdAsSad
    Resolving website.com (website.com)... 666.666.666.666
    Connecting to website.com (website.com)|666.666.666.666|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 12348 (12K) [text/html]
    Saving to:
    
    STDOUT'
    
        0K .......... ..                                         100% 36.6M=0s
    
    2016-03-14 10:00:15 (36.6 MB/s) - written to stdout [12348/12348]

    And some results in:

    --2016-03-14 05:30:01--  https://website.com/?warm_cache=DaSdAsSad
    Resolving website.com (website.com)... 666.666.666.666
    Connecting to website.com (website.com)|666.666.666.666 |:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 123 [text/html]
    Saving to:
    
    STDOUT'
    
        0K                                                       100% 6.98M=0s
    
    2016-03-14 05:30:12 (6.98 MB/s) - written to stdout [123/123]

    I guess that explains why the “416 errors”, since sometimes the file doesn’t seem to be fully “transferred”.

    Still, if anyone could explain to me all this behavior, I would appreciate very much.

    Plugin Author ramon fincken

    (@ramon-fincken)

    416 errors are new to me, have you asked your host?

    Plugin Author ramon fincken

    (@ramon-fincken)

    Hi prccp any word from your host about this?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cronjobs status messages’ is closed to new replies.