<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Dirk Koopman wrote:
<blockquote cite="mid1134657164.32615.113.camel@dirk3.int.tobit.co.uk"
type="cite">
<pre wrap="">On Mon, 2005-11-28 at 16:40 -0500, Alan D. Snyder wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi
When someone is locally connected to my node and sends me a talk
message, I don't receive it. It used to work, but haven't upgrade
version in a while
running DXSpider V1.51 build 59.374
Have issued 'set/talk' and 'set/anntalk' but to no avail
The debug files show the incoming talk message request, but nil for
what should be the propagated outgoing
Any ideas?
</pre>
</blockquote>
<pre wrap=""><!---->
None at all. There isn't really any information here to diagnose the
problem. I understand that you have fixed the problem by restarting the
node. However, that would not explain why it happened in the first
place. In principle: there is no state retained in talk messages that a
restart would fix.
What version of perl are you running? In a shell, do:
$ perl -v
</pre>
</blockquote>
the output is attached (the file is named 'p')<br>
<br>
<br>
<blockquote cite="mid1134657164.32615.113.camel@dirk3.int.tobit.co.uk"
type="cite">
<pre wrap="">
Generally if you want to diagnose a protocol issue of this kind, it is
worth doing a:
set/debug chanerr
This will output messages to the debug log as to why certain messages
are ignored, you can stop these (rather verbose) extra messages by doing
a:
unset/debug chanerr
Dirk
_______________________________________________
Dxspider-support mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@dxcluster.org">Dxspider-support@dxcluster.org</a>
<a class="moz-txt-link-freetext" href="http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">http://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
<font face="Comic Sans MS">Dirk - <br>
<br>
When I examined the debug output files I saw the "I"nbound <- Talk
line but spider never attempted to "D"eliver the msg<br>
<br>
The node was up for a few months when it started to sink talk messages.
At that time the node was experiencing all sorts of partner disconnects
due to the DSL modem losing synch with the ISP, so perhaps the node
itself was in an odd state??<br>
<br>
Without retained state information over a reboot, I agree that it would
be hard to diagnose.<br>
<br>
I've heard before, anecdotally, from N3RD that the 'init' command is
sometimes necessary to restore a node to passing Talk messages, but
this node didn't respond.<br>
<br>
When it was sinking talk messages, I even tried a local telnet session
with a phantom call but talk messages were treated the same. So I
concluded that it had nothing to do with remote or local clients. We
never tried talk from a client connected to a partner node then to here.<br>
<br>
Oh well ...<br>
<br>
Thank you very much for the hint (un)set/debug chanerr. If if recurs,
will work with the debug output and share it with you for diagnosis.<br>
<br>
By the way, it is a pretty slick product! Congrats on a job well done<br>
<br>
<br>
Best,<br>
Alan KF3B<br>
<br>
<br>
<br>
</font><br>
</body>
</html>