On Thu, 25 Sep 1997, Skye Merlin Poier wrote:
> After running exim for over a week, there are about a hundred messages
> in the queue that are MUCH older than the maximum retry time. I have
> auto_thaw set to 6h, ignore_errmsg_errors set to true (as of a few
> days ago), and retry config:
>
> * * F,2h,15m; G,16h,2h,1.5; F,2d,6h
>
> When I view the message log from eximon, it shows it hasn't been touched
> for 5 days, when it was unfrozen by auto_thaw. I even tried unfreezing one
> of them from eximon, but the queue runner doesn't seem to do anything
> with it. Some sort of db corruption? What do I need to do to fix it?
Strange. One thing you can do is to force a delivery attempt and see
what happens. To see what *really* happens, do this from the command
line with -d9 to get all the debugging output.
> Second question, it seems the exim-main.log file got truncated to zero
> bytes when I kill -HUP'd the server! Not good... doesn't happen often,
> this is the second time I've noticed it though. Anyone else seen this?
> At least I *think* its the kill -HUP that is doing it...
I have never seen this, and I kill -HUP quite a lot. :-)
Exim opens the mainlog with O_APPEND so that all writes are appended to
the end of it. That should never have the effect of truncating. Next
time you kill -HUP, can you observe carefully, please?
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
* This is sent by the exim-users mailing list. To unsubscribe send a
mail with subject "unsubscribe" to exim-users-request@???
* Exim information can be found at http://www.exim.org/
