Issue Bug Closed

#87094A Symfony Console based scheduler task can't be executed and breaks the scheduler module

Josef Glatz 12/07/18, 00:15 updated 05/07/19, 12:15

Description

Problem/Description

Ways to reproduce

  1. Install TYPO3 and setup a language update scheduler task
  2. Create a DB dump of task
  3. Import into any other TYPO3 instance or run the same instance in another environment (where the path to var folder is different then before)
  4. The scheduler can’t be opened

The problem seems to be the serialized task object

#1170251401 RuntimeException
Could not create directory “/Volumes/CS/Projekte/TYPO3/TYPO3-Distribution/TYPO3-Distribution/app/var/log/”!

O:54:"TYPO3\CMS\Scheduler\Task\ExecuteSchedulableCommandTask":11:{s:20:"*commandIdentifier";s:15:"language:update";s:12:"*arguments";a:1:{s:7:"locales";a:0:{}}s:11:"*defaults";a:1:{s:7:"locales";a:0:{}}s:10:"*taskUid";i:11;s:11:"*disabled";b:0;s:19:"*runOnNextCronJob";b:0;s:12:"*execution";O:29:"TYPO3\CMS\Scheduler\Execution":6:{s:8:"*start";i:1499404020;s:6:"*end";s:1:"0";s:11:"*interval";i:0;s:11:"*multiple";s:1:"0";s:10:"*cronCmd";s:11:"30 23 * * 7";s:23:"*isNewSingleExecution";b:0;}s:16:"*executionTime";i:1544394600;s:14:"*description";s:66:"Update language packs of active extensions from translation server";s:12:"*taskGroup";i:1;s:9:"*logger";O:25:"TYPO3\CMS\Core\Log\Logger":5:{s:7:"*name";s:54:"TYPO3.CMS.Scheduler.Task.ExecuteSchedulableCommandTask";s:12:"*requestId";s:13:"822f9e9294e05";s:18:"*minimumLogLevel";i:7;s:10:"*writers";a:8:{i:0;a:2:{i:0;O:36:"TYPO3\CMS\Core\Log\Writer\FileWriter":1:{s:10:"*logFile";s:97:"/Volumes/CS/Projekte/TYPO3/TYPO3-Distribution/TYPO3-Distribution/app/var/log/typo3_def1afbf7d.log";}i:1;O:42:"TYPO3\CMS\Adminpanel\Log\InMemoryLogWriter":0:{}}i:1;a:2:{i:0;r:26;i:1;r:28;}i:2;a:2:{i:0;r:26;i:1;r:28;}i:3;a:2:{i:0;r:26;i:1;r:28;}i:4;a:2:{i:0;r:26;i:1;r:28;}i:5;a:1:{i:0;r:28;}i:6;a:1:{i:0;r:28;}i:7;a:1:{i:0;r:28;}}s:13:"*processors";a:0:{}}}

Acceptance Criteria

A scheduler task must work if you import a dump or you run the TYPO3 instance in another path

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.