What is a tracinfo 00006005? It’s not in the /etc/config/traceinfo files
here (dated 1998).
We are having network problems and are seeing lots of pairs such as the
following:
Jan 28 10:32:21 3 00006005 00000667
Jan 28 10:32:21 3 00006005 00000000
sin ver for Tcpip → 5.00C Dec 09 2002
TIA
Richard
“Richard Kramer” <rrkramer@kramer-smilko.com> wrote in message
news:b16bfj$d5g$1@inn.qnx.com…
What is a tracinfo 00006005? It’s not in the /etc/config/traceinfo files
here (dated 1998).
Try traceinfo -e /etc/config/traceinfo.net (file location from memory)
We are having network problems and are seeing lots of pairs such as the
following:
Jan 28 10:32:21 3 00006005 00000667
Jan 28 10:32:21 3 00006005 00000000sin ver for Tcpip → 5.00C Dec 09 2002
TIA
Richard
Mario Charest wrote:
“Richard Kramer” <> rrkramer@kramer-smilko.com> > wrote in message
news:b16bfj$d5g$> 1@inn.qnx.com> …What is a tracinfo 00006005? It’s not in the /etc/config/traceinfo files
here (dated 1998).
Try traceinfo -e /etc/config/traceinfo.net (file location from memory)
Not there - that’s all Net stuff; this is Tcpip. There are entries in
the normal traceinfo file for major #6 but none for minor #5.
Richard
We are having network problems and are seeing lots of pairs such as the
following:
Jan 28 10:32:21 3 00006005 00000667
Jan 28 10:32:21 3 00006005 00000000sin ver for Tcpip → 5.00C Dec 09 2002
TIA
Richard
\
Would someone from QNX please respond (I’d post to the beta group but it
seems to have disappeared):
Two recent failures have been preceeded by this trace sequence
Jan 30 09:27:50 3 00006005 99000002
Jan 30 09:27:50 3 00006005 97000002
Jan 30 09:27:50 3 00006005 97000002
Jan 30 09:27:50 3 00006005 99000001
Jan 30 09:27:50 3 00006005 97000001
Jan 30 09:27:50 3 00006005 97000001
The sequence I reported earlier below occurs throughout the day with no
noticeable effect.
Richard
Richard Kramer wrote:
Mario Charest wrote:
“Richard Kramer” <> rrkramer@kramer-smilko.com> > wrote in message
news:b16bfj$d5g$> 1@inn.qnx.com> …What is a tracinfo 00006005? It’s not in the /etc/config/traceinfo files
here (dated 1998).
Try traceinfo -e /etc/config/traceinfo.net (file location from memory)Not there - that’s all Net stuff; this is Tcpip. There are entries in
the normal traceinfo file for major #6 but none for minor #5.Richard
We are having network problems and are seeing lots of pairs such as the
following:
Jan 28 10:32:21 3 00006005 00000667
Jan 28 10:32:21 3 00006005 00000000sin ver for Tcpip → 5.00C Dec 09 2002
TIA
Richard
\
Richard Kramer <rrkramer@kramer-smilko.com> wrote in message
news:b1bg4q$bjq$1@inn.qnx.com…
Would someone from QNX please respond (I’d post to the beta group but it
seems to have disappeared):
The beta425 group is still there. FYI, if you require support in a certain
timeframe, you should use the offical channels of support.
The /etc/config/traceinfo files are used in formating the data, non lists
codes aren’t formatted. The list of major/minor codes is located in
/usr/include/sys/tracecod.h .
Two recent failures have been preceeded by this trace sequence
Jan 30 09:27:50 3 00006005 99000002
Jan 30 09:27:50 3 00006005 97000002
Jan 30 09:27:50 3 00006005 97000002
Jan 30 09:27:50 3 00006005 99000001
Jan 30 09:27:50 3 00006005 97000001
Jan 30 09:27:50 3 00006005 97000001
The 9900 0002, 9900 0001, and 9700 00002 refer to the network interface
setup onto a LAN. The 0000 0667 code says that mbufs where exhausted and
more had to be carved out, and 0000 0000 just is a trace of a drop from code
0000 0667. In all cases, they are for debugging the stack, and the errors
are expected/transient.
-Adam
Thanks (I had thought the beta was dead).
Adam Mallory wrote:
Richard Kramer <> rrkramer@kramer-smilko.com> > wrote in message
news:b1bg4q$bjq$> 1@inn.qnx.com> …Would someone from QNX please respond (I’d post to the beta group but it
seems to have disappeared):
The beta425 group is still there. FYI, if you require support in a certain
timeframe, you should use the offical channels of support.The /etc/config/traceinfo files are used in formating the data, non lists
codes aren’t formatted. The list of major/minor codes is located in
/usr/include/sys/tracecod.h .
Two recent failures have been preceeded by this trace sequence
Jan 30 09:27:50 3 00006005 99000002
Jan 30 09:27:50 3 00006005 97000002
Jan 30 09:27:50 3 00006005 97000002
Jan 30 09:27:50 3 00006005 99000001
Jan 30 09:27:50 3 00006005 97000001
Jan 30 09:27:50 3 00006005 97000001
The 9900 0002, 9900 0001, and 9700 00002 refer to the network interface
setup onto a LAN. The 0000 0667 code says that mbufs where exhausted and
more had to be carved out, and 0000 0000 just is a trace of a drop from code
0000 0667. In all cases, they are for debugging the stack, and the errors
are expected/transient.-Adam
“Richard Kramer” <rrkramer@kramer-smilko.com> wrote in message
news:b1cgb4$gaa$1@inn.qnx.com…
Thanks (I had thought the beta was dead).
I have seen some problems with the TCP/IP beta group too, sometimes it’s
there, sometimes it isn’t. Now it’s there, but there are only 2 messages. I
told our IS depertment… Maybe they removed all the old messages and
re-created it or something, who knows.
-Martin.
Martin Walter wrote:
“Richard Kramer” <> rrkramer@kramer-smilko.com> > wrote in message
news:b1cgb4$gaa$> 1@inn.qnx.com> …Thanks (I had thought the beta was dead).
I have seen some problems with the TCP/IP beta group too, sometimes it’s
there, sometimes it isn’t. Now it’s there, but there are only 2 messages. I
told our IS depertment… Maybe they removed all the old messages and
re-created it or something, who knows.
The fact that it requires a login and password which are different than
the qnx425’s group has been a bloody nuisance since I have to just about
re-boot the machine to get access to the one if I had logged into the
other. In other words, I, for one, don’t miss it.
-Martin.