IPTraf's messages are presented in two ways. In interactive mode, messages are displayed in a distictive message box. In daemon (background) mode, appropriate messages are written to the iptraf.log file in the IPTraf log directory (normally /var/log/iptraf.
Unable to create config file
IPTraf cannot create the configuration file. The most likely cause of this is that you didn't properly install the program, and the necessary directory /var/local/iptraf does not exist. Can also be generated if you have a disk problem or if you have too many files open.
Unable to read config file
The configuration record cannot be read. You most likely have a disk problem.
Unable to write config file
The configuration file cannot be written. You either have a disk problem, or (more likely), your disk is full.
Enter an appropriate description for this filter
Enter something to clearly describe the filter you are defining.
Error loading filter list file
IPTraf cannot access the list of defined TCP or UDP filters. Can also be an indicator of a bad disk.
Error writing filter list file
The filter list file cannot be written to. You may have trouble accessing your filters.
Unable to read TCP/UDP/misc IP filter file
IPTraf cannot read the filter data off the file. Could be caused by a bad disk.
Error opening filter data file
IPTraf cannot open the filter file. Could be caused by a shortage of file descriptors or a bad disk.
Unable to write filter data
IPTraf cannot add the newly defined filter to the filter list. This may be due to a bad disk.
Cannot create filter data file
IPTraf cannot create the filter record file. The defined filter is lost.
Unable to save filter changes
IPTraf cannot save the changes you made to the filter. You probably have a disk error.
Unable to write filter state information
The current state of the filters cannot be saved. IPTraf will be unable to correctly reload the filters the next time it's started. This can be caused by a bad disk or improper installation.
Unable to save interface flags
IPTraf was unable to save the flags of the network interfaces. This is probably due to a bad installation or full filesystem.
Unable to retrieve saved interface flags
IPTraf was unable to retrieve the save interface flags. Probably again due to a bad installation or full filesystem.
protocol filter data file in use; try again later
Filter state file in use; try again later
Another IPTraf process is modifying the TCP, UDP or miscellaneous IP filter data or the filter state file and has locked the files or file. Try again once the other IPTraf process has terminated or completed its modifications and unlocked the files.
Unable to resolve hostname
The indicated host name in the filter cannot be resolved into an IP address. Check the local hosts database /etc/hosts or your machine's DNS configuration or DNS server. The filter parameters will not be used.
Unable to open host description file
IPTraf cannot open the file containing the descriptions for Ethernet or FDDI addresses. Could be due to a bad disk or a hit on the file descriptor limit.
Unable to write host description
IPTraf was unable to write the description record for this Ethernet or FDDI address. Could be due to a bad disk or corrupted filesystem.
Cannot open log file
There is a problem opening the log file. There is most likely a problem with the disk, or there are too many open files.
Unable to obtain interface list
IPTraf was unable to retrieve the list of network interfaces from the /proc filesystem. This may be due to a badly configured kernel. IPTraf needs /proc filesystem support.
No active interfaces. Check their status or the /proc filesystem.
IPTraf found no active interfaces. Either all interfaces are down or the /proc/net/dev file was empty or unavailable. Activate at least one interface or check the /proc/net/dev file.
Unable to obtain interface parameters for interface
The system call to retrieve the interface's flags failed. Check your interface or kernel driver.
Promisc change failed for interface
The system call to change the promiscuous flag failed. Check your interface or its kernel driver.
Unable to open raw socket for flag change
IPTraf was unable to open the necessary socket for the promiscuous change operation. May be due to a shortage of file descriptors.
Unable to open socket for MTU determination
Returned by the facility for detailed interface statistics if the raw socket's opening sequence failed. The facility will abort.
Unable to open raw socket
IPTraf was unable to open the raw socket for packet capture. May be due to a shortage of file descriptors.
IPTraf 2.x.x requires Linux kernel 2.2.x, with the Packet Socket option compiled in or installed as a module. IPTraf 2.x will return this error on a pre-2.2 kernel or on a 2.2 kernel without Packet Socket.
Unable to obtain interface MTU
The detailed statistics facility was unable to obtain the maximum transmission unit (MTU) for the selected interface. The facility will abort.
Specified interface not supported
The interface specified with the -i, -d, -s, -l, or -z command-line parameters is not supported by IPTraf.
Specified interface not active
The interface specified with the -i, -d, -s, -l, or -z command-line parameters is supported, but not currently activated.
Fatal: memory allocation error
May occur if you have too little memory to allocate for windows, the menu system, or dialog boxes. IPTraf tries to prevent further allocations if memory runs out during a monitor. However, this could also mean a bug if you're reasonably sure you're not out of memory. An instructional message on bug reporting follows this message.
This is actually a response to the segmentation fault error (SIGSEGV).
This program can be run only by the system administrator
IPTraf normally does not allow anybody but uid 0 (root) to run it. This measure is included for safety reasons. See the section on recompiling the program below if you want to override this. This feature is built in, and not part of the configuration
Your TERM variable is not set
The TERM (terminal type) environment variable must be set to a valid terminal type so that the screen management routines can function properly. Set it to the appropriate terminal type. Linux consoles typically have their TERM variables set to linux.
Received TERM signal
Not related to the previous message. The TERM (terminate) signal is normally used to gracefully shut down a program. This message simply indicates that the TERM signal was caught and IPTraf is attempting to shut down as gracefully as possible.
Invalid option or missing parameter, use iptraf -h for help
The -i, -d, -s, -l, or -z options were specified but no interface was specified on the command line. These parameters require a valid interface name (or all for -i or -l). This message also appears if an unknown option is passed to the iptraf command.
Warning: unable to tag this process
IPTraf normally tags itself when it runs to prevent multiple instances of the statistical facilities from running. This message means the program was unable to create the necessary tag file. This may be due to a bad or improper installation. Try running the make install procedure or the Setup in the distribution's top-level directory.
Warning: unable to tag facility
IPTraf was unable to create the tag file for the facility you started. The facility will still run, but other instances of IPTraf that may be running simultaneously will allow the same facility to run. This may cause both instances of the facility to malfunction. This could be due to a bad disk or bad installation.
facility already running/listening on interface
The facility you tried to start is currently running on the indicated interface in another IPTraf process on the machine. This restriction is placed to prevent conflicts involving internal sockets or the log files.
General interface statistics already active in another process
Only one instance of the general interface statistics can run at a time.
Duplicate port/range entry
You entered a port number or range that was already added to the list of additional ports to be monitored by the TCP/UDP service monitor
Can't start rvnamed; lookups will block
IPTraf cannot start the rvnamed daemon; probably due to a bad installation. IPTraf will fall back to blocking lookups.
Can't spawn new process; lookups will block
IPTraf cannot start a new process. This may be due to memory shortage. IPTraf will fall back to blocking lookups.
Fork error, IPTraf cannot run in background
IPTraf cannot start a new process, and can go into the background. This may be due to memory shortage. IPTraf aborts.
No memory for new filter entry
IPTraf was unable to allocate memory for a new filter entry. Most likely due to memory shortage.
This indicator appears if memory runs low due to a lot of entries in a facility. Should critical functions fail (window creation, internal allocation), the program could terminate with a segmentation violation.
Any message or indicator about low memory means that your system does not have enough memory to handle the entries. It is almost certain that sooner or later, IPTraf or other applications will abort due to the failure of important system calls or library functions. Memory must be added right away.
This indicator appears if an error occurs receiving data from the rvnamed program (IPC stands for Interprocess Communication). This indication should not occur under normal circumstances. Report instances of this condition and the circumstances under which it happens. You may also include data from the rvnamed.log file.
Error opening terminal: terminal
The screen management routines cannot find the terminfo entry for your terminal. IPTraf expects the terminfo database located in /usr/share/terminfo. This error could occur when your terminfo database is located somewhere else. See the section on controlling the terminfo search path.