Re^3: Parallel ForkManager problem: parent dies early before all the child finishes

That is probably the Apache web server timing out your process. A http server does not like to wait around on long processes, there are ways around it. See Managing a long running server side process using CGI. You might check the httpd error logs and see if you see an error about timeout, or google for expired: ap_content_length_filter: apr_bucket_read() failed. . A most often recommended read for this problem is Merlyn's watching long processes thru cgi

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

Comment on Re^3: Parallel ForkManager problem: parent dies early before all the child finishes

Replies are listed 'Best First'.
Re^4: Parallel ForkManager problem: parent dies early before all the child finishes by dayem98 (Initiate) on Aug 19, 2011 at 14:55 UTC
I was running the normal(serial) version of the program and it runs for 1 hour or so without any problem. I was trying to use parallel version to make the whole thing faster, but for some reason, parent process cant live for even 3/4 minutes.	[reply]
Re^5: Parallel ForkManager problem: parent dies early before all the child finishes by zentara (Cardinal) on Aug 19, 2011 at 17:56 UTC
This is in accordance with ikegami's advice: Do you have signal handlers in the parent? I'm just guessing here, but read O'Reilly forking child processes in cgi It may be that you are not handling the SIG{'CHILD'} for the parallel processes correctly. It recommends `$SIG{'CHLD'} = "wait_for_child_to_die"; sub wait_for_child_to_die{ wait; }` [download] I'm not really a human, but I play one on earth. Old Perl Programmer Haiku ................... flash japh	[reply] [d/l]