From robin-lists at robinbowes.com Fri Oct 30 17:02:17 2009 From: robin-lists at robinbowes.com (Robin Bowes) Date: Fri, 30 Oct 2009 17:02:17 +0000 Subject: nanny processes remaing running when pulse stopped Message-ID: <4AEB1C19.2070304@robinbowes.com> Hi, I've noticed that the nanny processes remaining running when the pulse daemon is stopped/restarted. So, if you restart pulse a few times, you end up with dozens of nanny processes. Surely this is not supposed to happen? Should pulse close all the nanny processes when it shutdown? R. From robin-lists at robinbowes.com Fri Oct 30 17:08:51 2009 From: robin-lists at robinbowes.com (Robin Bowes) Date: Fri, 30 Oct 2009 17:08:51 +0000 Subject: nanny processes remaing running when pulse stopped In-Reply-To: <4AEB1C19.2070304@robinbowes.com> References: <4AEB1C19.2070304@robinbowes.com> Message-ID: <4AEB1DA3.7010607@robinbowes.com> On 30/10/09 17:02, Robin Bowes wrote: > Hi, > > I've noticed that the nanny processes remaining running when the pulse > daemon is stopped/restarted. So, if you restart pulse a few times, you > end up with dozens of nanny processes. > > Surely this is not supposed to happen? Should pulse close all the nanny > processes when it shutdown? I should add that this is: # cat /etc/redhat-release CentOS release 5.4 (Final) # rpm -q piranha piranha-0.8.4-13.el5 R. From lhh at redhat.com Fri Oct 30 17:13:18 2009 From: lhh at redhat.com (Lon Hohberger) Date: Fri, 30 Oct 2009 13:13:18 -0400 Subject: nanny processes remaing running when pulse stopped In-Reply-To: <4AEB1C19.2070304@robinbowes.com> References: <4AEB1C19.2070304@robinbowes.com> Message-ID: <1256922798.5025.23.camel@localhost.localdomain> On Fri, 2009-10-30 at 17:02 +0000, Robin Bowes wrote: > Hi, > > I've noticed that the nanny processes remaining running when the pulse > daemon is stopped/restarted. So, if you restart pulse a few times, you > end up with dozens of nanny processes. > > Surely this is not supposed to happen? Should pulse close all the nanny > processes when it shutdown? It's supposed to shut them down. I'd file a bugzilla. -- Lon From robin-lists at robinbowes.com Fri Oct 30 18:09:17 2009 From: robin-lists at robinbowes.com (Robin Bowes) Date: Fri, 30 Oct 2009 18:09:17 +0000 Subject: nanny processes remaing running when pulse stopped In-Reply-To: <1256922798.5025.23.camel@localhost.localdomain> References: <4AEB1C19.2070304@robinbowes.com> <1256922798.5025.23.camel@localhost.localdomain> Message-ID: <4AEB2BCD.8020509@robinbowes.com> On 30/10/09 17:13, Lon Hohberger wrote: > On Fri, 2009-10-30 at 17:02 +0000, Robin Bowes wrote: >> Hi, >> >> I've noticed that the nanny processes remaining running when the pulse >> daemon is stopped/restarted. So, if you restart pulse a few times, you >> end up with dozens of nanny processes. >> >> Surely this is not supposed to happen? Should pulse close all the nanny >> processes when it shutdown? > > It's supposed to shut them down. I'd file a bugzilla. Aha - known issue. https://bugzilla.redhat.com/show_bug.cgi?id=522230 I'm actually running pulse under runit, so I have added a finish script which runs "pkill /usr/sbin/nanny" when the service is shutdown. Nice to know I can remove that when this issue is fixed. R. From robin-lists at robinbowes.com Fri Oct 30 20:13:47 2009 From: robin-lists at robinbowes.com (Robin Bowes) Date: Fri, 30 Oct 2009 20:13:47 +0000 Subject: nanny processes remaing running when pulse stopped In-Reply-To: <4AEB2BCD.8020509@robinbowes.com> References: <4AEB1C19.2070304@robinbowes.com> <1256922798.5025.23.camel@localhost.localdomain> <4AEB2BCD.8020509@robinbowes.com> Message-ID: <4AEB48FB.1050909@robinbowes.com> On 30/10/09 18:09, Robin Bowes wrote: > > I'm actually running pulse under runit, so I have added a finish script > which runs "pkill /usr/sbin/nanny" when the service is shutdown. Nice to > know I can remove that when this issue is fixed. Just in case anyone reads this and thinks "Huh? That doesn't work.", the correct command is "pkill nanny" :) R. From tapan.thapa2000 at gmail.com Sat Oct 31 07:34:28 2009 From: tapan.thapa2000 at gmail.com (Tapan Thapa) Date: Sat, 31 Oct 2009 13:04:28 +0530 Subject: LVS Clustering Not working - Help Message-ID: <1dba33ef0910310034k7bdeb128s89aad41ba5ec3c9a@mail.gmail.com> Dear List Members, Since last three days i am trying to implement LVS through Piranha under testing but unfortunately i have no success. I have configured lvs.cf via piranha web interface and followed all instruction provided by the RHEL5_Virtual_Server_Administration.pdf for direct routing as well as NAT routing. My problem is pulse daemon is getting started properly and ips are also getting alias in Ethernet interfaces but when i am firing netstat command to see if port is listing as per my configuration then netstat command is not showing any port. My lvs.cf and netstat is attached. ipvsadm output: [root at lvs1 ~]# ipvsadm -L -n IP Virtual Server version 1.2.1 (size=4096) Prot LocalAddress:Port Scheduler Flags -> RemoteAddress:Port Forward Weight ActiveConn InActConn TCP 192.168.56.254:80 wlc persistent 600 -> 192.168.56.103:80 Route 1 0 0 netstat output [root at lvs1 ~]# netstat -an |grep 80 unix 3 [ ] STREAM CONNECTED 10580 /tmp/orbit-root/linc-a55-0-10162d195a1e1 unix 3 [ ] STREAM CONNECTED 9801 /var/run/dbus/system_bus_socket unix 3 [ ] STREAM CONNECTED 9800 unix 3 [ ] STREAM CONNECTED 7680 unix 2 [ ] DGRAM 7280 unix 2 [ ] DGRAM 6806 [root at lvs1 ~]# lvs.cf serial_no = 29 primary = 192.168.56.104 service = lvs backup_active = 0 backup = 0.0.0.0 heartbeat = 1 heartbeat_port = 539 keepalive = 6 deadtime = 18 network = direct nat_nmask = 255.255.255.255 debug_level = NONE virtual HTTP_Cluster { active = 1 address = 192.168.56.254 eth0:1 vip_nmask = 255.255.255.0 port = 80 persistent = 600 send = "GET / HTTP/1.0\r\n\r\n" expect = "HTTP" use_regex = 0 load_monitor = none scheduler = wlc protocol = tcp timeout = 6 reentry = 15 quiesce_server = 0 server real1.example.com { address = 192.168.56.103 active = 1 port = 80 weight = 1 } } I am unable to send port 80 traffic to its public ip as port is not listing. Please help... For you info i have tried nat and direct routing both and no luck. Regards Tapan Thapa -------------- next part -------------- An HTML attachment was scrubbed... URL: