Hi.
If you tell the cron service that "here is a file", it understands it as an executable binary. That's why you have to run the shell script through an interpreter. For example like this:
* */1 * * * /bin/bash /usr/script/test5.sh > /tmp/test5.log
The first value */60 at the beginning is of course an error ! A slash marks every N-th repetition, i.e. "stepping size". You used it for the first value from the left which represents minutes. So you want to repeat the same thing every 60 minutes ? That's nonsense ;-). Simply put the fixed value 0 there. So the result will look like this:
0 * * * *
https://crontab.guru/#0_*_*_*_*
“At minute 0 (whenever the minute hand on the real time clock points to zero).”
...but the correct expression is also this:
0 */1 * * *
https://crontab.guru...u/#0_*/1_*_*_*
“At minute 0 past every hour.”
Cron works by checking the clock status every minute... as the match:
minutes hours day month week
If the Cron process finds a match with your time data setting with the real clock, then the command that is listed after this time data is executed.
Also, allowed numerical values for hours and minutes are only 0 to 59. Yes, even zero is a number ! Together with the zero number, there are basically 60 variations altogether. For example, if you wanted to run something every 30 minutes, then you would use this:
*/30 * * * *
https://crontab.guru/#*/30_*_*_*_*
You should also check if your shell script is working properly. It should contain the hashtag: #!/bin/bash on the very first line, and it should also contain newline codes according to Unix, not according to Windows (you can check this in Notepad++, for example).