Subj : binkstats.ini error messages
To : Khronos
From : Digital Man
Date : Tue Feb 06 2024 06:04 pm
Re: binkstats.ini error messages
By: Khronos to All on Tue Feb 06 2024 02:19 pm
> Hi,
> I am setting up a peer and I get the following messages in the binkstats.ini
> file.
> I get a callout failure even though the traffic appears to be sent properly
> somehow.
>
> [callout failure: 38:585/1@fu-net]
> oper = Jason Bock
> AKAs =
> 1:267/310@fidonet.,1:1/101@fidonet.,1:267/311@fidonet.,10:101/10 @araknet,21
> :2/141@fsxnet,25:25/9@metronet,38:38/0@fu-net,38:38/1@fu-net,38:38/2 @fu-net
> ,38:585/0@fu-net,38:585/1@fu-net,38:972/0@fu-net,38:972/1@fu-net,39:902/ 538
> @amiganet,46:10/177@agoranet,77:1/149@scinet,110:221/0@linuxnet,110:221/1@li
> nuxnet,411:411/42@combatnt,432:1/154@vkradio,454:1/310@ilink,618:100/40@micr
> one t,1337:3/189@tqwnet
> caps = CM,IBN
> vers = Internet Rex 2.31 Win32
> host = siliconu.com
> port = 24554
> info.sys = SiliconUnderground - ProBoard / FuNet WHQ
> info.loc = Rochester, NY
> info.time = 2024/02/06 14:11:10 -5:00
> localtime = Feb 6 2024 14:11:09
>
> My syslog entries look like:
> Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL BinkIT/2.41 invoked with
> options: -p
> Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL Attempting poll for node
> 38:585/1@fu-net
> Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL JSBinkP/4 callout to
> 38:585/1@fu-net started
> Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL Connecting to 38:585/1@fu-net
> at siliconu.com:24554
> Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL Peer version: Internet Rex
> 2.31 Win32
> Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL Peer ended their VER with "
> (binkp/1.1)" instead of the required " binkp/1.1", but we're assuming binkp
> 1.1 anywayFeb 6 14:11:09 bbs synchronet: evnt BINKPOLL Authentication
> successful: Feb 6 14:11:09 bbs synchronet: evnt BINKPOLL Timed event:
> BINKPOLL returned 0
>
> On all of my other peers I get callout success messages.
It's kind of a mystery without more debugging of what's the actual failure being detected in BinkP.prototype.session or BinkP.prototype.connect in load/binkp.js. Feel free to add some debugging if you want to find the issue, but if all looks fine and packets/files are flowing, then you can probably safely ignore the error as well.
--
digital man (rob)
