http://qs321.pair.com?node_id=979255


in reply to Errors in Worst Nodes

The non-technical explanation, in complete detail: "S*** happens!"

The technical explanation isn't much different. Server hiccups. MySQL glitches. Xmsn errors. Power dips. Flaky RAM. Disk errors....

A "page refresh" may yield the (apparent) result of clearing the error, but it doesn't have much to do with the underlying problem(s).

BTW, this is a complicated (by some standards) system. In a prior life, dealing with mechanical critters like airplanes, we frequently cited another truism: "Aircraft are complicated mechanical systems. Complicated systems break." With modest paraphasing, that applies here, too.

Replies are listed 'Best First'.
Re^2: Errors in Worst Nodes
by thomas895 (Deacon) on Jun 30, 2012 at 19:25 UTC

    The technical explanation isn't much different. Server hiccups. MySQL glitches. Xmsn errors. Power dips. Flaky RAM. Disk errors....
    There would have to be quite a few of them -- I've been seeing it almost daily.

    A "page refresh" may yield the (apparent) result of clearing the error, but it doesn't have much to do with the underlying problem(s).
    I know, I just had to take the Microsoft way(where restarting makes problems go away, but then refresh here), as there's not much I could do at the moment.

    ~Thomas~
    confess( "I offer no guarantees on my code." );
[reply]
[d/l]
      Yes, sometimes there are an annoying, troublesome, puzzling "quite a few" of them but, OTOH, the annoying, troublesome, puzzling "quite a few" of them could all get thrown because a single adverse occurance is repeating itself.

      In any case, the keepers of the Monastery are aware... and are using their stockpile of (name your favorite insecticide) to try to stop any further repetitions.

      Thanks for your concern. Wish I had happier answer.

[reply]
        It better not be toxic to oysters.
[reply]

In Section Perl Monks Discussion