The first thing that came to mind was an untrapped SIGPIPE, but it appears that the Net::Server::PreFork handles that for you.

Could there be another fatal signal getting sent on your system?

Here's a list of default actions for signals on linux systems taken from kernel/signal.c (kernel 2.6.21.1). 

+--------------------+-----------------+
|  POSIX signal      | default action  |
+--------------------+-----------------+
|  SIGHUP            |  terminate      |
|  SIGINT            |    terminate    |
|  SIGQUIT           |    coredump     |
|  SIGILL            |    coredump     |
|  SIGTRAP           |    coredump     |
|  SIGABRT/SIGIOT    |    coredump     |
|  SIGBUS            |    coredump     |
|  SIGFPE            |    coredump     |
|  SIGKILL           |    terminate(+) |
|  SIGUSR1           |    terminate    |
|  SIGSEGV           |    coredump     |
|  SIGUSR2           |    terminate    |
|  SIGPIPE           |    terminate    |
|  SIGALRM           |    terminate    |
|  SIGTERM           |    terminate    |
|  SIGCHLD           |    ignore       |
|  SIGCONT           |    ignore(*)    |
|  SIGSTOP           |    stop(*)(+)   |
|  SIGTSTP           |    stop(*)      |
|  SIGTTIN           |    stop(*)      |
|  SIGTTOU           |    stop(*)      |
|  SIGURG            |    ignore       |
|  SIGXCPU           |    coredump     |
|  SIGXFSZ           |    coredump     |
|  SIGVTALRM         |    terminate    |
|  SIGPROF           |    terminate    |
|  SIGPOLL/SIGIO     |    terminate    |
|  SIGSYS/SIGUNUSED  |    coredump     |
|  SIGSTKFLT         |    terminate    |
|  SIGWINCH          |    ignore       |
|  SIGPWR            |    terminate    |
|  SIGRTMIN-SIGRTMAX |    terminate    |
+--------------------+-----------------+
|  non-POSIX signal  |  default action |
+--------------------+-----------------+
|  SIGEMT            |  coredump       |
+--------------------+-----------------+

[download]

If you aren't running linux, your vendor should have a similar list available.


TGI says moo

In reply to Re: Problem with Net::Server::Prefork - Server died w/o apparent reason by TGI
in thread Problem with Net::Server::Prefork - Server died w/o apparent reason by psini

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.