intop exits with a segmentation fault within 1 second
of starting the program. I use the command line
[root@lochness /root]# intop -i eth3
to start the program. I have reviewed the FAQ and the
user & dev archives back to January 2002, but I haven't
found a description of a similar problem. (Pointers
to overlooked information gratefully accepted.)
If the source of my problem isn't immediately obvious,
I'd be pleased to receive helpful suggestions about how
to gather addtional information which could help narrow
down what's going wrong.
Here's the complete output I see:
[root@lochness /root]# intop -i eth3
-- intop 0.0.1 (Jun 11 2002) -- The first interactive ntop program.
(C) Copyright 2000 L. Deri and R. Carbone. All rights reserved.
It allows you to control the power of ntop using fingers rather than mouse!
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
Initializing intop engine.... Please wait.
Segmentation fault (core dumped)
[root@lochness /root]#
Configuration information follows:
Hardware
Type & # of processors 1 AMD K6-2 550 Mhz
Amount of memory 128 Mbytes
# network interfaces and types 4 Linksys PCI interfaces
Software
NTop version, etc. ntop-2.0.99-rc2.tar
openssl-0.9.6d.tar
libpcap-0.7.1.tar
Linux vendor & version Red Hat 6.2
Any major upgrades no
gcc version (e.g. gcc --version) egcs-2.91.66
glibc version glibc-2.1.3-15 (from RPM -q -a)
What else is running Not much, but see output from
ps -Af at end of message.
(This is one of 3-4 dozen
similarly configured linux
systems in the computer room
adjacent to the lab. I chose
it because it is lightly used.)
Network
Telnet access to this system is via eth0, which is connected through
Ethernet switches and a router to the corporate network. eth1 & eth2 are
unused at the current time. eth3 is the port used by ntop. eth3
is connected to a Fast Ethernet hub (a real hub, floods to all ports,
not a switch). There are two of our own devices connected to the same
hub; it is traffic to and from those devices which we wish to monitor.
The 4th connection to the hub is an upstream connection to an
Ethernet switch to the corporate network. So this means that I would
expect to see a fair amount of broadcast traffic (DHCP, ARP) but directed
traffic only to and from the two of our own devices.
[root@lochness log]# ps -Af
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 06:28 ? 00:00:05 init [3]
root 2 1 0 06:28 ? 00:00:00 [kflushd]
root 3 1 0 06:28 ? 00:00:00 [kupdate]
root 4 1 0 06:28 ? 00:00:00 [kpiod]
root 5 1 0 06:28 ? 00:00:00 [kswapd]
root 6 1 0 06:29 ? 00:00:00 [mdrecoveryd]
bin 544 1 0 06:29 ? 00:00:00 portmap
root 559 1 0 06:29 ? 00:00:00 [lockd]
root 560 559 0 06:29 ? 00:00:00 [rpciod]
root 569 1 0 06:29 ? 00:00:00 rpc.statd
root 583 1 0 06:29 ? 00:00:00 /usr/sbin/apmd -p 10 -w 5
-W -s
root 598 1 0 06:29 ? 00:00:00 ypbind (master)
root 603 598 0 06:29 ? 00:00:00 ypbind (slave)
root 642 1 0 06:29 ? 00:00:00 /usr/sbin/automount
--timeout 60
root 646 1 0 06:29 ? 00:00:00 /usr/sbin/automount
--timeout 60
root 665 1 0 06:29 ? 00:00:00 /usr/sbin/automount
--timeout 60
root 717 1 0 06:29 ? 00:00:00 syslogd -m 0
root 726 1 0 06:29 ? 00:00:00 klogd
nobody 740 1 0 06:30 ? 00:00:00 identd -e -o
nobody 744 740 0 06:30 ? 00:00:00 identd -e -o
nobody 745 744 0 06:30 ? 00:00:00 identd -e -o
nobody 746 744 0 06:30 ? 00:00:00 identd -e -o
nobody 747 744 0 06:30 ? 00:00:00 identd -e -o
daemon 758 1 0 06:30 ? 00:00:00 /usr/sbin/atd
root 772 1 0 06:30 ? 00:00:00 crond
root 790 1 0 06:30 ? 00:00:00 inetd
root 804 1 0 06:30 ? 00:00:00 lpd
root 852 1 0 06:30 ? 00:00:00 sendmail: accepting
connections
root 867 1 0 06:30 ? 00:00:00 gpm -t ps/2
xfs 906 1 0 06:30 ? 00:00:00 xfs -droppriv -daemon -port -1
root 944 1 0 06:30 tty2 00:00:00 /sbin/mingetty tty2
root 945 1 0 06:30 tty3 00:00:00 /sbin/mingetty tty3
root 946 1 0 06:30 tty4 00:00:00 /sbin/mingetty tty4
root 947 1 0 06:30 tty5 00:00:00 /sbin/mingetty tty5
root 948 1 0 06:30 tty6 00:00:00 /sbin/mingetty tty6
root 970 790 0 07:51 ? 00:00:00 in.telnetd:
kes.celoxnetworks.co
root 971 970 0 07:51 pts/0 00:00:00 login -- johnson
johnson 975 971 0 07:51 pts/0 00:00:00 -tcsh
root 1007 975 0 07:51 pts/0 00:00:00 su -
root 1008 1007 0 07:51 pts/0 00:00:00 -bash
root 1240 1 0 08:19 tty1 00:00:00 /sbin/mingetty tty1
root 1362 790 0 09:28 ? 00:00:00 in.telnetd:
kes.celoxnetworks.co
root 1363 1362 0 09:28 pts/1 00:00:00 login -- johnson
johnson 1364 1363 0 09:28 pts/1 00:00:00 -tcsh
root 1396 1364 0 09:28 pts/1 00:00:00 su -
root 1397 1396 0 09:28 pts/1 00:00:00 -bash
root 1432 1397 0 09:33 pts/1 00:00:00 ps -Af
Ken Johnson [EMAIL PROTECTED]
Celox Networks 314 439 8487 Ken Johnson
940 Westport Plaza Drive
Suite 300 314 439 8300 Main number
St. Louis, MO 63146 314 317 8949 fax
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://lists.ntop.org/mailman/listinfo/ntop
