I had a staging site working with AdvAgg turned on. Async mode was working. I ran a verify, clone site (to www.website.com on the same platform) and verify again and after status report, I get the following errors for AdvAgg.

On Status Report I'm getting the familiar:

Adv CSS/JS Agg - Asynchronous Mode Set to FALSE.
Check to see if you have fast 404s, if so create an exception for this module. The readme file explains what needs to be changed. You can try flushing the menu cache as well. If you are still having issues you can go to the AdvAgg information tab and select Asynchronous debug info. If creating an issue on d.o be sure to include this information .
Adv CSS/JS Agg - Socket Timeout Already set to 1 seconds. Raw timer: 108.8
AdvAgg JS Compress - Callback The callback for testing if a JS file is compressible is not working.
As a result if jsmin+ encounters a file that it cannot compress, it will kill that PHP process.

I have made sure Optimize CSS and Javascript are turned off in admin/settings/performance/default

I didn't have Fast 404 installed and I got this error. I tried also flushing menu cache (and just about every other cache to try and make it go away. I have attached the Asynchronous debug info also.

IP Address to send all asynchronous requests is set to: -1

I thought this might be a BOA issue as I did have it working on pressflow-6.22-prod until Clone task was run. If you feel its an AdvAgg issue I will move it to that project.

Do you know why this could be happening? Should I have disabled Advagg modules before clone then reenabled them after clone?

Thanks for your help!

CommentFileSizeAuthor
advagg_error_1.txt1.04 KBtribe_of_dan
octopus_log.txt671 bytestribe_of_dan
barracuda_log.txt1.15 KBtribe_of_dan
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented 
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /sites/www.website.com /files/advagg_css/css_missing11304542531321059622_0.css was not found on this server.</p>
<p>Additionally, a 404 Not Found
error was encountered while trying to use an ErrorDocument to handle the request.</p>
</body></html>

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Seems like Drupal is not handling 404's. If you created an exception of imagecache do the same for advagg.

tribe_of_dan’s picture

tribe_of_dan CreditAttribution: tribe_of_dan commented

Hi Mikeytown2, thanks for the quick reply!

I haven't done any exceptions before for imagecache. Could it be that I was using Search404 module in the past before perhaps? I did have search404 disabled before cloning the site and AdvAgg was working before.

After seeing this issue, I even tried installing Fast404 and adding the code to settings.php but async was still set to FALSE. Information page also shows a missing css file date_picker.css (which upon a search of d.o is a common issue for Date module). Could this missing file be involved? Thanks for your help.

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented
Status: Active » Postponed (maintainer needs more info)

BOA has built-in support for AdvAgg and "Fast404" in Nginx, so you shouldn't add anything to the settings.php file.

You should disable, uninstall *and* remove Search404 module - it causes more problems than resolves.

It is rather weird, as cloning or renaming the site in Aegir doesn't affect anything AdvAgg related.

Is this site hosted on the extra IP on this server with local proxy, as explained in the SSL how-to maybe?

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

I just checked this in a few sites using latest AdvAgg with correct config and latest, standard BOA config and it just works, so I'm going to close this as 'cannot reproduce'. Feel free to reopen if you will find more details related to your specific issue.

tribe_of_dan’s picture

tribe_of_dan CreditAttribution: tribe_of_dan commented

Got it working!

I did as you said and completely uninstalled search404 and deleted the directory and re-verified and it went away. They were both hosted on the same IP (yes the extra one).

When I add fast404 to the mix the error comes back. I will continue to troubleshoot for that but this is good now thanks.

tribe_of_dan’s picture

tribe_of_dan CreditAttribution: tribe_of_dan commented

Hi Mikeytown2,

I did get async to work but now I'd love to get Fast404 working with it. When I enable Fast404 module, I get this error again. I've completely removed search404 module and can't figure out why this couldn't be working.

I've check that I have the required Nginx support code in my configuration (nginx_advanced_include.conf in BOA). Could you please give me any insight into where I should start looking to troubleshoot this? Thanks.

omega8cc’s picture

omega8cc CreditAttribution: omega8cc commented

What you mean by "fast404 module"? I don't see anything like that on d.o

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

http://drupal.org/project/fast_404
#1166622: AdvAgg, Fast 404: Support for AdvAgg
The patch for this is fairly easy to do

tribe_of_dan’s picture

tribe_of_dan CreditAttribution: tribe_of_dan commented

I can see where I was getting confused here.

So technically there are two fast 404s? 1. your method as in readme, and 2. a seperate module.

I had assumed when I saw Fast 404 in the readme, that you were referring to the module and that the 2bits article was how to get Fast 404 module working with AdvAgg.

As @omega8cc says "BOA has built-in support for AdvAgg and "Fast404" in Nginx" so I'll just remove the fast404 module and I should be fine yes?

Thanks for clearing this up.