CMS Made Simple Forums

Warning: filemtime(): Stat failed for /data/11/0/93/61/908550/user/929382/htdocs/tmp/templates_c/%%25/25C/25C8B04D%%template%3A15.php (errno=116 - Stale NFS file handle) in /data/11/0/93/61/908550/user/929382/htdocs/lib/smarty/Smarty.class.php on line 1392

This seems to happen from time to time, it's not a common error. I hit refresh and the error then goes away. This will only annoy the client. Anyone know why this would be happening?

CMS Made Simple 0.13
PHP 4.4
MySQL 4.1
Network Solutions

-K

Kayin wrote: Warning: filemtime(): Stat failed for /data/11/0/93/61/908550/user/929382/htdocs/tmp/templates_c/%%25/25C/25C8B04D%%template%3A15.php (errno=116 - Stale NFS file handle) in /data/11/0/93/61/908550/user/929382/htdocs/lib/smarty/Smarty.class.php on line 1392

This seems to happen from time to time, it's not a common error. I hit refresh and the error then goes away. This will only annoy the client. Anyone know why this would be happening?

CMS Made Simple 0.13
PHP 4.4
MySQL 4.1
Network Solutions

-K

Hmm... Other websites with other software have had the same problem: http://www.google.com/search?q=php+Warn ... +handle%22

Here are some pages that describe your error: http://www.google.com/search?q=%22Stale ... +handle%22

This page seems to have a fix (you'd have to ask your webhost about it): http://www.actkid.com/2006/06/08/ls-sta ... 03-server/

It seems as though the webhost uses NFS (Network File System. A protocol for sharing file systems over a network.) which seems to cause problems with CMSMS's cache files.

It could be the wehhost has occasional problems with NFS.

From: http://www.neowin.net/forum/index.php?showtopic=470907

...
Sounds to me like the NFS share between the servers has borked.
...

Maybe turning off smarty caching would solve this problem (I'm not sure if this will actually disable the caching solving this problem, Ted would probably know better):
http://forum.cmsmadesimple.org/http://p ... 066#p27066

I assume clearing the CMSMS cache in "Site Admin -> Global Settings" has not worked?

Hope you find a solution to this.

Yea I've been clearing the cache from time to time and still get the errors.

NFS stale file handling seems like a webserver configuration issue more so than a CMS issue which kind of irritates me, the webhost had a pretty significant php bug last weekend all weekend basically rending the site entirely useless. I got an e-mail from them about it.

I'll try to disable the smart caching system tomorrow at work, I'll keep ya updated.

A stale file handle is given when
1) an NFS server is heavily loaded and cannot respond to NFS requests;
2) The NFS Server has crashed (can usually be detected by numerous RPC timeouts by the client);
3) The destination mount-point, file or directory location has been compromised thus making it inaccessible to the NFS Client (the NFS client points to something that does not exist).

#3 seems most likely given the circumstances.

-K

I tried to disable the smarty caching and still wound up with the error.

Anyone else have any ideas?

Well, still haven't solved this fun little problem.  I talked to the host and they don't seem to know what "NFS" is.  I can't get through the hirearchal BS to the people who actually might help, all the lower levels absolutely insist that because I'm running a web application that uses a database and php, that the problem is the software.

Sorry bout the small rant, just a bit frusterated.  Thought i'd bump this to see if anyone had any other ideas.

-K