File manager

File manager - Edit - /usr/share/doc/iptraf-ng/Documentation/a1980.html

Back
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >Messages</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REL="HOME" TITLE="IPTraf-ng User's Manual" HREF="index.html"><LINK REL="PREVIOUS" TITLE="Background Operation" HREF="c1957.html"><LINK REL="NEXT" TITLE=" Resolving Process Messages" HREF="x2335.html"></HEAD ><BODY CLASS="APPENDIX" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >IPTraf-ng User's Manual</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="c1957.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="x2335.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="APPENDIX" ><H1 ><A NAME="MESSAGES" ></A >Appendix A. Messages</H1 ><P >IPTraf-ng'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 <TT CLASS="FILENAME" >iptraf-ng.log</TT > file in the IPTraf-ng log directory (normally <TT CLASS="FILENAME" >/var/log/iptraf-ng</TT >.</P ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="IPTRAFMESSAGES" >A.1. IPTraf-ng Messages</A ></H1 ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN1988" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to create config file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot create the configuration file. The most likely cause of this is that you didn't properly install the program, and the necessary directory <TT CLASS="FILENAME" >/var/local/iptraf-ng</TT > does not exist. Can also be generated if you have a disk problem or if you have too many files open.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN1995" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to read config file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The configuration record cannot be read. You most likely have a disk problem.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2001" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to write config file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The configuration file cannot be written. You either have a disk problem, or (more likely), your disk is full.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2007" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Enter an appropriate description for this filter</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > Enter something to clearly describe the filter you are defining. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2013" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Error loading filter list file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot access the list of defined TCP or UDP filters. Can also be an indicator of a bad disk.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2019" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Error writing filter list file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The filter list file cannot be written to. You may have trouble accessing your filters. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2025" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to read TCP/UDP/misc IP filter file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot read the filter data off the file. Could be caused by a bad disk. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2031" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Error opening filter data file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot open the filter file. Could be caused by a shortage of file descriptors or a bad disk.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2037" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to write filter data</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot add the newly defined filter to the filter list. This may be due to a bad disk.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2043" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Cannot create filter data file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot create the filter record file. The defined filter is lost.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2049" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to save filter changes</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot save the changes you made to the filter. You probably have a disk error.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2055" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to write filter state information</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The current state of the filters cannot be saved. IPTraf-ng 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.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2061" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to save interface flags</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to save the flags of the network interfaces. This is probably due to a bad installation or full filesystem.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2067" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to retrieve saved interface flags</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to retrieve the save interface flags. Probably again due to a bad installation or full filesystem.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2073" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" ><TT CLASS="REPLACEABLE" ><I >protocol</I ></TT > filter data file in use; try again later</SAMP ></P ><P ><SAMP CLASS="COMPUTEROUTPUT" >Filter state file in use; try again later</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > Another IPTraf-ng 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-ng process has terminated or completed its modifications and unlocked the files.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2082" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to resolve hostname</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The indicated host name in the filter cannot be resolved into an IP address. Check the local hosts database <TT CLASS="FILENAME" >/etc/hosts</TT > or your machine's DNS configuration or DNS server. The filter parameters will not be used.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2090" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to open host description file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng 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. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2096" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to write host description</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to write the description record for this Ethernet or FDDI address. Could be due to a bad disk or corrupted filesystem. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2102" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >No descriptions </SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > You tried to edit or delete a description with no previous descriptions defined. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2108" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Cannot open log file</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > There is a problem opening the log file. There is most likely a problem with the disk, or there are too many open files. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2114" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to obtain interface list</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to retrieve the list of network interfaces from the <TT CLASS="FILENAME" >/proc</TT > filesystem. This may be due to a badly configured kernel. IPTraf-ng needs <TT CLASS="FILENAME" >/proc</TT > filesystem support. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2122" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >No active interfaces. Check their status or the /proc filesystem.</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng found no active interfaces. Either all interfaces are down or the <TT CLASS="FILENAME" >/proc/net/dev</TT > file was empty or unavailable. Activate at least one interface or check the <TT CLASS="FILENAME" >/proc/net/dev</TT > file. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2130" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to obtain interface parameters for interface</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The system call to retrieve the interface's flags failed. Check your interface or kernel driver. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2136" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Promisc change failed for interface</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The system call to change the promiscuous flag failed. Check your interface or its kernel driver. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2142" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to open raw socket for flag change</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to open the necessary socket for the promiscuous change operation. May be due to a shortage of file descriptors. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2148" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to open socket for MTU determination</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > Returned by the facility for detailed interface statistics if the raw socket's opening sequence failed. The facility will abort.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2154" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to open raw socket</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to open the raw socket for packet capture. May be due to a shortage of file descriptors.<DIV CLASS="NOTE" ><P ></P ><TABLE CLASS="NOTE" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TH ALIGN="LEFT" VALIGN="MIDDLE" ><B >Reminder</B ></TH ></TR ><TR ><TD > </TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > 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.</P ></TD ></TR ></TABLE ></DIV ></BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2163" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Unable to obtain interface MTU</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The detailed statistics facility was unable to obtain the maximum transmission unit (MTU) for the selected interface. The facility will abort. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2169" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Specified interface not supported</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The interface specified with the <SAMP CLASS="COMPUTEROUTPUT" >-i</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-d</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-s</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-l</SAMP >, or <SAMP CLASS="COMPUTEROUTPUT" >-z</SAMP > command-line parameters is not supported by IPTraf-ng.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2180" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Specified interface not active</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The interface specified with the <SAMP CLASS="COMPUTEROUTPUT" >-i</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-d</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-s</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-l</SAMP >, or <SAMP CLASS="COMPUTEROUTPUT" >-z</SAMP > command-line parameters is supported, but not currently activated. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2191" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Fatal: memory allocation error</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > May occur if you have too little memory to allocate for windows, the menu system, or dialog boxes. IPTraf-ng 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.<DIV CLASS="NOTE" ><P ></P ><TABLE CLASS="NOTE" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TH ALIGN="LEFT" VALIGN="MIDDLE" ><B >Technical note</B ></TH ></TR ><TR ><TD > </TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P >This is actually a response to the segmentation fault error (SIGSEGV).</P ></TD ></TR ></TABLE ></DIV ></BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2200" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >This program can be run only by the system administrator</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng 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 </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2206" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Your TERM variable is not set</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The <CODE CLASS="ENVAR" >TERM</CODE > (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 <CODE CLASS="ENVAR" >TERM</CODE > variables set to <SAMP CLASS="COMPUTEROUTPUT" >linux</SAMP >. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2215" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Received TERM signal</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > Not related to the previous message. The <SAMP CLASS="COMPUTEROUTPUT" >TERM</SAMP > (terminate) signal is normally used to gracefully shut down a program. This message simply indicates that the <SAMP CLASS="COMPUTEROUTPUT" >TERM</SAMP > signal was caught and IPTraf-ng is attempting to shut down as gracefully as possible.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2223" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" > Invalid option or missing parameter, use iptraf-ng -h for help</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The <SAMP CLASS="COMPUTEROUTPUT" >-i</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-d</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-s</SAMP >, <SAMP CLASS="COMPUTEROUTPUT" >-l</SAMP >, or <SAMP CLASS="COMPUTEROUTPUT" >-z</SAMP > options were specified but no interface was specified on the command line. These parameters require a valid interface name (or <SAMP CLASS="COMPUTEROUTPUT" >all</SAMP > for <SAMP CLASS="COMPUTEROUTPUT" >-i</SAMP > or <SAMP CLASS="COMPUTEROUTPUT" >-l</SAMP >). This message also appears if an unknown option is passed to the <B CLASS="COMMAND" >iptraf-ng</B > command. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2239" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Warning: unable to tag this process</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng 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 <B CLASS="COMMAND" >make install</B > procedure or the <B CLASS="COMMAND" >Setup</B > in the distribution's top-level directory. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2247" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Warning: unable to tag facility</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to create the tag file for the facility you started. The facility will still run, but other instances of IPTraf-ng 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. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2253" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" ><TT CLASS="REPLACEABLE" ><I >facility</I ></TT > already running/listening on interface</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The facility you tried to start is currently running on the indicated interface in another IPTraf-ng process on the machine. This restriction is placed to prevent conflicts involving internal sockets or the log files. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2260" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >General interface statistics already active in another process</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > Only one instance of the general interface statistics can run at a time. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2266" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Duplicate port/range entry </SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > 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 </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2272" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >No custom ports</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > There are no ports or port ranges earlier added. There's nothing to delete. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2278" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Can't get communication sockets; lookups will block</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot communicate with the resolving process. IPTraf-ng will fall back to blocking lookups. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2284" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Can't spawn new process; lookups will block</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot start a new process. This may be due to memory shortage. IPTraf-ng will fall back to blocking lookups. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2290" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Fork error, IPTraf-ng cannot run in background</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng cannot start a new process, and can go into the background. This may be due to memory shortage. IPTraf-ng aborts. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2296" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >No memory for new filter entry</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > IPTraf-ng was unable to allocate memory for a new filter entry. Most likely due to memory shortage. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2302" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Memory Low</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > 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.<DIV CLASS="NOTE" ><P ></P ><TABLE CLASS="NOTE" WIDTH="100%" BORDER="0" ><TR ><TD WIDTH="25" ALIGN="CENTER" VALIGN="TOP" ><IMG SRC="../images/note.gif" HSPACE="5" ALT="Note"></TD ><TH ALIGN="LEFT" VALIGN="MIDDLE" ><B >Note</B ></TH ></TR ><TR ><TD > </TD ><TD ALIGN="LEFT" VALIGN="TOP" ><P > 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-ng or other applications will abort due to the failure of important system calls or library functions. Memory must be added right away.</P ></TD ></TR ></TABLE ></DIV ></BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2311" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >IPC Error</SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > This indicator appears if an error occurs receiving data from the resolving process (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 <TT CLASS="FILENAME" >rvnamed-ng.log</TT > file. </BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2318" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >Error opening terminal: <TT CLASS="REPLACEABLE" ><I >terminal</I ></TT ></SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" > The screen management routines cannot find the <TT CLASS="FILENAME" >terminfo</TT > entry for your terminal. IPTraf-ng expects the terminfo database located in <TT CLASS="FILENAME" >/usr/share/terminfo</TT >. This error could occur when your terminfo database is located somewhere else. See the section on controlling the <TT CLASS="FILENAME" >terminfo</TT > search path.</BLOCKQUOTE ></DIV ><DIV CLASS="SIMPLEMSGENTRY" ><A NAME="AEN2329" ></A ><P ><SAMP CLASS="COMPUTEROUTPUT" >This will end your IPTraf-ng session </SAMP ></P ><BLOCKQUOTE CLASS="MSGEXPLAN" >In interactive mode IPTraf-ng asks you to confirm your exit command. Press Enter to return to the shell or any other key to cancel your command and return to the main menu.</BLOCKQUOTE ></DIV ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="c1957.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="x2335.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Background Operation</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" > </TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Resolving Process Messages</TD ></TR ></TABLE ></DIV ></BODY ></HTML >

| ver. 1.4 | Github | . | PHP 7.4.33 | Generation time: 0.41 | proxy | phpinfo | Settings