Shooting out errors

I so appreciate this forum and the help that is shared.  Am still rebuilding my site after it was destroy by a hacker,  am getting these errors..

ANY idea what this needs to be fixed?

THANKS

 - - copy and paste

- Membership expiration letters -
Send membership expire letters: 0 letters

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphotNA4A8N in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphot0xX5Hk in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphotmR3pEp in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphottBJ2ZJ in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphotrb1BGS in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphotmYXF5T in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

Warning: filectime(): stat failed for /home/clubadve/public_html/adventistdate.com/tmp/pphotcum0xX in /home/clubadve/public_html/adventistdate.com/inc/classes/BxDolCronCmd.php on line 172

While I can't say for certain what's causing the problem, I can tell you this:

The error in question is that the command filectime($filename) is bashing it's head into something.  Here is the command in context:

$diff = time() - filectime( $value . $lang_file);

What this is doing is trying to find out how old a file is.  By taking the current timestamp, subtracting the timestamp the file was created on, and the result is the difference (in seconds).  If it's over 86400 (1 day) it wants to clean (delete) the file.

This is part of the cron job that tries to keep your file cache fresh and clean.

What could be stopping it?  That part I'm not certain.  But I'll lend a few guesses, see if Any of these are something you haven't thought of:

1. Check permissions in the cache & tmp folders.  If the user that your cron job runs as doesn't have access to view these folders contents, then this may be what's stopping it.

2. It's going after your 'tmp' and 'cache' folders.  I'd double check to ensure that neither of these folders were corrupted, or even deleted by the hack, or in the process of cleaning up from the hack.

Thanks for the response, I really appreciate that.

Those folders are 755 should they be 777?

It happened again last night at the cron time  9:00 pm my time midnight server time.