UNIX for Beginners Questions & Answers

I have cross-checked it, and the cron jobs are set only once,and scripts are all fine no duplicate lines

So as neo suggested, why don't you insert a timestamp generation logging command into the script that will write a file every time the job runs.

What's the last modified time on the duplicate output reports that you have? Are they created/modified at exactly the same time?

Maybe something like this, just an example, in the script:

Code:

echo $(date +%s)  >> /tmp/mylogfile.txt

Code:

# echo $(date +%s)  >> /tmp/mylogfile.txt
# cat /tmp/mylogfile.txt
1561379037
# echo $(date +%s)  >> /tmp/mylogfile.txt
# cat /tmp/mylogfile.txt
1561379037
1561379165
# echo $(date +%s)  >> /tmp/mylogfile.txt
# cat /tmp/mylogfile.txt
1561379037
1561379165
1561379175

Or even something better

Thanks Neo/Hick.. giving it a try.. so logging is a remedy

--- Post updated at 12:55 AM ---

@hick ..the duplicate record is in (45 seconds),from the first one

You need to be more specific in your analysis and posts.

For example:

Please post the last 10 entries of the DB timestamps vis-a-vis the timestamps from the script.

For example, you informed us that there is a duplicate DB entry 45 seconds from the first entry; but you did not yet inform us when the crontab runs, nor did you provide the crontab entry and nor did you provide the crontab script.

You seem to be asking for us to make up a solution or possible cause to your problem but you are not willing to provide any details.

Why not just provide the details so we can help you?

Hi Neo,

I did cross checked it the log has that mechanism covered in it,logs are getting generated as per timestamp when its run.. and a file is created with the date time stamp for the cron scheduled.

eg logifile25062019.txt (DDMMYY)

But still on the DB side we are observing duplicate entries for that job scheduled