Here is a snipped of the netstat -nape output. Let me know if you want more.
udp 0 0 0.0.0.0:25984 0.0.0.0:* 101 18640946 30742/python udp 0 0 0.0.0.0:25856 0.0.0.0:* 101 18271512 30742/python udp 0 0 0.0.0.0:25728 0.0.0.0:* 101 18163090 30742/python udp 0 0 0.0.0.0:25600 0.0.0.0:* 101 17826889 30742/python udp 0 0 0.0.0.0:25472 0.0.0.0:* 101 17506123 30742/python udp 0 0 0.0.0.0:25344 0.0.0.0:* 101 17448245 30742/python udp 0 0 0.0.0.0:25216 0.0.0.0:* 101 17140507 30742/python udp 0 0 0.0.0.0:25088 0.0.0.0:* 101 16861628 30742/python udp 0 0 0.0.0.0:25985 0.0.0.0:* 101 18641949 30742/python udp 0 0 0.0.0.0:25857 0.0.0.0:* 101 18272376 30742/python udp 0 0 0.0.0.0:25729 0.0.0.0:* 101 18163843 30742/python udp 0 0 0.0.0.0:25601 0.0.0.0:* 101 17827497 30742/python udp 0 0 0.0.0.0:25473 0.0.0.0:* 101 17506614 30742/python udp 0 0 0.0.0.0:25345 0.0.0.0:* 101 17448593 30742/python udp 0 0 0.0.0.0:25217 0.0.0.0:* 101 17140738 30742/python udp 0 0 0.0.0.0:25089 0.0.0.0:* 101 16861763 30742/python udp 0 0 0.0.0.0:25986 0.0.0.0:* 101 18642950 30742/python udp 0 0 0.0.0.0:25858 0.0.0.0:* 101 18273241 30742/python udp 0 0 0.0.0.0:25730 0.0.0.0:* 101 18164592 30742/python PID 30742 belongs to the process below. /opt/zenoss/bin/python /opt/zenoss/Products/DataCollector/zenmodeler.py --configfile /opt/zenoss/etc/zenmodeler.conf --cycle --daemon Thanks, Jared -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Newton Sent: Wednesday, February 21, 2007 6:54 AM To: General discussion of using zenoss system Subject: Re: [zenoss-users] UDP connection count Hi Jared, This should not be happening. Something is spawning children and not reaping them properly. Can you determine what processes are listening to these ports? As root: # netstat -nape This will get you the process id, and you can get the full process invocation like this: # ps auxww | grep PID If you could just tell me the port number(s), that would narrow it down. -Eric Jared Meeker wrote: > I just noticed that our Zenoss server has over 1000 "listening" UDP > connections. When I restart Zenoss the connections all clear out, then > over the case of just a few days there are over 1k of them again. > Everything seems to be running ok, but I'm just wondering if this will > eventually cause problems. Another side note is that there is a notable > increase every 12 hours or so. Is this normal behavior? > > > > I'm running version 1.1.0-2, on CentOS 4.4 using the rpm. > > > > > > - Jared Meeker > > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Greg Haygood > Sent: Tuesday, February 20, 2007 4:08 PM > To: General discussion of using zenoss system > Subject: Re: [zenoss-users] Zensyslog not starting > > > > i had a similar issue when i first started playing with zenoss. i > changed the device name of the monitor station from the fqdn to the > shortname, and everything started breaking. even when i changed back, > though, it couldn't recover. i didn't have anything invested yet, so i > just blew it away and started over. > > (NOT TESTED!) look in the DB (table heartbeat) and see if the value of > device matches the new hostname. if it's your public addr, use SQL to > update to the correct value: > > UPDATE heartbeat set device='newvalue' where device='oldvalue'; > > (replace newvalue & oldvalue accordingly) > > > > > On 2/20/07, Brent Wiese <[EMAIL PROTECTED]> wrote: > > After upgrading to 1.1.0, zensyslog no longer starts. > > Based on a similar post, I added -v10 to the generic line. > > Here is the output. Is this the culprit? I don't get anything after the > "started" line in any log I can find. > > Interestingly, the device I received email from changed after the > ugprade > from the PTR DNS ip of the public firewall interface this machine NAT's > through to the actual hostname of the zenoss box now. Could it be > related? > > I also changed the admin password after the upgrade. > > 2007-02-20 15:03:23 DEBUG zen.Events: EventClassInst=Start > 2007-02-20 15:03:23 DEBUG zen.Events: update status set clearid = > '0a6c85c134fc1362bfffffff' where device='ddd-phx-vma-1.3d24x7.com' and > component='zensyslog' and eventKey='' and (eventClass='/App/Stop' or > eventClass='/App/Start'): --> 0 > 2007-02-20 15:03:23 DEBUG zen.Events: insert into log (evid, userName, > text) > select evid, "admin", "auto cleared" from status where clearid = > "0a6c85c134fc1362bfffffff": --> 0 > 2007-02-20 15:03:23 DEBUG zen.Events: insert into history set > firstTime=1172009003.523,severity=0,component='zensyslog',summary='zensy > slog > started',dedupid='ddd-phx-vma-1.3d24x7.com|zensyslog|/App/Start||0|zensy > slog > started',manager='ddd-phx-vma-1.3d24x7.com',eventKey='',device='ddd-phx- > vma- > 1.3d24x7.com',eventClass='/App/Start',lastTime= > 1172009003.523,message='zensy > slog started',deletedTime=null,evid='0a6c85c134fc1362bfffffff': --> 1 > 2007-02-20 15:03:23 DEBUG zen.Events: DELETE FROM status WHERE clearid > IS > NOT NULL: --> 0 > 2007-02-20 15:03:23 INFO zen.ZenSyslog: started > > Thanks, > Brent > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users > > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
