Hide Forgot
Description of problem: 'service pulse stop' does not kill the nanny processes after piranha-0.8.4-ipvs-rport.patch was added to piranha (see bug 500909). Ranjith Rajaram noticed that this patch has a chunk for startClientMonitor: - clientInfo.port = service->port; + clientInfo.port = vserver->port; + clientInfo.rport = service->port; and it needs a corresponding chunk for shutdownClientMonitor to shut down cleanly: - clientInfo.port = service->port; + clientInfo.port = vserver->port; + clientInfo.rport = service->port; See the attached patch. Version-Release number of selected component (if applicable): piranha-0.8.4-13.el5 How reproducible: every time Steps to Reproduce: 1. service pulse start 2. pgrep -lf nanny 3. service pulse stop 4. pgrep -lf nanny Actual results: nanny is still running after pulse was stopped Expected results: nanny stops running Additional info:
Created attachment 360334 [details] patch to shutdown nanny Attached is Ranjith's patch to cleanly shutdown the nanny process
Thanks for patch, pushed to upstream: http://git.fedorahosted.org/git/?p=piranha.git;a=commit;h=a82e1facdeb9ab9980351ab7b6f754ceb0885ce1
/me too. Any idea when this is going to make a release? R.
Planned for next update
~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~ RHEL 5.5 Beta has been released! There should be a fix present in this release that addresses your request. Please test and report back results here, by March 3rd 2010 (2010-03-03) or sooner. Upon successful verification of this request, post your results and update the Verified field in Bugzilla with the appropriate value. If you encounter any issues while testing, please describe them and set this bug into NEED_INFO. If you encounter new defects or have additional patch(es) to request for inclusion, please clone this bug per each request and escalate through your support representative.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0297.html