INN 2.5, inn-CURRENT-20090103 Issues
Julien ÉLIE
julien at trigofacile.com
Thu Jan 8 19:27:52 UTC 2009
Hi William,
> It has been 22 hours running with this new patch and no assertions errors or any other signs of problems.
I am happy to hear that and know your issue is probably solved.
In case you see other assertion failures (in other lines of connection.c),
feel free to tell us.
> The patch I am using that you sent is below, just so we know which one it is.
>
> - if (!cxnCheckstate (cxn))
> + if (cxn != NULL && !cxnCheckstate (cxn))
I have just committed this patch. You will find it in all the following
snapshots. However, as I told you, I used (cxn == NULL || !cxnCheckstate (cxn))
because it is better to execute the code just after in case cxn is NULL.
> The only other thing odd in the inn 2.5 current version as I mentioned before is the innreport message:
> - Use of uninitialized value in string eq at (eval 139) line 3
> With the exception of that, I haven't notice any other problems. What should I do about this innreport message, any suggestions?
Could you please try to run innreport by hand?
innreport -f ~/etc/innreport.conf ~/log/news ~/log/news.notice
(with the right paths to the mentioned files)
Is the warning still happening?
If that is the case, you could please send me (in private if you prefer
not to post it to the list) these three files?
> I am very encouraged by the host.c patch, sure is a nice thing to see innfeed running without all these assertion problems.
The most annoying is that, when it happens, innfeed generates dropped files
in its directory. Therefore, you have to use "procbatch -vm" on these
files by hand.
--
Julien ÉLIE
« Vinum spumosum nisi defluat est uitiosum. »
More information about the inn-workers
mailing list