Hi Jeremy,
> On 03/06/2020 09:42, Mikhail Golub via Exim-users wrote:
>> 42885 creating notifier socket
>> 42885? /var/spool/exim/exim_daemon_notify
>> 42885 LOG: MAIN PANIC
>> 42885?? daemon_notifier_socket bind: Address already in use
>>
>> It's bug?
> It's something still using that socket.
>
> Either "ss -p" or "netstat -panu" might tell you what process,
> if this is a persistent condition.
today I gave Exim 4.94 a try and ran into the same problem. I must
admit that my configuration requires to run two Exim instances in
parallel. I'm executing the following two commands to start the
daemons:
# 1. for listeners on port 25/tcp and 587/tcp
# daemon_smtp_ports = smtp : submission
/usr/sbin/exim -bd -q20m -om -oP /var/run/exim.pid
# 2. for a listener on port 465/tcp
/usr/sbin/exim -bd -q20m -om -tls-on-connect -oX ssmtp -oP
/var/run/exim-ssmtp.pid
Until v4.93.0.4 this works without any error message, but v.4.94
generates the mentioned message. Is there a specific trick to get
the same function back without that message? Do I need to modifiy
my configuration or is it a bug in the latest version?
Thank
Juergen
--
