Actions
Bug #43888
closed
Backend login fails when the syslog file cannot be created
Start date:
2012-12-11
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
6.0
PHP Version:
Tags:
Complexity:
easy
Is Regression:
No
Sprint Focus:
Description
When logging to a file is configured in TYPO3_CONF_VARS[SYS][systemLog] and the folder where this file should be does not exist, the backend login process fails because of a non-acquirable lock.
When changing the path to some invalid value after a successful login, everything works as expected. I still have not figured out why this happens, but maybe there was no syslog call in my test environment.
Steps to reproduce:
- set the key [SYS][systemLog] in LocalConfiguration.php to "file,/invalid/path,0"
- clear all caches
- try to log in to the Backend
Updated by Steffen Müller over 11 years ago
confirmed in latest 4.5 ec03f107cf20f61b19ff2e3301e898c19a78e217
Updated by Mateusz Wojtuła about 10 years ago
I tried to reproduce this bug in TYPO3 6.2, but I couldn't. I think this issue is solved in this version.
Updated by Mathias Schreiber about 9 years ago
- Status changed from New to Closed
- Is Regression set to No
Actions