Hello,
I have a local working copy of a PHP-driven website.
It seems that some Windows process/service is preventing the website's
constituent files from being read at sporadic intervals.
Before I investigate potential non-WAMP-stack causes, such as virus
scanner, etc., I thought I would ask the Tortoise mailing list whether
or not any component of TortoiseSVN (e.g., shell icon overlay) is
capable of causing the observed read-locking behavior.
2 to 5% of the time, the page fails to load, and throws a warning and
error like the following (the files, line numbers, etc. vary):
-----
[06-Jun-2012 16:24:30 UTC] PHP Warning: Unknown: failed to open stream:
No such file or directory in Unknown on line 0
[06-Jun-2012 16:24:30 UTC] PHP Fatal error: Unknown: Failed opening
required 'C:/Users/Me/Documents/Apache/project/public/auxiliary/js.php'
(include_path='.;C:\Program Files\php\PEAR\pear') in Unknown on line 0
-----
The file in question,
"C:/Users/Me/Documents/Apache/project/public/auxiliary/js.php",
definitely exists and has appropriate permissions applied (as evidenced
by the fact that this error does not occur the vast majority of the time).
If I refresh the page, the error/warning list grows shorter with each
refresh, and usually disappears altogether after 2-3 refreshes.
And it's not just PHP files that fail to be read, which leads me to
conclude that the problem is not with PHP or even Apache. Sometimes, it
is a JS or CSS file that cannot be read, in which case the Web-server
responds with "403 Forbidden":
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>403 Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>You don't have permission to access
/project/public/common/js/libs/fancyapps.fancyBox-2.5/source/jquery.fancybox.css
on this server.</p>
</body></html>
With respect to the above 403, the file mentioned is a static library
file that never moves and is never modified. So, it's not as though I'm
doing anything development-related that is locking the file (at least
not willfully). If I reload the page, the issue does not occur this time.
It bears mention that PHP is configured to use APC (Alternate PHP Cache,
an op-code caching engine), and the following directives are being
applied relative to APC, which should prevent stale content from being
served (and thus prevent errors like those pasted above):
apc.stat On
apc.stat_ctime On
Initially, I thought that APC might be causing the problem, despite the
above configuration directives, so I disabled APC completely, yet the
problem persists.
For those interested, PHP is running as an Apache2 module, via mod_php.
Apache is running as a standalone executable (httpd.exe) in command-line
mode.
Thank you for any insights!
-Ben
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2969350
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-06-06 19:34:00 CEST