I have a cron job:
1 0 * * * /usr/bin/wget -q -O /dev/null 'http://123.456.78.90/index/parsedata?&today=1'
It should gather a bunch of data from the DB at 12:01am each day, organize it for use by our app in graphs and displays and then be done.
Sometimes, certain graphs seem to have not been processed as they show no results for some period of time. Manually running the command will cause them to have the correct data.
So it seems cron is part of the issue. Either cron is not firing this, not true as I see most entries display expected graph data, or perhaps cron is not finishing? I do not know where to look as I felt that since manually triggering the above line of script works, why wouldn't it work in the same manner when I set cron to do it? Any ideas?
There is another cron job that runs every 5 minutes on the same server, using the same code:
*/5 * * * * /usr/bin/wget -q -O /dev/null http://123.456.78.90/index/parsedata
Is it possible that the first run takes too long and is still being processed when this script, which runs every 5 minutes, kicks in and this is messing things up? The first script can take longer than 5 minutes to run so this second instance can get run while the first is still grinding way. They both use the same action, parsedata(), in our framework and write to the same database. Maybe? Any ideas appreciated.