HEX
Server: Apache
System: Linux vps-cdc32557.vps.ovh.ca 5.15.0-156-generic #166-Ubuntu SMP Sat Aug 9 00:02:46 UTC 2025 x86_64
User: hanode (1017)
PHP: 7.4.33
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
$ pwd: /usr/share/doc/iptraf-ng/Documentation/
Upload Files
File: //usr/share/doc/iptraf-ng/Documentation/x2335.html
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>  Resolving Process 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="UP"
TITLE="Messages"
HREF="a1980.html"><LINK
REL="PREVIOUS"
TITLE="Messages"
HREF="a1980.html"><LINK
REL="NEXT"
TITLE="GNU Free Documentation License"
HREF="a2377.html"></HEAD
><BODY
CLASS="SECT1"
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="a1980.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Appendix A. Messages</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="a2377.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="RVNAMEDMESSAGES"
>A.2. Resolving Process Messages</A
></H1
><P
>  Resolving process does not send messages to the screen. It
  writes its messages to the file <TT
CLASS="FILENAME"
>rvnamed-ng.log</TT
> in the
  IPTraf-ng log directory.</P
><DIV
CLASS="SIMPLEMSGENTRY"
><A
NAME="AEN2340"
></A
><P
><SAMP
CLASS="COMPUTEROUTPUT"
>  Unable to open child communication socket</SAMP
></P
><BLOCKQUOTE
CLASS="MSGEXPLAN"
>  Resolving process was unable to open the communication endpoint for
  data reception from the children it creates. This is highly unusual
  and should it occur, report the circumstances.</BLOCKQUOTE
></DIV
><DIV
CLASS="SIMPLEMSGENTRY"
><A
NAME="AEN2346"
></A
><P
><SAMP
CLASS="COMPUTEROUTPUT"
>  Unable to open client communication socket</SAMP
></P
><BLOCKQUOTE
CLASS="MSGEXPLAN"
>  Resolving process was unable to open the communication endpoint for
  data exchange with the IPTraf-ng program. This is highly unusual and
  should it occur, report the circumstances.</BLOCKQUOTE
></DIV
><DIV
CLASS="SIMPLEMSGENTRY"
><A
NAME="AEN2352"
></A
><P
><SAMP
CLASS="COMPUTEROUTPUT"
>  Error binding client communication socket
  Error binding child communication socket</SAMP
></P
><BLOCKQUOTE
CLASS="MSGEXPLAN"
>  Resolving process was unable to assign a name to the indicated
  communication socket. This may be due to a bad, full or corrupted
  filesystem.</BLOCKQUOTE
></DIV
><DIV
CLASS="SIMPLEMSGENTRY"
><A
NAME="AEN2358"
></A
><P
><SAMP
CLASS="COMPUTEROUTPUT"
>  Fatal error: no memory for descriptor monitoring</SAMP
></P
><BLOCKQUOTE
CLASS="MSGEXPLAN"
>  Resolving process ran out of memory. IPTraf-ng will resort to blocking
  and may freeze.</BLOCKQUOTE
></DIV
><DIV
CLASS="SIMPLEMSGENTRY"
><A
NAME="AEN2364"
></A
><P
><SAMP
CLASS="COMPUTEROUTPUT"
>  Error on fork, returning IP address</SAMP
></P
><BLOCKQUOTE
CLASS="MSGEXPLAN"
>  Resolving process had a problem spawning a copy of itself to resolve the IP
  address; it will simply return the IP address in its literal,
  dotted-decimal notation. IPTraf-ng will still function normally. This may
  be due to lack of memory or a process limit hit.</BLOCKQUOTE
></DIV
><DIV
CLASS="SIMPLEMSGENTRY"
><A
NAME="AEN2370"
></A
><P
><SAMP
CLASS="COMPUTEROUTPUT"
>  Maximum child process limit reached</SAMP
></P
><BLOCKQUOTE
CLASS="MSGEXPLAN"
>  Resolving process has reached its maximum number of child processes. This
  is intended as a "brake" to prevent too many children from hogging
  your computer's resources and possibly crashing it.  Unless IPTraf-ng is monitoring an extremely busy network without filters,
  this shouldn't happen, at least, not that often. If you notice
  this message, try applying filters or check your DNS server. Many times,
  this can happen when the DNS server goes down for whatever reason
  and you have resolving process children taking too long to resolve.</BLOCKQUOTE
></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="a1980.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="a2377.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Messages</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="a1980.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>GNU Free Documentation License</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
@ Telegram