Bug #75802
closed
scheduler cron command
0%
Description
Hi,
I am not sure if I am doing something wrong.
I have scheduled a scheduler command in cron syntax.
30 * * * * /usr/bin/php /var/www/av_homep/typo3/cli_dispatch.phpsh scheduler
From my perspective, this should be a valid syntax for a cron command.
I use this on ubuntu level the same way and it works to start the job each hour at xx:30.
The error message I get:
Invalid frequency. Please enter either a number of seconds or a valid cron command. The cron parser said: Unable to split given cron command to five fields. [code: 1291227373].
I hope it is not a bug. So I would be happy someone to tell me the right syntax.
Regards
Karl-Heinz
Updated by Wouter Wolters over 8 years ago
- Status changed from New to Needs Feedback
Can you check your scheduled task and their frequency? This is not the cron task on the server itself but in your TYPO3 installation that gives this error.
Updated by Karl-Heinz Fischbach over 8 years ago
Hi,
I don't know what you mean with this question.
The description of the backend field "frequency" sais, that I can put in a command as shown in the bug with cron syntax.
So I did.
This throws the error in typo3 -------- not on linux level.
Since the cron syntax does not work I had to set the frequency on a fixed value (seconds). But cron logic would suit my needs better.
Karl-Heinz
Updated by Wouter Wolters over 8 years ago
"30 * * * * /usr/bin/php /var/www/av_homep/typo3/cli_dispatch.phpsh scheduler" needs to be set in a crontab not in TYPO3 itself.
From TYPO3 you can add the real cronjobs you want to run and specify the frequency as "30 * * * *".
Updated by Karl-Heinz Fischbach over 8 years ago
Hi,
O.K., the description of the scheduler and the backend form have mislead me.
Now, entering only the time part of the cron command in t3 scheduler there is no error message anymore.
Sorry for wrong understanding from my side.
Please close ticket.
Regards
Karl-Heinz
Updated by Wouter Wolters over 8 years ago
- Status changed from Needs Feedback to Closed
No problem :) Great it worked out in the end. If you have more questions or problems it is a good idea to join our Slack channel and ask other TYPO3 developers for some help.
Chat with us:
The TYPO3 team is using a tool called Slack to openly communicate with each other and with the public. Several teams use Slack as a way to communicate internally and most channels are a welcome place for you to join and get yourself involved.
Register: https://forger.typo3.org/slack/
Slack: https://typo3.slack.com/
Updated by Feeela no-lastname-given over 6 years ago
I vote to re-open this bug as the description and documentation still is misleading.
The input-field in the scheduler backend is labeled with “Frequency (seconds or cron command)”. But if one inserts a cron command here, an error is thrown as described above.
Please update the field label and documentation, so that it becomes clear that a “cron schedule expression” is expected instead of a “cron command”. (The latter including the command to execute.)
The choice of words is important. Thank you.