• Re: Posts staying in "incoming" folder, not processed

    From Borax Man@boraxman@geidiprime.nospam to news.software.nntp on Sun Jul 27 06:02:11 2025
    From Newsgroup: news.software.nntp

    On 2025-07-26, Nomen Nescio <nobody@dizum.com> wrote:
    I posted the message too early. To clarify, I can see files in
    /var/spool/news/incoming, which are the posted messages waiting to be
    processed.

    Did you set "spoolfirst" in inn.conf or readers.conf?

    spoolfirst
    If true, nnrpd(8) will spool new articles rather than attempting to send
    them to innd(8). If false, nnrpd will spool articles only if it receives
    an error trying to send them to innd. Setting this to true can be useful
    if nnrpd must respond as fast as possible to the client; however, when
    set, articles will not appear to readers until they are given to innd.
    nnrpd won't do this; "rnews -U" must be run periodically to take the
    spooled articles and post them. This is a boolean value and the default
    is false.


    spoolfirst is set to false

    spoolfirst: false

    There should be a cron job to process posts every hour:

    # Every hour, run an rnews -U. This is not only for UUCP sites, but
    # also to process queud up articles put there by nnrpd in case
    # innd wasn't accepting any articles.
    10 * * * * news [ -x /usr/bin/rnews ] && rnews -U


    The posts have now appeared, and I didn't do anything other then restart
    the service a few times.

    At the moment, the posts are going through. Why they weren't before,
    I'm not sure, but I changed nothing with regards to configuration.

    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From Borax Man@boraxman@geidiprime.nospam to news.software.nntp on Wed Aug 13 10:35:24 2025
    From Newsgroup: news.software.nntp

    On 2025-07-27, Borax Man <boraxman@geidiprime.nospam> wrote:
    On 2025-07-26, Nomen Nescio <nobody@dizum.com> wrote:
    I posted the message too early. To clarify, I can see files in
    /var/spool/news/incoming, which are the posted messages waiting to be
    processed.

    Did you set "spoolfirst" in inn.conf or readers.conf?

    spoolfirst
    If true, nnrpd(8) will spool new articles rather than attempting to send >> them to innd(8). If false, nnrpd will spool articles only if it receives >> an error trying to send them to innd. Setting this to true can be useful >> if nnrpd must respond as fast as possible to the client; however, when
    set, articles will not appear to readers until they are given to innd. >> nnrpd won't do this; "rnews -U" must be run periodically to take the
    spooled articles and post them. This is a boolean value and the default >> is false.


    spoolfirst is set to false

    spoolfirst: false

    There should be a cron job to process posts every hour:

    # Every hour, run an rnews -U. This is not only for UUCP sites, but
    # also to process queud up articles put there by nnrpd in case
    # innd wasn't accepting any articles.
    10 * * * * news [ -x /usr/bin/rnews ] && rnews -U


    The posts have now appeared, and I didn't do anything other then restart
    the service a few times.

    At the moment, the posts are going through. Why they weren't before,
    I'm not sure, but I changed nothing with regards to configuration.


    The posts have stopped going through now. I've restarted the machine, nothing.

    They just sit in "incoming".

    Also, manually running /usr/bin/rnews -U does not work.

    What I'd like help on, if possible, is troubleshooting, or at least understanding WHY inn2 is not posting.

    By the way, I am running nnrpd, and it seems it could be an issue with nnrpd passing articles to inn2.

    nnrpd is started with the following systemd service file.

    [Unit]
    Description=InterNetNews NNRPD
    Documentation=man:innd(8)
    After=inn2.service
    Wants=network-online.target

    [Service]
    Type=forking
    Restart=on-abort
    ExecStart=/usr/lib/news/bin/nnrpd -D -S -p 563
    User=news
    Group=news
    ConfigurationDirectory=news
    LogsDirectory=news
    LogsDirectoryMode=775
    RuntimeDirectory=news
    StateDirectory=news
    StateDirectoryMode=775
    ReadWritePaths=/var/spool/news/
    ProtectSystem=full
    ProtectControlGroups=yes
    ProtectHome=yes
    LimitNOFILE=infinity

    [Install]
    WantedBy=multi-user.target

    --- Synchronet 3.21a-Linux NewsLink 1.2