inn newbie
Russ Allbery
rra at stanford.edu
Thu Oct 16 05:44:37 UTC 2003
kamaru adzh <che_awe81 at yahoo.com> writes:
> i've finished setup my newsgroup server using inn-2.3.5 in Linux Redhat
> 7.1 All configuration has done so far and everyone can connect. But when
> i try to get newsfeed from other news server, there are error recorded
> at my log files. This is the error which generated by news.err and
> news.notice:
> 1)news.err:
> Aug 12 16:37:17 opticlab innd: innfeed! exit 1 elapsed 0 pid 9440
> Aug 12 16:37:17 opticlab innfeed[9441]: seteuid(0) failed: Operation not permitted
In case you hadn't yet figured this out:
URL: <http://www.eyrie.org/~eagle/faqs/inn.html#S3.1>
Subject: 3.1. INN won't start after a new installation
The most common cause of this problem is that inndstart isn't setuid root.
inndstart must be installed owned by root and group news, mode 4550. The
ls -l output for inndstart should look something like:
-r-sr-x--- 1 root news 53768 Jan 8 00:47 inndstart*
inndstart will automatically be installed with the right permissions if
you run make install as root. If inndstart isn't setuid root, it will log
errors to syslog when it tries to start and cannot. If you aren't seeing
those error messages in syslog either, you probably haven't set up syslog
properly (see 3.4).
The other most frequent cause of this problem is not correctly following
the instructions in INSTALL on how to set up the initial history database.
After running makedbz, the initial history database files will have names
starting with history.n. These files must be renamed to remove the ".n"
before innd will start.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
Please send questions to the list rather than mailing me directly.
<http://www.eyrie.org/~eagle/faqs/questions.html> explains why.
More information about the inn-workers
mailing list