INN throttling problem?

Lou Rabon lrabon at netstream.biz
Tue Jul 23 15:39:49 UTC 2002



>=20
>=20
> On Tue, Jul 23, 2002 at 09:41:34AM -0400, Lou Rabon wrote:
> > Jul 23 00:03:08 cheetah innd: tradindexed: could not open
> > /var/spool/news/overview/c/c/control.cancel.DAT: Permission denied
> =20
> It looks like your permissions are set wrong on the spool and/or
> overview directories.  Take a look at your spool/overview and spool
> directories to make sure they are owned by user news and grouped
> by user news as well.  It probably wouldn't hurt if you were to do
> something like chown -R news:news /news/spool  or whereever your
> spool resides.

drwxr-xr-x   8 news     news         4096 Jul 22 19:17 .
drwx--x--x   8 root     root         4096 Jul 17 19:45 ..
drwxr-xr-x   2 news     news         4096 Jul  9 22:01 archive
drwxr-xr-x   2 news     news         4096 Jul  9 22:01 articles
drwxr-xr-x   3 news     news         4096 Jul 17 19:45 incoming
drwxr-xr-x   2 news     news         4096 Jul 23 11:28 innfeed
drwxr-xr-x   2 news     news         4096 Jul 22 17:29 outgoing
drwxr-xr-x   6 news     news         4096 Jul 23 11:30 overview

>=20
> > Now when I try to check news, etc, I get:
> >=20
> > Jul 23 09:13:46 cheetah nnrpd[3021]: 65.1.2.3 rejected=20
> Permission denied
> > writing creating overview file -- throttling
>=20
> More permissions problems?  how are you starting innd anyways?

I'm using the /etc/init.d script, which is starting it with the news =
account:

start() {
        echo -n $"Starting INND system: "
        # INN uses too many un-checked shell scripts
        unset LANG
        unset LC_COLLATE
        daemon --user news /etc/rc.news
        RETVAL=3D$?
        [ $RETVAL -eq 0 ] && touch /var/lock/subsys/innd
        echo
}

> you should be using rc.news via this method:
>=20
> # su - news=20
> $ /news/bin/rc.news start
>=20
> And if you need to shut it down, instead give rc.news a 'stop'=20
> argument.
>=20
> If you are doing the above, then another likely reason is that
> your innd/inndstart permissions are screwed up.  They should look
> like:
>=20
> -r-xr-x---  1 news  news  1107490 Jul 14 04:15 /news/bin/innd
> -r-sr-x---  1 root  news   121042 Jul 13 04:30 /news/bin/inndstart
>=20

-r-xr-xr-x   1 news     news      1693729 Jul  9 22:01 /usr/bin/innd
-r-sr-x---   1 root     news       145197 Jul  9 22:01 =
/usr/bin/inndstart

> You should also make it a habbit to run the /news/bin/inncheck
> proggie (after new installs/upgrades/etc) to make sure your other
> files and/or directories have sane permissions etc.
>=20

I have...no other problems:

/etc/news/inn.conf:21: org is blank
/etc/news/inn.conf:99: modmailer has bad address
/etc/news/newsfeeds:0: warning you accept all incoming article =
distributions

> > I'm sure restarting the server will fix it, but I fear I=20
> may have this
> > problem all the time.  The archives have some mention of=20
> this, but no
> > fix
>=20
> Again, this is a permissions related issue, something quite commonly
> overlooked by people.  I could have sworn I recalled the FAQ having
> something about this a while ago, but then again I'll admit I haven't
> looked at it in a few years :)
>=20
> -mohan

I found an article stating that I needed to add a "trash" field to my =
sotrage.conf, which I've done too:

method trash {
        newsgroups: *
        class: 9999
}

I'm still getting these errors and it's stopping the server from =
running...



More information about the inn-workers mailing list