-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"cache.lock" won't be deleted #48
Comments
I got this error once today, but after cleaning my cache dir the error did not occur again. @ametad Could you remove the two This may help us to reproduce the cause of the error. |
Thank you mimmi for your message. Today I am not working, so tomorrow I will have a look at this! |
Steps I took today:
The logging do indeed show some insight. /var/log/apache2/access.log : /var/log/apache2/error.log : The rest of the website works and the server is an Ubuntu14.04. |
Looks like this is duplicate of #20 then |
Indeed, thanks! I will head over there. |
Hi Asgrim, I still have a small problem with the cache.lock file. When configured with: ... and the path to the local file was incorrect, the cache.lock file still resides and therefore does not allow a next try to update the cache with a corrected path. A perfectly expected Exception is thrown with the path set wrongly: Right after this I set the correct path. But it still gives an error: "temporary file already exists", And when I manually remove cache.lock all works like a charm. But I think it should work a bit more fault resistance. The problem is that when an Exception is thrown the lock file is not removed anymore. Perhaps it should be better that the fault will be catched first, so the file can be deleted first and then it can be thrown again...? |
If you use an local file, please set the autoUpdate to false |
Oke I will do that. It was not clear to me that this is the way it should be done. When using the updateMethod UPDATE_LOCAL, how can you update the cache when you provide a newer version of the ini file locally? That is why I set the autoUpdate to true. |
Hi everyone,
The cache.lock file is still present after a successful retrieval of the browscap.ini file. Therefore the next time I try to use Browscap->getBrowser() I get an Exception: "temporary file already exists".
The files:
drwxrwxrwt 8 root root 4096 aug 26 17:13 ./
drwxr-xr-x 23 root root 4096 aug 26 16:17 ../
-rw-r--r-- 1 www-data www-data 8180003 aug 26 16:47 browscap.ini
-rw-r--r-- 1 www-data www-data 0 aug 26 16:47 cache.lock
The directory they reside in is, in this case /tmp:
drwxrwxrwt 8 root root 4096 aug 26 17:06 tmp/
Do I overlook something? Or is this a problem, perhaps experienced by others too?
The text was updated successfully, but these errors were encountered: