Closed futtta closed 6 years ago
But all 3 are "NO_RESPONSE", not "NO_CSS". When would that happen @denydias ?
(got a big-ass queue.log file which I can provide if needed)
Do not copy that... NO_RESPONSE is a service disruption. NO_CSS is another thing...
service disruption at criticalcss.com's?
Yep. WP tried a connection and reached a closed door (or something like that). This could happen in the better and stable families...
OK, we'll ignore those in that case :)
On Thu, Apr 19, 2018 at 9:22 AM, Deny Dias notifications@github.com wrote:
Yep. WP tried a connection and reached a closed door (or something like that). This could happen in the better and stable families...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/futtta/ao_critcss_aas/issues/27#issuecomment-382636642, or mute the thread https://github.com/notifications/unsubscribe-auth/AALEMVRmUgBXdieAMkVqC2fINvwrbsK9ks5tqDsggaJpZM4TWMx_ .
You should! You can't ged rid of every single E. There are so many circumstances where a job just can't complete in a good manner.
You see all three E are close in time. Probably some quick maintenance on their side, or a network problem on your side, or their side, a machine reboot, a huge DDoS attack going on at Karkumenistan which routed traffic on ccss.com provider for a couple minutes... who knows! :P
no for something weird; I don't seem to get "no_css" any more, did you already implement some fix @denydias or is this coincidence?
closing, no more NO_CSS to be seen.
To be looked into after finsishing queue cleanup, for now just a reminder ;-)