Hmm .. maybe wrap the offending call in an eval and do a confess if a bad thing happened ..

Interesting what happens when you follow your own advice.

I wrapped the three possibly offending calls up with an eval and after trying to provoke the error finally got *two* errors:

• Inappropriate ioctl for device
• Stale NFS file handle

with the first error causing the second error. So that tells me that it's an NFS problem, which is fine. The parallel processes are jobs running on a Sun Grid Engine that are all using NFS to come back to my workstation's file system.

That tells me that NFS may need tuning, but it's not the fault of the Cache::Cache family of modules or even my web application.

So, problem solved. Thanks anyway!

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.