Hi. I have problem with monit sending emails of timestamp failure even if it shouldn't. On server I have configured following:

1. fetching data from another server with logging by script saved in /usr/local/bin/eset_dl.sh:
#!/bin/bash
wget -P /share/eset -r -m http://nod.rirs.sk/nod4/ --user=name --password=******** &> /share/eset/eset.log

2. removing all data except update.ver file, which is controlled by monit is done by script saved in /usr/local/bin/eset_rm.sh
#!/bin/bash
find /home/eset/nod.rirs.sk/nod4 -type f ! -name 'update.ver' -execdir rm {} +

3. in /etc/cron.d/eset is set periodical run of scripts
# aktualizacia databazy eset mirroru raz denne
0 6 1 * * eset /usr/local/bin/eset_rm.sh
0 6 * * * eset /usr/local/bin/eset_dl.sh

4. monit has this configuration:
Check file eset-version with path /share/eset/nod.rirs.sk/nod4/update.ver
if timestamp > 3 day then alert

I have 3 servers. On 2 with Debian Wheezy (both virtual machines) it works perfect, but one with Debian Squeezy (physical machine) makes problems by sending mails, that update.ver file is not available. Has anyone idea, where could be a problem? Thank You

Welcome to LQ, hope you like it here. You could (temporarily) extend your eset_dl.sh and eset_rm.sh thusly to test?:
(Obviously the line should be inserted before you actually download or remove stuff.) BTW, no idea but you're referring to "/home/eset/" in one script while referring to "/share/eset/" in others?..

Thanks for response. I've added it now, but I'll try it later this week I hope. That different path is just mistake in post, correct path is /home/eset.
I'll post results, when I'll try it.

I've tried it today. Script eset_dl.sh always return "Missing update.ver." message. I've try it on wheezy and it runs without message.