#86785Calling scheduler command on CLI throws error if not in /var/www/html
Description
Calling the scheduler command on CLI throws an error, if the TYPO3 installation is not running in /var/www/html/.
Given the installation, e.g., in /var/www/example.org and calling on CLI
/var/www/example.org/public/typo3/sysext/core/bin/typo3 scheduler:run
the following error is given back:
In GeneralUtility.php line 2172:
Could not create directory “/var/www/html/var/log/”!
Yes, the script has no right to write there, but it is also the wrong directory. It should write into /var/www/example.org/var/log/.
Reviews 5
- main 94495[BUGFIX] Allow scheduler tasks with logger references to be deserialized
- 13.4 94494[BUGFIX] Allow scheduler tasks with logger references to be deserialized
- 14.3 94514[BUGFIX] Allow scheduler tasks with logger references to be deserialized
- main 59237[BUGFIX] Exclude logger from serialize on save for scheduler task
- 9.5 59253[BUGFIX] Exclude logger from serialize on save for scheduler task
Related issues 5
- Bug #86941Logger instances in scheduler tasks are deserialized with outdated paths
- Bug #87261Upgrade wizard for scheduler tasks with invalid Logger instance paths
- Bug #87780Extbase Task should call parents __sleep and __wakeup Methods
- Task #90415Clarify change "Important: #86785 - Calling scheduler command on CLI throws error if not in /var/www/html" ?
- Bug #110049Serialized scheduler database tasks are blocked by DenyListSerializer because of references to TYPO3\CMS\Core\Log\Logger