Bug#482312: exim4: exits when asked to reload configuration

[Johannes Berg]

> Please help us to reproduce this issue by providing debug output and
> other evidence of the bug, step-by-step instructions to reproduce this
> behavior.
> 
> [2/501]mh at scyw00225:~$ pstree -ap | grep [e]xim
>   |-exim4,3474 -bd -q30m
> [3/502]mh at scyw00225:~$ sudo /etc/init.d/exim4 reload
> mh's sudo password for scyw00225:
> Reloading exim4 configuration files: exim4.
> [4/503]mh at scyw00225:~$ pstree -ap | grep [e]xim
>   |-exim4,3474 -bd -q30m
> [5/504]mh at scyw00225:~$

[...]

> As you can see, this works here on two systems.

fun.

# pstree -ap | grep [e]xim
  |-exim4,6060 -bd -q30m
  |   `-exim4,12021 -bd -q30m
# /etc/init.d/exim4 reload
Reloading exim4 configuration files: exim4.
ALERT: exim paniclog /var/log/exim4/paniclog has non-zero size, mail
system possibly broken
# pstree -ap | grep [e]xim
  |-exim4,12021 -bd -q30m


That particular process 12021 is a mail handling process, not a listener
process, a while later:
# pstree -ap | grep [e]xim
#

First thought: Maybe it has to do with the panic log? That always
contains entries from when clamav found problems or happened to not be
contactable (although I ignore that in my exim config).

But testing that (cycled paniclog) I still have the problem.

I have no idea what to do, what kind of debug output do you want? Start
the shell script with tracing?

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-exim4-maintainers/attachments/20080521/aec3cbb4/attachment-0001.pgp