No subject

[root at giant news]# /usr/lib/news/bin/makehistory -O
[root at giant news]# su - news
-sh-2.05b$ cd /var/lib/news/
-sh-2.05b$ makedbz -s 0 -o
-sh-2.05b$ logout
[root at giant news]# service innd restart
Stopping INNWatch service:                                 [  OK  ]
Starting INND system:                                      [  OK  ]
[root at giant news]# service innd status
innd (pid 11035) is running...

Now it runs

:D

Is there a better way?

This is what is supplied with RHAS3-64, while I could update it outside
of the RHN system, I then have to maintain it separately outside of
up2date, which is a real pain when you have lots of servers with
individual needs.=20

I guess it was a false positive, I did try #'ing the one line but it
still did a funny.

Thanks

Steven

-----Original Message-----
From: Jeffrey M.Vinocur [mailto:jeff at litech.org]=20
Sent: Friday, 11 February 2005 2:42 p.m.
To: INN Workers (E-mail)
Subject: Re: innd install problems

On Feb 10, 2005, at 5:06 PM, Steven Jones wrote:

> [root at giant news]# rpm -q inn
>
> inn-2.3.5-5

This version is very out of date, FYI.  Unfortunately Redhat is very=20
slow about updating their RPMs.


> [root at giant news]# service innd status
> innd dead but subsys locked

Mmm isn't that a fun error.  It's been a long while since I had it,=20
though; I think a lot of the cases that caused it have been fixed.


> [root at giant news]# /usr/lib/news/bin/inncheck
>
> /etc/news/expire.ctl:23: malformed line.
> /etc/news/expire.ctl:30: malformed line.
>
> Lines 23 and 30 are the /remember/:10 lines, checking man expire.ctl
> shows the syntax is OK.

Well, there shouldn't be multiple /remember/ lines in the expire.ctl,=20
but I don't think that's your problem.  (inncheck has a lot of false=20
positives.)


> Feb  3 09:00:25 giant innd: SERVER cant dbzinit /var/lib/news/history
> Numerical argument out of domain

Ok, now -this- is probably your real problem.  That looks like the=20
history.dir, history.idx, and history.hash files (which are used for=20
speedy access to the history file itself) are corrupted.  You can=20
rebuild them with makedbz, it should take only a few seconds and not=20
have any adverse effects.


--=20
Jeffrey M. Vinocur
jeff at litech.org