alseambusher / crontab-ui

Easy and safe way to manage your crontab file
https://lifepluslinux.blogspot.com/2015/06/crontab-ui-easy-and-safe-way-to-manage.html
MIT License
2.88k stars 478 forks source link

Error: Expression has only 1 part. At least 5 parts are required.` #198

Closed gabrielmaster123 closed 2 years ago

gabrielmaster123 commented 2 years ago

Make sure these boxes are checked( - [x] ) before submitting an issue.

Running job ID: 30jwU1hIYBDzNHRG Original command: python '/home/gabriel/Documents/anisync/plexanisync/PlexAniSync.py' Executed command: ((({ python '/home/gabriel/Documents/anisync/plexanisync/PlexAniSync.py'; } | tee /tmp/30jwU1hIYBDzNHRG.stdout) 3>&1 1>&2 2>&3 | tee /tmp/30jwU1hIYBDzNHRG.stderr) 3>&1 1>&2 2>&3); if test -f /tmp/30jwU1hIYBDzNHRG.stderr; then date >> "/usr/local/lib/node_modules/crontab-ui/crontabs/logs/30jwU1hIYBDzNHRG.log"; cat /tmp/30jwU1hIYBDzNHRG.stderr >> "/usr/local/lib/node_modules/crontab-ui/crontabs/logs/30jwU1hIYBDzNHRG.log"; fi; if test -f /tmp/30jwU1hIYBDzNHRG.stdout; then date >> "/usr/local/lib/node_modules/crontab-ui/crontabs/logs/30jwU1hIYBDzNHRG.stdout.log"; cat /tmp/30jwU1hIYBDzNHRG.stdout >> "/usr/local/lib/node_modules/crontab-ui/crontabs/logs/30jwU1hIYBDzNHRG.stdout.log"; fi Error: Expression has only 1 part. At least 5 parts are required.

i have set this to run hourly

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Victorhtf commented 10 months ago

I'm also with this error, dont know why. That doesnt make sense.

cparello commented 8 months ago

when you use the @hourly i get the error but if i replace it with a standard cron expression 0 the errs goes away 1 part vs 5 parts

LunarTwilight commented 8 months ago

when you use the @hourly i get the error but if i replace it with a standard cron expression 0 the errs goes away 1 part vs 5 parts

Oh that's a good catch, I didn't pick up on that being the reason for the error. Also your message gave me idea to poke around crontab-ui's code and see what's causing the error and it looks like a library that crontab-ui uses (construe) doesn't support crontab extensions (https://github.com/bradymholt/cRonstrue/issues/190, https://github.com/bradymholt/cRonstrue/issues/277) image