Intermittent problems are always the worst. Before we go too far, I'm suspecting that you're using mod_perl here - is that right? Do you set $Date::Manip::Cnf{"UpdateCurrTZ"} to true? That's the only scenario under which my perusal of the code says that this failure could occur. So perhaps the short-term fix is to stop using mod_perl ;-)
The next step may be to put a stack trace in Date::Manip::Date_Init to see who is calling it and when (and why). At some point, some bad value must be getting into $Curr{"y"}, and then things get screwed up from there. A stack trace there may help pinpoint things, though it'll likely completely overwhelm your apache error log (assuming you're throwing your stack trace to stderr, which makes more sense than stdout!), so you may want to create a new log file. The key here is to catch the transition from good to bad, and what happens at that point. I'm not sure what to expect, but that's the next step I'd be looking at.
In reply to Re: obscure/random input Date::Manip errors
by Tanktalus
in thread obscure/random input Date::Manip errors
by ksublondie
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |