Child processes getting killed by itself on application startup deployed on Perl 5.12.1

ritesh292 has asked for the wisdom of the Perl Monks concerning the following question:

Hi, I was trying to deploy my application on production on perl 5.12.1 and have encountered this issue where the child elements are getting killed by itself on starting the application. As part of this change we had also upgrade the perl version to 5.12.1 so that we can make use of the DBIX module. The same application or code is working fine in my pre live env. Also we had installed the perl lib just by creating a tar of the libs used in pre live(working) and copy pasting it to production env. Is there a chance this would have caused this? Or is it happening because it requires any additional modules? We got the following error during the change-: INFO (main::(1790)) 17/11/2011 02:03:21:97 Making a new child INFO (main::(1799)) 17/11/2011 02:03:22:01 <Application> Started and Listening INFO (main::_the_reaper(1527)) 17/11/2011 02:03:22:04 It appears that one or more children has died. Check if this is the case and clean up INFO (main::_the_reaper(1540)) 17/11/2011 02:03:22:04 Dead child was PID: 28537 INFO (main::_the_reaper(1540)) 17/11/2011 02:03:22:04 Dead child was PID: 28538 INFO (main::_the_reaper(1540)) 17/11/2011 02:03:22:04 Dead child was PID: 28539 Please can someone please let me know if they have ever encountered this kind of a prob? I need to have a resolution to this at the earliest.

Comment on Child processes getting killed by itself on application startup deployed on Perl 5.12.1

Replies are listed 'Best First'.
Re: Child processes getting killed by itself on application startup deployed on Perl 5.12.1 by chromatic (Archbishop) on Nov 18, 2011 at 07:41 UTC
Without more information about the environment or the execution model or any additional logs (are there other logs? "Something isn't running anymore" is pretty vague!), all anyone can do is guess. With that said, unless your working and production environments are exactly the same (down to the way you've compiled or installed Perl and such), copying over libs tends not to work well. Improve your skills with Modern Perl: the free book.	[reply]

Replies are listed 'Best First'.

Re: Child processes getting killed by itself on application startup deployed on Perl 5.12.1
by chromatic (Archbishop) on Nov 18, 2011 at 07:41 UTC

Without more information about the environment or the execution model or any additional logs (are there other logs? "Something isn't running anymore" is pretty vague!), all anyone can do is guess.

With that said, unless your working and production environments are exactly the same (down to the way you've compiled or installed Perl and such), copying over libs tends not to work well.

Improve your skills with Modern Perl: the free book.

[reply]