Bug #87094

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

Added by Josef Glatz 3 months ago. Updated 6 days ago.

Status:
Needs Feedback
Priority:
Must have
Assignee:
-
Category:
scheduler
Target version:
-
Start date:
2018-12-07
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
language:update, cron
Complexity:
Is Regression:
Yes
Sprint Focus:

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


Related issues

Related to TYPO3 Core - Bug #86941: Logger instances in scheduler tasks are deserialized with outdated paths New 2018-11-16
Duplicated by TYPO3 Core - Bug #87715: Exception while deserialization of a task object Closed 2019-02-14
Duplicates TYPO3 Core - Bug #86785: Calling scheduler command on CLI throws error if not in /var/www/html Resolved 2018-12-21

History

#1 Updated by Josef Glatz about 1 month ago

  • Related to Bug #86941: Logger instances in scheduler tasks are deserialized with outdated paths added

#2 Updated by Josef Glatz 6 days ago

  • Duplicated by Bug #87715: Exception while deserialization of a task object added

#3 Updated by Georg Ringer 6 days ago

  • Duplicates Bug #86785: Calling scheduler command on CLI throws error if not in /var/www/html added

#4 Updated by Georg Ringer 6 days ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback

isnt that solved with #86785 as well?

Also available in: Atom PDF