1. Forum
  2. FidoNet
  3. BINKD

  • dlo

    From Chad Adams@1:19/40 to ALL on Wed Mar 20 13:00:18 2024
    Every so often, binkd creates a .HLD file. Why does it do this? I assume it#13 doesnt poll when it does.
    -Nugax


    --- CyberBBS v1.0.12 2024/03/19 [Debian Linux/x64]
    * Origin: CyberBBS BBS System | http://www.cyberbbs.net (1:19/40)
  • From Wilfred van Velzen@2:280/464 to Chad Adams on Wed Mar 20 19:31:34 2024
    Hi Chad,

    On 2024-03-20 13:00:18, you wrote to ALL:

    Every so often, binkd creates a .HLD file. Why does it do this? I
    assume it#13 doesnt poll when it does.

    It does that when there is a problem with the specific node. You can find out in your binkd.log what exactly is the cause. For instance from my log:

    ...
    + 20 Mar 00:04:09 [332] 5fa19e73.pkt skipped by remote
    + 20 Mar 00:04:09 [332] done (to 2:5020/400@fidonet, OK, S/R: 0/0 (0/0 bytes)) + 20 Mar 00:04:09 [332] holding skipped mail for 28800 sec
    + 20 Mar 00:04:09 [332] holding 2:5020/400@fidonet (2024/03/20 08:04:09)
    20 Mar 00:04:09 [332] session closed, quitting...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Chad Adams@1:19/40 to Wilfred van Velzen on Wed Mar 20 13:47:42 2024
    Your log doesnt really show why though? How do you tell?
    -Nugax


    --- CyberBBS v1.0.12 2024/03/19 [Debian Linux/x64]
    * Origin: CyberBBS BBS System | http://www.cyberbbs.net (1:19/40)
  • From Wilfred van Velzen@2:280/464 to Chad Adams on Wed Mar 20 20:44:16 2024
    Hi Chad,

    On 2024-03-20 13:47:43, you wrote to me:

    Your log doesnt really show why though? How do you tell?

    It is because of the "skipped by remote". That only happens when there is a problem at the remote link, like a full disk. So the node is put on hold for a configurable amount of time. In my case 28800 seconds = 8 hours.

    Bye, Wilfred.

    --- FMail-lnx64 2.3.0.1-B20240319
    * Origin: FMail development HQ (2:280/464)
  • From Jay Harris@1:229/664 to Chad Adams on Wed Mar 20 16:58:24 2024
    On Wednesday March 20 2024, Chad Adams said the following...

    Your log doesnt really show why though? How do you tell?
    -Nugax

    This happens to me on occasion when the node is unreachable for whatever reason (no internet, they're down, etc). Usually the error I see in my logs is "no route to host".


    Jay

    ... The only splits I can do are of the banana variety
    --- GoldED+/LNX 1.1.5-b20240309
    * Origin: Northern Realms (1:229/664)
  • From Chad Adams@1:19/40 to Wilfred van Velzen on Wed Mar 20 16:05:30 2024
    So is this typically an issue with a remote server? And after a time
    it will resolve itself to start working. I am not sure what in my
    binkd config would cause a hld and it only seems to happen on
    one node.
    -Nugax


    --- CyberBBS v1.0.12 2024/03/20 [Debian Linux/x64]
    * Origin: CyberBBS BBS WHQ System | whq.cyberbbs.net:6023 (1:19/40)
  • From Rick Smith@1:105/81 to Chad Adams on Fri Mar 22 06:54:40 2024
    Hello Chad!

    Wednesday March 20 2024 16:05, you wrote to Wilfred van Velzen:

    So is this typically an issue with a remote server? And after a time
    it will resolve itself to start working. I am not sure what in my
    binkd config would cause a hld and it only seems to happen on
    one node.
    -Nugax

    Try polling that node manually, see if that reveals clues. Also depending on your tosser/packer you could set a specific node for hold so that it would have to pick up mail instead of binkd delivering it.. Thats what I understand anyhow.

    Regards,

    Rick

    ... It was good BBSing with you @F
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)