exim-users at spodhuis
Jun 17, 2008, 5:49 PM
Post #2 of 2
(302 views)
Permalink
|
On 2008-06-17 at 10:20 +0200, Fernando Gonzo wrote:
> i'm sending the log to file and syslog. when logfile is unwriteable the
> loglevel for normal messages in syslog is changed from info to critical.
> i don't like this.
>
> mail.crit exim[10236]: 2008-06-17 00:31:52 1K8HEY-0008Ub-UG Completed
> QT=6h24m46s
So you should see, just below that, the warning that Exim is dying:
exim: could not open panic log - aborting: see message(s) above
Unexpected log failure, please try later
Exim only does this when it fails to write the logs, so it tries to
write to the panic log, and that fails too.
The write to the paniclog is normally accompanied by writing at alert
level, not critical level.
If this is failing then you're either messing with usercodes in weird
ways and not ensuring that your logs are writeable by the correct user,
or your disk is full. Whatever, a failure to write to panic log is
critical.
Fix the problem; if the disk is full any you're using remote syslog,
perhaps you should only be using remote syslog? Or keeping fewer old
logs on local disk?
-Phil
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
|
