Discussion:
dlo
(too old to reply)
Rick Smith
2024-03-22 03:54:40 UTC
Permalink
Hello Chad!

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

CA> So is this typically an issue with a remote server? And after a time
CA> it will resolve itself to start working. I am not sure what in my
CA> binkd config would cause a hld and it only seems to happen on
CA> one node.
CA> -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
Jay Harris
2024-03-20 13:58:24 UTC
Permalink
On Wednesday March 20 2024, Chad Adams said the following...

CA> Your log doesnt really show why though? How do you tell?
CA> -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
Wilfred van Velzen
2024-03-20 16:31:34 UTC
Permalink
Hi Chad,

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

CA> Every so often, binkd creates a .HLD file. Why does it do this? I
CA> 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/***@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/***@fidonet (2024/03/20 08:04:09)
20 Mar 00:04:09 [332] session closed, quitting...


Bye, Wilfred.
Chad Adams
2024-03-20 10:47:43 UTC
Permalink
Your log doesnt really show why though? How do you tell?
-Nugax
Wilfred van Velzen
2024-03-20 17:44:16 UTC
Permalink
Hi Chad,

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

CA> 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.

Loading...