Hi,
I have an apache-2.4.54 server on fedora37, and seeing errors related to
cache_disk, although this problem has been happening through many
previous versions as well.
[Mon Nov 28 11:29:38.432076 2022] [cache_disk:error] [pid 65726:tid
65836] (2)No such file or directory: [client 141.101.76.185:43162]
AH00708: Cannot open data file
/var/cache/httpd/by1/Efa/HuNQwPygHKuABt5g.header.vary/zFc/VdE/fLiaUcpBcM4BLolg.data
[Mon Nov 28 11:29:48.984197 2022] [cache_disk:error] [pid 67093:tid
67128] (70014)End of file found: [client 172.68.11.126:14692] AH00717:
Premature end of cache headers., referer:
https://linuxsecurity.com/features/introduction-to-gnu-privacy-guard
The site is proxied by cloudflare, so both IPs are owned by them as
well. Is anyone familiar with a potential httpd cache and cloudflare
cache conflict or other issues related to cloudflare that may be causing
this?
The fLiaUcpBcM4BLolg.data file referenced above indeed doesn't exist.
However, the .header version of the file does. This entry appears to be
from September, more than 60 days ago.
CacheQuickHandler off
CacheLock on
CacheLockPath /tmp/mod_cache-lock
CacheLockMaxAge 5
CacheIgnoreHeaders Set-Cookie
CacheRoot "/var/cache/httpd"
CacheDetailHeader on
CacheEnable disk "/"
CacheHeader on
CacheDefaultExpire 800
CacheMaxExpire 64000
CacheIgnoreNoLastMod On
ExpiresActive on
ExpiresDefault A300
CacheDirLevels 2
CacheDirLength 3
If CacheDefaultExpire is set to 800 seconds, why is apache still looking
in a location that is 60 days old? Why wasn't the entire directory
removed when the cache expired? I believe we used to have htcacheclean
set up as a daemon, but it hasn't run in some time. Is this related?
Thanks,
Dave
--
DaveWreski
President & CEO
Guardian Digital, Inc.
We Make Email Safe
640-800-9446 <tel:640-800-9446>
dwreski@guardiandigital.com <mailto:dwreski@guardiandigital.com>
https://guardiandigital.com <https://guardiandigital.com>
103 Godwin Ave, Suite 314, Midland Park, NJ 07432
facebook <https://www.facebook.com/gdlinux>
twitter <https://twitter.com/gdlinux>
linkedin <https://www.linkedin.com/company/guardiandigital>
I have an apache-2.4.54 server on fedora37, and seeing errors related to
cache_disk, although this problem has been happening through many
previous versions as well.
[Mon Nov 28 11:29:38.432076 2022] [cache_disk:error] [pid 65726:tid
65836] (2)No such file or directory: [client 141.101.76.185:43162]
AH00708: Cannot open data file
/var/cache/httpd/by1/Efa/HuNQwPygHKuABt5g.header.vary/zFc/VdE/fLiaUcpBcM4BLolg.data
[Mon Nov 28 11:29:48.984197 2022] [cache_disk:error] [pid 67093:tid
67128] (70014)End of file found: [client 172.68.11.126:14692] AH00717:
Premature end of cache headers., referer:
https://linuxsecurity.com/features/introduction-to-gnu-privacy-guard
The site is proxied by cloudflare, so both IPs are owned by them as
well. Is anyone familiar with a potential httpd cache and cloudflare
cache conflict or other issues related to cloudflare that may be causing
this?
The fLiaUcpBcM4BLolg.data file referenced above indeed doesn't exist.
However, the .header version of the file does. This entry appears to be
from September, more than 60 days ago.
CacheQuickHandler off
CacheLock on
CacheLockPath /tmp/mod_cache-lock
CacheLockMaxAge 5
CacheIgnoreHeaders Set-Cookie
CacheRoot "/var/cache/httpd"
CacheDetailHeader on
CacheEnable disk "/"
CacheHeader on
CacheDefaultExpire 800
CacheMaxExpire 64000
CacheIgnoreNoLastMod On
ExpiresActive on
ExpiresDefault A300
CacheDirLevels 2
CacheDirLength 3
If CacheDefaultExpire is set to 800 seconds, why is apache still looking
in a location that is 60 days old? Why wasn't the entire directory
removed when the cache expired? I believe we used to have htcacheclean
set up as a daemon, but it hasn't run in some time. Is this related?
Thanks,
Dave
--
DaveWreski
President & CEO
Guardian Digital, Inc.
We Make Email Safe
640-800-9446 <tel:640-800-9446>
dwreski@guardiandigital.com <mailto:dwreski@guardiandigital.com>
https://guardiandigital.com <https://guardiandigital.com>
103 Godwin Ave, Suite 314, Midland Park, NJ 07432
facebook <https://www.facebook.com/gdlinux>
twitter <https://twitter.com/gdlinux>
linkedin <https://www.linkedin.com/company/guardiandigital>