| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 23 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 52:12:16 |
| Calls: | 583 |
| Files: | 1,139 |
| D/L today: |
34 files (520K bytes) |
| Messages: | 111,533 |
I set up some years ago an INN server for private use. It worked for years almost without issue however I've run into a program that has appeared for seemingly no reason.
The server I set up is for me and friends, and does not peer with any other server.
The issue I've found, which I'm asking for help troubleshooting, is that submitted posts are not appearing. They are being held in /var/spool/news/incoming
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.
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.
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
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.