|Subject: (4.5) My innd won't start!|
Keep a "tail -f /var/adm/messages" running. INN reports most errors
via syslog. The syslog messages usually explain what is wrong.
Elsewhere in this document are details about some of the less obvious
Chances are, INN is starting, finding a misconfigured "ME" line in the
newsfeeds file, and exiting. You might want to read the section on
configuring your "newsfeeds" file first.
Rich Salz says a common reason is that you ran makehistory but didn't
rename the DBZ files. "makehistory" generates history.n.dir
and history.n.pag. They must be renamed:
mv history.n.dir history.dir mv history.n.pag history.pag(In the future, you could run "makehistory -f history", which is a
little more risky... so read the man page before you use it. "makehistory"
is part of the man page "news-recovery". This will change in 1.5.)
Izar Tarandach <email@example.com> suggests that another common
mistake is that innd wasn't being started by the correct uid. innd
(and therefore rc.news) must be started from "root" (not "news"). It
immediately turns itself in user "news" once certain tasks are
If you use a suid root inndstart, you can run it as any user.
[Last Changed: $Date: 1997/08/26 01:26:21 $ $Revision: 2.19 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]