Everthing seems fine ? isn't it? Time priod is right. There is no error messages.
I added !/bin/bash first line of this script but reason didn't change.
If it isn't the missing # at the start of the shebang line then it could be that wget isn't on crontab's path.
try substituting the full path to the wget binary
Does your script rely on relative path names or other things that require a path? Items in cron do not get a full environment and thus need to have their variables defined more rigorously or source an environment script.
Also, how are you executing the script manually? Is there an x bit set for the user in cron?
This will redirect stdout and stderr to those 2 log files. There should be hopefully some message in them.
Also you might want to leave out the extra sh as you start a new shell anyway, with #!/bin/bash a bash, as you wrote. What's the leading "root" for?
Also in a script being issued via cron you should always use absolute paths like:
/usr/bin/wget ....
While I write this - just as people said.
There is also a good article about usage of crontab in this forum you should read:
Let me guess, you assume it's not working because you don't see a ntop-* file anywhere in your home directory, right? That's because cron doesn't execute your script in your home directory, but in an empty temporary directory.
Tell wget to save to an absolute path, instead of a relative, and you should see your file.
# tail -f /tmp/ntopdump.log
/bin/sh: root: command not found
/bin/sh: root: command not found
/bin/sh: root: command not found
/bin/sh: root: command not found
/bin/sh: root: command not found
/bin/sh: root: command not found
root is not command only user!!!!
schema of the crontab picture is attached.
I have deleted root parameter from crontab and it is done.
I have changed crontab line like below but it gave same error message.