Created attachment 379837 [details] Lvs.cf configuration file installing the previous piranha rpm 0.8.4-11.el5.i686.rpm FIXES the problem. Description of problem: Although the output from ps aux |grep nanny shows that nanny uses port 808 /usr/sbin/nanny -c -h ip1 -V ip2 -p 8080 -s GET / HTTP/1.1\r\n\r\n -x HTTP/1.1 -t 3 --fos in reality tcpdump -i any port 8080 gives no output. nanny uses the standard port 80 instead which is not according to our configuration. installing the previous piranha rpm 0.8.4-11.el5.i686.rpm FIXES the problem. Version-Release number of selected component (if applicable): piranha-0.8.4-13.el5.i686.rpm
Can you test this new srpm? It contains one fix for bug which occured when port != 80 http://marx.fedorapeople.org/piranha-0.8.4-15.el5.src.rpm
Hopefully I can provide my testresults today
Upgrading to version 0.8.4-15 did not solve the problem. Still not seeing any network traffic on tcp port 8080. We see the traffic on port 80, however. Do you need any additional information?
Sorry, for such delay - it looks like rport was set to 80 by default. Can you test this srpm? http://marx.fedorapeople.org/piranha-0.8.4-16.el5.src.rpm
rpmbuild -ba piranha.spec error: Failed build dependencies: popt-devel is needed by piranha-0.8.4-16.i386 ==> I cannot seem to find the popt-devel package for RHAS5.4
Sorry, wrong build. This one should be correct http://marx.fedorapeople.org/piranha-0.8.4-17.el5.src.rpm
Hello again This new build seems to fix the problem. Ok for me ! Thanks
When will this be available in the official redhat repository?
(In reply to comment #8) > When will this be available in the official redhat repository? It will be delivered with the next minor version of RHEL (RHEL5.5). If you need something sooner, or want official support please see the following: Thank you for taking the time to enter a bug report with us. We do appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for getting support, and as such we are not able to make any guarantees as to the timeliness or suitability of a resolution. If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain that it gets the proper attention and prioritization to assure a timely resolution. For information on how to contact the Red Hat production support team, please see: https://www.redhat.com/support/process/production/#howto Thanks!
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