innd stops responding

Gary Thandi Gary.Thandi at 360.net
Mon Jul 19 21:15:06 UTC 2004


So that I'm completely clear:

1) Download/save the patch file into your inn-2.4.1 source directory.  You
mentioned two patches.
	a. http://www.avalon.net/~hakehoe/inn/ovdb_2.4.1_patch.txt
	b. The patch that you attached in one of your emails, which I've
attached as "patch.txt"
	c. My source directory is /opt/SRC/src/inn-2.4.1.  Where would I put
each of the files listed in point 1a and 1b?
2) Change directory into your source directory: cd inn-2.4.1
3) Apply the patch with this command:  patch -p0 < ovdb_2.4.1_patch.txt
4) Repeat steps 1-3 with the patch.txt file that I sent you
5) Do a "make update"
6) Restart inn

I did the readserver fix (ovdb.conf) that you mentioned and the problem
still persists.

Thanks Heath.

-----Original Message-----
From: Heath Kehoe [mailto:hakehoe at avalon.net]
Sent: Monday, July 19, 2004 11:21 AM
To: Gary Thandi
Subject: Re: innd stops responding


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

1) Download/save the patch file into your inn-2.4.1 source directory.
2) Change directory into your source directory: cd inn-2.4.1
3) Apply the patch with this command:  patch -p0 < ovdb_2.4.1_patch.txt
4) Repeat steps 1-3 with the patch.txt file that I sent you
5) Do a "make update"
6) Restart inn


On Jul 19, 2004, at 12:45, Gary Thandi wrote:

>
> How do I apply the patch ovdb_2.4.1?
>
> -----Original Message-----
> From: Heath Kehoe [mailto:hakehoe at avalon.net]
> Sent: Monday, July 19, 2004 7:40 AM
> To: INN Workers Mailing List
> Subject: Re: innd stops responding
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Jul 19, 2004, at 8:50, Alex Kiernan wrote:
>
>> On Mon, 19 Jul 2004 06:42:48 -0700, Gary Thandi <gary.thandi at 360.net>
>> wrote:
>>>
>>> yes.  i've had to resort to stopping and starting all news processes
>>> every
>>> 60 minutes.
>>>
>>
>> Try getting a snapshot - I know Heath's made some fixes to the ovdb
>> code, but I've not tried those.
>
> Either that, or you can get this patch:
> http://www.avalon.net/~hakehoe/inn/ovdb_2.4.1_patch.txt
>
>> Certainly the behaviour you're seeing is typical for ovdb on Solaris;
>> I'm not sure if anyone's addressed the way nnrpd does termination yet,
>> but last time I looked it seemed like if you took a signal at the
>> wrong moment, nnrpd would try and make calls into ovdb (and hence
>> BerkeleyDB) in a re-entrant fashion, which isn't supported (not
>> unreasonably) by BerkeleyDB.
>
> Whoa!!!  I never knew about this.  OK, looks like the sigpipe handler
> calls ExitWithStats.  Yuck!!  But how often does nnrpd exit in this 
> way?
>
> There's an easy workaround:  turn on readserver in ovdb.conf, and
> restart
> news.  With readserver on, the nnrpd doesn't access BerkeleyDB 
> directly,
> thus avoiding the signal handler problem.
>
> - - h
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (Darwin)
>
> iD8DBQFA+91O4uXPAG0A1J4RAkw4AJ4/80HO4vQjnLD3KgFUUMMy1x2rSACeM3xD
> IJautqYW8B/CGhBvy37SZWw=
> =xA3i
> -----END PGP SIGNATURE-----
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFA/BEl4uXPAG0A1J4RAjKOAJ9eqZ1FNIxBSsXNY1eQu3Gre1OUlwCggB+6
MXuLh+ReZBoFzKMPB5HhMYs=
=c+oN
-----END PGP SIGNATURE-----


More information about the inn-workers mailing list