I found it!!

Something in the OS - that was also my first thought, as I did not write such a silly error msg into my script.

I am running Debian/Linux (Ubuntu). And the hint to var log was right: I found in var/log/kern.log an entry which sais "Out of memory: Killed process 2832 (perl)", which is what triggered the event!

What my server-script does: it consumes (and needs) quite an amount of memory (about 200MB of 1Gig system dram total). The log also tells some swapping happened before the event, I think that swap, plus system plus my script was just too much... Now, I will insert some tweaks to reduce ram usage, until the system receives more physical ram. Thanks again!
(although I am not yet such an ace to know what oom and ulimit exactly is..;) )

In reply to Re^2: Why does my script exit with "Killed" - that's all... by isync
in thread Why does my script exit with "Killed" - that's all... by isync

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.