I get tons of accesses in Apache logs like this one:

87.98.176.200 - - [19/Dec/2012:22:51:09 +0100] "GET /sites/see.shareontheweb.com/files/advagg_js/js_f40a872b0b9245e5791ca54500538f16_0.js?generator=1&redirect_counter=0 HTTP/1.0" 302 - "-" "Drupal (+http://drupal.org/)"

They ultimately break the server by lack of memory. (I ust changed some Apache settings to avoid this)

I recently switched the whole site to ssl, I don't know if it is related.

Any idea?
Thanks for help

Comments

jvieille’s picture

Every 2 hours, the server is bombed by thousands of these queries - actually about 800/sec
Apache serves up to 100 processes from a 2-3 normally, Mysql goes to 100 threads, CPU from 0.5 to 5% and app memory from 2 to 8 GB

I finally managed to keep the server alive, but something needs to be fixed.

jbizzay’s picture

Priority: Normal » Major

I am seeing this now as well, drupal logs show tons of page not found errors for the same type of js/css calls:

sites/default/files/advagg_js/js_25632e46611907a3506c65e15df3d516_13.js?generator=1&redirect_counter=0

Any clues on what should be done to fix this? I'll be digging into this right away, because it causes my server load to skyrocket (have seen it close to 100)

jvieille’s picture

I ended up disabling advagg.
Performance boosted on the spot.
I thing advagg is to be used in specific cases, when needed. Otherwise, better to abstain.

jbizzay’s picture

Thanks for advising jvielle, but I think I may have found a clue. Running this query:

select * from menu_router where page_callback = 'advagg_missing_css';

returned a path of advagg_css/% . This doesn't match up with the above urls. Flushing the menu cache through drupal admin and drush. set the path entry to sites/default/files/advagg_css/% . Now lo and behold all is working as it should and I'm not seeing those errors. I just can't figure out what would cause it to be set without the sites/default/files part. I may end up just setting a custom path to make sure it doesn't go screwy again.

mikeytown2’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

Sounds similar to an issue and fix I put in the D7 branch. I'm marking this as won't fix as in I'm not going to work on backporting the patch. If someone wants to create a patch I will commit it. #2464153: Don't serve a 404 even if the menu router fails.