Closed (fixed)
Project:
CDN
Version:
7.x-2.x-dev
Component:
Module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jan 2012 at 13:06 UTC
Updated:
3 Mar 2012 at 19:20 UTC
Jump to comment: Most recent file
I'm getting this error in my blog pages. I think it's new, though I'm not sure. How can I debug this? Or does anyone know why it's happening?
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 1421282-5.patch | 900 bytes | wim leers |
| #3 | 1421282-3-no-cache-during-file-creation-D6.patch | 781 bytes | mr.baileys |
| #2 | 1421282-2-no-cache-during-file-creation.patch | 844 bytes | mr.baileys |
| #1 | 1421282-no-cache-during-file-creation.patch | 787 bytes | mr.baileys |
Comments
Comment #1
mr.baileysWe are seeing similar behavior on one of our sites, albeit on a D7 site and only with Image Style derivatives. We changed some of the image style definitions, which caused the pre-generated (obsolete) images to be removed. The new versions of images for these image styles are not being generated, and the CDN links all contain "/cdn/farfuture/mtime:/*" (note the empty mtime UFI) .
The site is behind a reverse proxy (Squid), and CDN uses drupal_http_request() to trigger recreation of the images. While the drupal_http_request is successful, it is actually ending up with a cached version of the file. Here's an example:
This means that the file is not actually created and CDN cannot get a filemtime, resulting in a warning and an empty mtime UFI.
We are currently testing with the patch attached (against 7.x-dev) to try and avoid getting a cached item. I'll provide feedback once I know whether or not this works.
Comment #2
mr.baileysPrevious patch was mixing D6- and D7-style drupal_http_request parameters...
Comment #3
mr.baileysPatch in #2 resolved our issues, here is a D6 version of the patch (contrary to the D7 patch, this one is untested).
Comment #4
wim leers#1415448: HTTP Error 503 Service unavailable merged into this one.
Comment #5
wim leersWith minor changes (comment wrapped at col 80, s/$uri/$path/ in the D6 patch), committed! Thanks :)
D7: http://drupalcode.org/project/cdn.git/commit/3860d89
D6: http://drupalcode.org/project/cdn.git/commit/2c92ade
If you get this for
blog/feedhowever, this patch won't solve your problem. This probably only happens when you haven't applied the Drupal core patch.I've rolled a patch that fixes this problem (tested and verified that it works). The problem is that it's impossible to discern between menu system items that do generate files and that don't. So this patch will fail when a URL that uses page arguments (which ImageCache uses, but "blog/feed" does not) and does not generate files.
Comment #6
jaypanI've applied the core patch, but am getting the error for blog/feed (I'm the OP).
Soo... is this patch safe to apply even if I've patched core? Is it going to cause me problems? What do you mean it will fail? Is there some way for me to fix this?
Thanks for your prompt reply by the way, much appreciated.
Comment #7
wim leersI'd guess it'll work fine for 95% of all sites. But there are cases where it may fail.
However, if you can reproduce the "blog/feed" problem even when you *do* have the core patch enabled (did you just apply it, or did you already have it applied in the OP?), something strange must be happening on your site. Could you add the following just before the line that's throwing the error:
Could you then post the output here? Thanks :)
Comment #8
jaypanApologies - I didn't have the core patch applied. I had applied it to a different Drupal installation a few days ago, not the installation I was getting this message from. I've applied it, and the error is gone. Thanks for the assistance!
Comment #9
jaypanComment #10
wim leersThat makes much more sense :) Glad to hear it's solved now!
Comment #12
philsward commentedI'm getting the same thing on 6.x-2.3-dev+1 but for Ubercarts /catalog URL's...
Is this related and in need of backporting? If so, should I create a new issue for it?
I tried to block the catalog* in the CDN Drupal Path blacklist, but this didn't seem to help... From what I can tell, it's only on the homepage of the site too...??
Comment #13
broncomania commented#5 fixes for me also this bug in d7
Comment #14
indigoblue commentedI am also seeing this issue.
I am runing d7.12 and CDN 7.x-2.3.
In addition to the patch in #5, there was mention of a "core" patch - is this something I need to do ( if so, where is it? ).
tx