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

Am 11.09.2014 um 18:44 schrieb Jeremy Harris:
[...]
> 
> It might be useful to know when the *connection* arrived from
> (sigh, obfuscated thus making our lives harder in interpreting
> this) "<= XXXX"
> 
I know the problem with obfuscated logs, but german law is very strict
in this case.

The connections arrive from all over the world

> This:
> 
>> +++ 1XRtXj-0003UM-OW has not completed +++
> 
> was presumably exigrep again, on the paniclog not the mainlog. 
> Please, keep the two separate.
> 
> 
> This:
>> 2014-09-11 03:51:48 1XRtXj-0003UM-OW => XXXX C="250 2.6.0 
>> <[email protected]> 
>> [InternalId=3665] Queued mail for delivery"
> 
> ... I assume that was from the paniclog also.

No, it was in mainlog only.

Two confusing things
> here: - it's apparently a store&forward delivery "=>", not the
> cutthrough delivery ">>" - the InternalId given by the destination
> end is different, implying that it really was a duplicate delivery
> that we did
> 
> Was that line in mainlog as well as paniclog?

These lines were only in mainlog.
> 
> 
>> 2014-09-11 03:51:48 1XRtXj-0003UM-OW failed to unlink 
>> /var/spool/exim4/msglog/j/1XRtXj-0003UM-OW: No such file or 
>> directory 2014-09-11 03:51:49 End queue run: pid=13382

This line is from mainlog.

In paniclog, we have only one line:

2014-09-11 03:51:48 1XRtXj-0003UM-OW failed to unlink
/var/spool/exim4/msglog/j/1XRtXj-0003UM-OW: No such file or directory

Nothing more.
>> 
>> But only 1 daemon running at the moment:
>> 
>> # ps aux | grep exim root      4372  0.0  0.0   3788   784 pts/0 
>> S+   08:23   0:00 grep exim 102      24243  0.0  0.0  11008  2752
>> ? Ss   Sep03   1:36 /usr/local/bin/exim -bd -q30m
>> 
>> How can this happen? exim is not started from cron. Monit is 
>> running, but did not restart exim.
> 
> I can't think of a way right now...  unless - is the system clock 
> stable?  Is time jumping backwards?  That would invalidate all
> sorts of assumptions if true.
> 

ntpd is running on the system and doesn't show any inconsistency.

More curious: the error message did not appear any more since
2014-09-12 12:21:56.

Is it save to remove the *-J-files in the spool-dir?

- -- 
Regards,

Kerstin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iNwEAQECAAYFAlQX+jMACgkQPPx5/A6Q3cnYXQX9HkYZYtcxhjmWIKeFxZicr4Dw
gxnjR+Y4AIB7CLDD0BbsjBVUGFDbdueX0nCbQrGx6FSCDhV4dCPHXPCWFXgBW02U
FHg7f4zL1aU0CRn6dHfNJPsisoi2BG9iBs65XBoYuH4XydfQYeEBpZOpKyoD9++B
gwyGBQ47iJvoJ9yuif4IVTIQ0rzcb7nI2jyNNq3nyXxoEuTQWld2Zm3EDAEtr/3A
+eAEr0a5SY8rURiAqued1SNB+UM+lEjSuwMG5q6a
=DZSr
-----END PGP SIGNATURE-----

-- 
## List details at https://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/

Reply via email to