Strange Tcpip trace entries

Hi,
I have some problems with TCP sockets, used by a QNX application to
deliver a big amount of data to a Linux or Windoze box.
Sometimes I see the TCP connection going down without a clear reason,
and in those cases the tracefile reports two entries like these:

May 31 09:00:44.929 3 00006005 00000667
May 31 09:00:44.929 3 00006005 00000000

As I can see in /etc/config/traceinfo, major number 0x00006 is used by
the Tcpip process (I use TCP/IP version 5), but the minor code 5 is
not associated to any error string.

Does anyone know what these strange trace entries mean?

Thanks in advance
Davide

“Ancri Davide” <nospam@please.me> wrote in message
news:c9fhpa$9ub$1@inn.qnx.com

Hi,
I have some problems with TCP sockets, used by a QNX application to
deliver a big amount of data to a Linux or Windoze box.
Sometimes I see the TCP connection going down without a clear reason,
and in those cases the tracefile reports two entries like these:

May 31 09:00:44.929 3 00006005 00000667
May 31 09:00:44.929 3 00006005 00000000

Try with /etc/config/traceinfo.net maybe it’s there.

As I can see in /etc/config/traceinfo, major number 0x00006 is used by
the Tcpip process (I use TCP/IP version 5), but the minor code 5 is
not associated to any error string.

Does anyone know what these strange trace entries mean?

Thanks in advance
Davide

Mario Charest wrote:

Try with /etc/config/traceinfo.net maybe it’s there.

Sorry, it isn’t.

/etc/config/traceinfo.net contains info about Net.*** drivers only,
not Socket/Tcpip infos.

Davide

Ancri Davide wrote:

Hi,
I have some problems with TCP sockets, used by a QNX application to
deliver a big amount of data to a Linux or Windoze box.
Sometimes I see the TCP connection going down without a clear reason,
and in those cases the tracefile reports two entries like these:

The minor code 5 means that the error being logged isn’t unexpected.

May 31 09:00:44.929 3 00006005 00000667

This says that the stack couldn’t allocate any mbufs to hold the
incoming packet (a request to grow the list of mbufs occurs, but the
packet is dropped).

May 31 09:00:44.929 3 00006005 00000000

The packet was dropped.

As I can see in /etc/config/traceinfo, major number 0x00006 is used by
the Tcpip process (I use TCP/IP version 5), but the minor code 5 is not
associated to any error string.

Does anyone know what these strange trace entries mean?

Thanks in advance
Davide

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

Adam Mallory wrote:

The minor code 5 means that the error being logged isn’t unexpected.

May 31 09:00:44.929 3 00006005 00000667


This says that the stack couldn’t allocate any mbufs to hold the
incoming packet (a request to grow the list of mbufs occurs, but the
packet is dropped).

May 31 09:00:44.929 3 00006005 00000000


The packet was dropped.

Thanks a lot…

Davide