Why not Cron executes the job on schedule?

Tell me, why cron can't work out the schedule and how Troubleshooting such reasons?

# run-parts
0 * * * * root run-parts /home/user/script
June 5th 19 at 21:40
4 answers
June 5th 19 at 21:42
Solution
1. When running as root works if run from any folder?
run-parts /home/user/script

2. If works, then check for empty rows at the end of the crontab

3. sudo crontab-e
each user has its own crontab, and if you are editing on behalf of a normal user, then convert will not work.
To run cron as root edit the cron as root
1. doesn't work (Not a directory: /home/user/script)
2. claim 1 does not work (empty string there)
3. to sudo crontab-e no problems running the script, but crontab-e (for specific user) - Fabiola_Run commented on June 5th 19 at 21:45
1. For starters, fix this item. /home/user/script obviously need to replace your way.
3. It is necessary to remove from a specific user and transfer in sudo crontab-e - Kiley33 commented on June 5th 19 at 21:48
and they can run manually and not scheduled from the Cron daemon? - Fabiola_Run commented on June 5th 19 at 21:51
manually only run in the console - Kiley33 commented on June 5th 19 at 21:54
June 5th 19 at 21:44
# run-parts
0 * * * * root run-parts /home/user/script


It's all in what crontab?
If it is in the user, then root is unnecessary.
If not custom, then I suspect that it finds run-parts - specify the full path to run-parts
June 5th 19 at 21:46
cat /var/log/syslog | grep 'cron'
June 5th 19 at 21:48
1. The correct path to the file?
2. Installed execute permission on the file chmod +x
3. When run from console, file executes?

In General, little information.
What file and what errors?

Find more questions by tags LinuxCron