Here's your backtrace dude... Jun 6 21:08:29 gw ntop[13720]: ntop caught signal 11 Jun 6 21:08:29 gw ntop[13720]: *****ntop error: Signal(11) Jun 6 21:08:29 gw ntop[13720]: backtrace is: Jun 6 21:08:29 gw ntop[13720]: 1. /lib/libpthread.so.0 [0x4021c567] Jun 6 21:08:29 gw ntop[13720]: 2. /lib/libc.so.6 [0x405217a8] Jun 6 21:08:29 gw ntop[13720]: 3. /usr/local/lib/libntop-2.0.so.99(getVendorInfo+0x29) [0x40294a45] Jun 6 21:08:29 gw ntop[13720]: 4. /usr/local/lib/libntop-2.0.so.99(mySQLnotifyHostCreation+0x12d) [0x4027e7bd] Jun 6 21:08:29 gw ntop[13720]: 5. /usr/local/lib/libntop-2.0.so.99(updateDbHostsTraffic+0xe0) [0x4028f858] Jun 6 21:08:29 gw ntop[13720]: 6. /usr/local/lib/libntop-2.0.so.99(updateDBHostsTrafficLoop+0x86) [0x40280902] Jun 6 21:08:29 gw ntop[13720]: 7. /lib/libpthread.so.0 [0x40219c04] Jun 6 21:08:29 gw ntop[13720]: 8. /lib/libc.so.6(__clone+0x3a) [0x405d950a] Jun 6 21:08:29 gw ntop[13720]: Cleaning up... Jun 6 21:08:29 gw ntop[13720]: Waiting until threads terminate... Jun 6 21:08:32 gw ntop[13720]: Freeing hash host instances... (3 device(s) to save)
root gw:~> psg ntop nobody 13714 1 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host nobody 13717 13714 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host nobody 13718 13717 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host nobody 13720 13717 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host nobody 13721 13717 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host nobody 13722 13717 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host nobody 13723 13717 0 20:55 ? 00:00:00 /usr/local/bin/ntop --mysql-host Parent process has hung waiting for child but on this occassion is still alive ! root gw:~> strace -p 13714 pause( root gw:~> strace -p 13720 --- SIGSTOP (Stopped (signal)) --- ----- Original Message ----- From: "Shaf Ali" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 06, 2002 9:03 PM Subject: Re: [Ntop] problems with -i command line parameter > > So it's dying, not rebooting the machine... ok... I've changed the > subject > > title to collect this for future reference. > > cool > > > > > Do you mean -I or -i? Because there is no -I in ntop. (I know, it's in > > theOpts in main.c, but that's wrong - and it should be giving a message, > > because there's nothing in the case statement to handle it. -I should > cause > > a "FATAL ERROR" message.) > > /usr/local/bin/ntop --mysql-host "ntop:foo:bar:localhost" -N -d -i > "eth0,eth1,eth2" -u nobody > FAILS > /usr/local/bin/ntop --mysql-host "ntop:foo:bar:localhost" -d -u nobody > IS STABLE > > > > > When it dies, where is it dying? Try running with -K - under gcc it will > > automatically put a backtrace in the log. It's not perfect, but it > usually > > gives a begining of a clue. > > OK in progress : > Previous run : Note it ran for more or less just 20 minutes this this > indicate anything ? > /usr/local/bin/ntop --mysql-host "ntop:foo:bar:localhost" -N -d -i > "eth0,eth1,eth2" -u nobody > > Jun 6 19:12:10 gw kernel: device eth0 left promiscuous mode > Jun 6 19:12:30 gw kernel: eth0: Promiscuous mode enabled. > Jun 6 19:12:30 gw kernel: device eth0 entered promiscuous mode > Jun 6 19:12:30 gw kernel: eth1: Promiscuous mode enabled. > Jun 6 19:12:30 gw kernel: device eth1 entered promiscuous mode > Jun 6 19:12:30 gw kernel: eth2: Promiscuous mode enabled. > Jun 6 19:12:30 gw kernel: device eth2 entered promiscuous mode > Jun 6 19:32:36 gw kernel: device eth0 left promiscuous mode > Jun 6 19:32:36 gw kernel: device eth1 left promiscuous mode > Jun 6 19:32:36 gw kernel: device eth2 left promiscuous mode > > > > > > I did mis-speak previously, however, without -i it looks like ntop will > > listen only on one device, whatever the 1st returned by pcap_lookupdev() > > is... > > > > Do you have netFlow or sFlow plugins active? (Those force the interfaces > > not to merge)? > > > Name Description Version Author Active > sFlow This plugin is used to tune ntop's sFlow support 1.1 L.Deri No > PDAPlugin ntop PDA Interface 1.1 W. Brock Yes > NetFlow This plugin is used to tune ntop's NetFlow support 1.1 L.Deri > Yes > nfsWatch This plugin handles NFS traffic 1.0 L.Deri No > LastSeen This plugin handles Last Seen Time Host 1.0 A.Marangoni No > icmpWatch This plugin handles ICMP packets 1.0 L.Deri Yes > > > > > > Also, check the Admin | Switch NIC page to make sure ntop is/is not > merging > > the interfaces. > > > > Done. not merging.. > > > > > It begins to sound like another case of the merge/indexing problem. > Getting > > the address where it's croaking (and the values of key variables) is > key... > > > > -----Burton > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Shaf > > Ali > > Sent: Thursday, June 06, 2002 2:04 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [Ntop] A reason for dying > > > > > > Yes I just had ntop die on me - it dies with the -I switch > > Going back to using ntop without any -i switches grrrr > > > > Here's the machine config : > > > > <snip> > > > > root gw:~> /usr/local/bin/ntop --version > > ntop v.2.0.99 MT (SSL) [i586-pc-linux-gnu] (05/23/02 07:32:36 PM build) > > > > root gw:~> cat /proc/pci > > Bus 0, device 17, function 0: > > Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev > 16). > > IRQ 5. > > Master Capable. Latency=64. Min Gnt=32.Max Lat=64. > > I/O at 0xd000 [0xd0ff]. > > Non-prefetchable 32 bit memory at 0xe5005000 [0xe50050ff]. > > Bus 0, device 19, function 0: > > Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (#2) > (rev > > 16). > > IRQ 12. > > Master Capable. Latency=64. Min Gnt=32.Max Lat=64. > > I/O at 0xe800 [0xe8ff]. > > Non-prefetchable 32 bit memory at 0xe5006000 [0xe50060ff]. > > Bus 0, device 20, function 0: > > Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (#3) > (rev > > 16). > > IRQ 11. > > Master Capable. Latency=64. Min Gnt=32.Max Lat=64. > > I/O at 0xec00 [0xecff]. > > Non-prefetchable 32 bit memory at 0xe5007000 [0xe50070ff]. > > > > Shaf > > > > > > ----- Original Message ----- > > From: "Devon Harding - GTHLA" <[EMAIL PROTECTED]> > > To: "'Burton M. Strauss III'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Sent: Thursday, June 06, 2002 6:55 PM > > Subject: RE: [Ntop] A reason for dying > > > > > > > Well I definitely know that -i has something to do with it. The minute > I > > > remove the option, ntop has been running for the last hour. Before, > ntop > > > would die in like 5min. > > > > > > Since I have multiple nic's, I'll try -M (without -i) to see what > happens > > > next. > > > > > > -Devon > > > > > > > > > > > _______________________________________________ > > Ntop mailing list > > [EMAIL PROTECTED] > > http://lists.ntop.org/mailman/listinfo/ntop > > > > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://lists.ntop.org/mailman/listinfo/ntop > _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://lists.ntop.org/mailman/listinfo/ntop
