Bug#810938: exim4-daemon-light: Cannot assign requested address: daemon abandoned at each startup

[Manuel Bilderbeek]

Hi,

On 14-01-16 23:01, Marc Haber wrote:
> Please keep the bug report always on Cc.

My apologies.

>>> See /usr/share/doc/exim4-base/README.Debian.gz, chapter 2.5.1
>>
>> It links to http://www.exim.org/bugzilla/show_bug.cgi?id=92
>> but that doesn't lead to a bug.

At least that is a bug in the documentation ;-)

>> Are you saying this is a known bug and I should therefore configure
>> $E4BCD_PANICLOG_NOISE to a regular expression?
>
> I am saying that your exim has for some reason believed that it
> couldn't bind to port 25 when restarting. Since you didn't say what

The point is: it has this at *every* start up. And I start up every day. 
So I get this e-mail every day.

> you investigated and are the only one who experiences this, chances

I have no idea what to investigate and how.

> are high that it was some local issue.

It's at least a persistent issue.

This is a relatively new installation (half a year old) and I didn't do 
any customization or tweaking, other than strictly necessary for a 
desktop system.

>         Please note that the
>         paniclog is not rotated daily, so existing issues will be reported
>         daily until either the paniclog is rotated due to its sheer size,
>         or you manually move it away, for example by calling logrotate -f
>         /etc/logrotate.d/exim4-paniclog from a shell.
>
> (this was copied verbatim from the docs).

Yes, I have read that, but it is not helpful if a new message is 
generated in the paniclog daily. I have a *growing* paniclog.

Here's the current content:

2016-01-12 18:52:17 socket bind() to port 25 for address ::1 failed: 
Cannot assign requested address: daemon abandoned
2016-01-13 08:17:34 socket bind() to port 25 for address ::1 failed: 
Cannot assign requested address: daemon abandoned
2016-01-14 19:32:12 socket bind() to port 25 for address ::1 failed: 
Cannot assign requested address: daemon abandoned

> I don't see a bug here at the moment.

I hope it's clear now what I mean. (Note that all of this is in my 
original bug report too...)

-- 
Kind regards,

Manuel