Hi Jesse,
$ echo fr.soc.politique | expireover -f - -Z tmp/lowmark
expireover: can't expire fr.soc.politique
I don't need to expire this group, but found it odd that the error was produced from the daily expireover, but only for this one group.
I can dump the contents with ovsqlite-util and, while I didn't examine all 4+ million lines, everything looks normal.
That's indeed very odd, either a bug or a corruption of some data.
This error appears when the expire_one() function in storage/ovsqlite/ovsqlite.c returns false.
If you wish and have a bit of time to investigate, is it possible to
rebuild INN with additional logs at each "return false"?
For instance, changing:
if (!write_request())
return false;
to:
if (!write_request()) {
syswarn("first write_request failed");
return false;
}
and so on...
There are 20 occurrences.
In the for loop, you may want to add the processed article number:
if (!unpack_now(response, &expires, sizeof expires)) {
syswarn("unpack_now expires failed for %lu", artnum);
return false;
}
Once the culprit is found, additional investigations will have to be
done, with again additional more precise logs, so it will take more time.
Tell me if you want to.
Also, for the changes of the 20 occurrences, do you want to do that
yourself or should I send you the modified ovsqlite.c file to your
e-mail address?
--
Julien ÉLIE
« Mon grand-père buvait un litre de whisky par jour et il est mort à 103
ans. À l'incinération, on a cru que le feu ne s'arrêterait jamais. »
(Sloppy White)
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)