Page 1 of 1

[solved] Random filemtime() errors

Posted: Tue Mar 24, 2009 12:48 am
by clc
Hi -- I'm randomly getting the following error at the top of pages when browsing through my site:

Warning: filemtime() [function.filemtime]: stat failed for {path to CMSMS root}/tmp/templates_c/%%7E^7E8^7E8F1701%%template%3A20.php in {path to CMSMS root}/lib/smarty/Smarty.class.php on line 1392

It will often go away upon refreshing, and doesn't do it consistently on any particular page, but it doesn't usually let me get through more than 5-10 clicks before it appears again.  I've tried clearing the cache but that doesn't seem to help.  It also does it in both Firefox 3.0.7 and IE 7 -- haven't seen it yet in Safari (PC) though.

Server/software details:

CMSMS: 1.5.3 full version
Debian Linux
Apache v1.3.33
PHP: 5.2.1
MySQL: 5.0.45
Firefox 3.0.7 and IE 7

Any help would be much appreciated...I'm not sure what to try next...

Thanks!
Karena

Re: Random filemtime() errors

Posted: Tue Mar 24, 2009 8:07 am
by alby
karena wrote: Warning: filemtime() [function.filemtime]: stat failed for {path to CMSMS root}/tmp/templates_c/%%7E^7E8^7E8F1701%%template%3A20.php in {path to CMSMS root}/lib/smarty/Smarty.class.php on line 1392
Because you have a "{path to CMSMS root}" ????
config.php?

Alby

Re: Random filemtime() errors

Posted: Mon Mar 30, 2009 5:18 am
by clc
Naw, I just put that "[path to CMSMS root]" in as a placeholder rather than typing out the whole path for security reasons.  However, I finally got a brilliant tech on the phone at the hosting company, who diagnosed the problem as a race condition.  He changed something in my PHP settings (enforce threading?) to prevent that from happening in the future.  And voila, the error messages are gone.  :)

Karena

Re: [solved] Random filemtime() errors

Posted: Thu Apr 30, 2009 3:35 pm
by JackOutoftheBox
I am having the same problem with one of my newly launched sites, and have just reached out to my hosting company on the matter, although they have said in the past that they do not offer third-party software support. With your direction, I hope to get their help, however. If I have anything to add here, I will add to this post for other folks. I have only noticed this issue on the newer software installs of 1.5.3 and 1.5.4.