Moving this issue #1942230-10: CDN module AdvAgg 7.x-2.x Integration to here.

CommentFileSizeAuthor
#1 advagg-2078049-1-increase-timeout.patch706 bytesmikeytown2
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Active » Fixed
FileSize
advagg-2078049-1-increase-timeout.patch706 bytes

Following patch has been committed. It will increase all HTTPRL timeouts to be at least 12 seconds.

@jhinxed
Let me know if this doesn't fix the issue you're seeing.

jhinxed’s picture

jhinxed CreditAttribution: jhinxed commented

Hi @mikeytown2,

Thanks for the response. I've updated to the recent module version 7.x-2.0-rc3, which also has the above patch.

Right now though, If I enable the patch for CDN, the site shows WSOD (White Screen of Death)

I had to remove the CDN patch so it went back to being okay. But then, it says now that I need the patch for CDN.

Any ideas?

jhinxed’s picture

jhinxed CreditAttribution: jhinxed commented

@mikeytown2 I'm using the new update rc3 on the site coupled with the patch for cdn.

Here's what I'm getting:

Adv CSS/JS Agg - HTTP Request	HTTP requests to advagg for css files are not getting through.
AdvAgg will issue a request for a file that does not exist inside of the AdvAgg directory. If AdvAgg sends a 404, everything is ok; if something else sends a 404 then that means that AdvAgg will not be able to generate an aggregate if it is missing as something else is handling the 404 before AdvAgg has a chance to do it. If you are reading this, it means that something else is handling the 404 before AdvAgg can. Raw request info:

stdClass Object
(
    [code] => -110
    [error] => Connection timed out
)

Any ideas how to fix?

jhinxed’s picture

jhinxed CreditAttribution: jhinxed commented
Status: Fixed » Needs work
mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

What this is saying is that the server can't connect to it's self. 12 seconds in order to make a connection to it's self should be more than enough time.

An error like this might mean that you webserver is only accepting 1 connection at a time. See if you can increase the number of connections that the server can handle. Also check that you don't have extremely low rate limiting.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Issue summary: View changes
Status: Needs work » Closed (cannot reproduce)

Can't repo. If you want to know why this I can't program around this to make it work read this: https://drupal.org/comment/8177131#comment-8177131