Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: AH00708: Cannot open data file |
|
| Author |
|
gossamer
Joined: 24 Feb 2019
Posts: 2
Location: US, Newark
|
 Posted: Mon 25 Feb '19 18:01 Post subject: AH00708: Cannot open data file |
 |
|
I'm experiencing a [cache_disk:error] problem with httpd-2.4.34 on fedora28. It appears to happen every few minutes. I have no idea what could be causing it. I had previously responded to an old, existing thread on this topic, but thought it would be better to start a new thread. I'm really stuck.
This is a joomla-3.8 host (linuxsecurity.com). I believe this started after we changed the site name from webstage to www, although it could be a coincidence.
I've tried setting EnableSendfile to off, but it hasn't helped. The document root is not on an NFS share or any of the other issues explained in the Apache docs here:
https://httpd.apache.org/docs/current/mod/core.html#enablesendfile
| Code: | | [Sun Feb 24 09:05:14.882412 2019] [cache_disk:error] [pid 24070:tid 140295157044992] (2)No such file or directory: [client 173.212.225.134:47834] AH00708: Cannot open data file /var/cache/httpd/HRx/pOb/xK7/mTz/tMN/ioVCrxg.header.vary/ULG/TWv/f_X/eCj/Q5X/QCqsi_Q.data |
Below is my config as it relates to caching:
| Code: | CacheQuickHandler off
CacheLock on
CacheLockPath /tmp/mod_cache-lock
CacheLockMaxAge 5
CacheIgnoreHeaders Set-Cookie
CacheRoot "/var/cache/httpd"
# Enable the X-Cache-Detail header
CacheDetailHeader on
CacheEnable disk "/"
CacheHeader on
CacheDefaultExpire 800
CacheMaxExpire 64000
CacheIgnoreNoLastMod On
ExpiresActive on
ExpiresDefault A300
CacheDirLevels 5
CacheDirLength 3 |
|
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7373
Location: Germany, Next to Hamburg
|
| Posted: Wed 27 Mar '19 16:27 Post subject: |
|
|
Maybe you can set the LogLevel[1] for the cache to a higher level to get that debugged.
Note that you can set that for each module,so you won't have debug content from all modules
e.g.
| Code: |
LogLevel warn ssl:error auth_digest:error socache_shmcb:warn mpm_worker:warn fcgid:info
|
[1] https://httpd.apache.org/docs/2.4/mod/core.html#loglevel |
|
| Back to top |
|
|
|
|
|
|
