Project

General

Profile

Actions
Copy link

Bug #61791

closed

Activating the scheduler with a cron job in a chrooted environment​

Added by N. Kara about 10 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-09-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

After the update of a Typo3 6.1 website to 6.2.4 activating the scheduler via Cron does not function.

Activation of the scheduler from 4.5.x to 6.1.x does work on the same server via:
/usr/bin/php -q /httpdocs/cms/typo3/cli_dispatch.phpsh scheduler

On this installation the following error message appears after updating to 6.2.4:

> /usr/bin/php -q
> PHP Warning:  require_once(/var/www/vhosts/myvhost.tld/httpdocs/cms/typo3/sysext/core/Classes/Package/PackageManager.php): failed to open stream: No such file or directory in /httpdocs/typo3_src-6.2.4/typo3/sysext/core/Classes/Core/ClassLoader.php on line 176
> PHP Fatal error:  require_once(): Failed opening required '/var/www/vhosts/myvhost.tld/httpdocs/cms/typo3/sysext/core/Classes/Package/PackageManager.php' (include_path='/httpdocs/cms/typo3/contrib/pear/:.:') in /httpdocs/typo3_src-6.2.4/typo3/sysext/core/Classes/Core/ClassLoader.php on line 176

The server administrator was able to provide a workaround emulating the directory structure in the chroot environment for which he used the symlink:
ln -s / /var/www/vhosts/myvhost.tld

This works absolutely fine, but I think it would be a cleaner solution if a workaround wouldn’t be necessary and Typo3 would search for the script directly in the correct directory.

Actions
Copy link

Also available in: Atom PDF