Maybe you can track it down a little bit by logging 'everything'.
I'd start by letting tcpdump log everything on input, everything on output into a file.
Once the server dies, the final parts of the logs might help finding out what is wrong.
Even if there is some bug to be found - I'd suspect some bad request - being able to reproduce the issue at will would be a huge help for debugging.
Also, monitor the server's size while running. Maybe it runs out of memory if there are some sort of memory leaks...?
Simply looking on the code and find what might be wrong is really hard, most of the time.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||