• How does INN handle retries when trying to feed to an inactive or offline peer?

    From Soul Patch@soul.patch@127.0.0.1 to news.software.nntp on Sat Sep 13 19:12:32 2025
    From Newsgroup: news.software.nntp

    If inn2 is unable to contact a peer to forward a feed, how many times does inn2 retry?

    How long does INN wait between successive retries?

    And how long until inn2 gives up trying to forward articles to the disconnected peer?
    --
    Soul Patch

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Jesse Rehmer@jesse.rehmer@blueworldhosting.com to news.software.nntp on Sun Sep 14 01:21:03 2025
    From Newsgroup: news.software.nntp

    On Sep 13, 2025 at 7:12:32rC>PM CDT, "Soul Patch" <soul.patch@127.0.0.1> wrote:

    If inn2 is unable to contact a peer to forward a feed, how many times does inn2 retry?

    How long does INN wait between successive retries?

    And how long until inn2 gives up trying to forward articles to the disconnected peer?

    From innfeed.conf manpage:

    initial-reconnect-time
    This key requires a positive integer value and defaults to 30. It
    defines how many seconds to first wait before retrying to reconnect
    after a connection failure. If the next attempt fails too, then
    the reconnect time is approximately doubled until the connection
    succeeds, or max-reconnect-time is reached.

    max-reconnect-time
    This key requires an integer value and defaults to 3600. It
    defines the maximum number of seconds to wait between attempt to
    reconnect to a peer. The initial value for reconnection attempts
    is defined by initial-reconnect-time, and it is doubled after each
    failure, up to this value.
    --- Synchronet 3.21a-Linux NewsLink 1.2