|Subject: (3.2) Why does innd just exit right away with no message?|
First, fix your syslog: innd (nearly) always logs a message before it exits.
(The INN distribution includes a version of the current UCB syslog, along
with instructions on how to install it. Ultrix systems might want to look at
the syslog that is available on gatekeeper.dec.com). If innd doesn't
syslog, then it did dump a core file, that you can inspect.
Second, the most common cause of this is that you do not have a history
file (or no history database). You will see a message like this:
ME cant dbminit /usr/local/news/history No such file or directory( Note that in versions > INN1.5, the word "ME'' is replaced by
This means that you do not have a history database (or no history.dir
and history.pag files). If you are just installing INN for your first
time, you might want to run the BUILD script in your INN source tree.
Or, you can read about makehistory in doc/news-recovery.8; if you do
the latter, make sure to rename the database files (pay attention to
the two "mv" commands).
Another possibility is a bad active file; e.g. one line only has three
fields instead of four. You can find such lines by running expire:
expire -n -x -twhich will then show you which lines are bad.
[Last Changed: $Date: 1997/11/03 18:15:12 $ $Revision: 2.18 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]