Bug #61791
closed
Activating the scheduler with a cron job in a chrooted environment
0%
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.
Updated by Markus Klein about 10 years ago
- Category deleted (
scheduler) - Status changed from New to Needs Feedback
Can you find out where TYPO3 gets to know about the true path at all?
Is there some environment or server variable that maybe has a wrong path?
Generally, in a chrooted env, this should be fully transparent and the application should not even recognize that it is in a limited env.
Updated by Alexander Opitz almost 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.