Bug#860317: upgrade to latest stretch version breaks

2017-04-20 Thread Brent S. Elmer Ph.D.
On Thu, 2017-04-20 at 17:20 +0200, Andreas Metzler wrote:
> 
> 
> 
> Ok, suspicion confirmed. Run dpkg-reconfigure exim4-config and drop
> ::1
> from the listening interfaces.
> 
> cu Andreas

Yes, that fixed it.

Thanks



Bug#860317: upgrade to latest stretch version breaks

2017-04-20 Thread Andreas Metzler
On 2017-04-19 "Brent S. Elmer Ph.D."  wrote:
> On Wed, 2017-04-19 at 18:45 +0200, Andreas Metzler wrote:
>> On 2017-04-17 "Brent S. Elmer Ph.D."  wrote:
>> [...]
>>> paniclog and mainlog contains this:
>>> 2017-04-17 14:30:26 IPv6 socket creation failed: Address family not
>>> supported by protocol

>> This looks like 610918, i.e. having changed Debian's default default
>> setup to disable IPv6 without adapting exim4 configuration
>> accordingly.

>> Are you able to manually start a daemon instance?
>> update-exim4.conf && exim4 -bd -d

>> cu Andreas

> No, here is the output.

> # update-exim4.conf && exim4 -bd -d
[...]
> originator: uid=0 gid=0 login=root name=root
>  3468 listening on 127.0.0.1 port 25
>  3468 LOG: MAIN
>  3468   IPv6 socket creation failed: Address family not supported by
> protocol
>  3468 LOG: PANIC DIE
>  3468   IPv6 socket creation failed: Address family not supported by
> protocol
>  3468 search_tidyup called
>  3468  Exim pid=3468 terminating with rc=1


Ok, suspicion confirmed. Run dpkg-reconfigure exim4-config and drop ::1
from the listening interfaces.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-19 Thread Brent S. Elmer Ph.D.
On Wed, 2017-04-19 at 18:45 +0200, Andreas Metzler wrote:
> On 2017-04-17 "Brent S. Elmer Ph.D."  wrote:
> [...]
> > paniclog and mainlog contains this:
> > 2017-04-17 14:30:26 IPv6 socket creation failed: Address family not
> > supported by protocol
> 
> This looks like 610918, i.e. having changed Debian's default default
> setup to disable IPv6 without adapting exim4 configuration
> accordingly.
> 
> Are you able to manually start a daemon instance?
> update-exim4.conf && exim4 -bd -d
> 
> cu Andreas

No, here is the output.

# update-exim4.conf && exim4 -bd -d
Exim version 4.89 uid=0 gid=0 pid=3468 D=fbb95cfd
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM
DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm
dbmjz dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Compiler: GCC [6.3.0 20170221]
Library version: Glibc: Compile: 2.24
Runtime: 2.24
Library version: GnuTLS: Compile: 3.5.8
 Runtime: 3.5.8
Library version: PCRE: Compile: 8.39
   Runtime: 8.39 2016-06-14
Total 13 lookups
WHITELIST_D_MACROS: "OUTGOING"
TRUSTED_CONFIG_LIST: "/etc/exim4/trusted_configs"
changed uid/gid: forcing real = effective
  uid=0 gid=0 pid=3468
  auxiliary group list: 
seeking password data for user "uucp": cache not available
getpwnam() succeeded uid=10 gid=10
configuration file is /var/lib/exim4/config.autogenerated
log selectors = cffc 0e320202
cwd=/home/brente 3 args: exim4 -bd -d
trusted user
admin user
seeking password data for user "mail": cache not available
getpwnam() succeeded uid=8 gid=8
DSN: hubbed_hosts propagating DSN
DSN: nonlocal propagating DSN
DSN: real_local propagating DSN
DSN: system_aliases propagating DSN
DSN: userforward propagating DSN
DSN: procmail propagating DSN
DSN: maildrop propagating DSN
DSN: lowuid_aliases propagating DSN
DSN: local_user propagating DSN
DSN: mail4root propagating DSN
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
 3468 listening on 127.0.0.1 port 25
 3468 LOG: MAIN
 3468   IPv6 socket creation failed: Address family not supported by
protocol
 3468 LOG: PANIC DIE
 3468   IPv6 socket creation failed: Address family not supported by
protocol
 3468 search_tidyup called
 3468  Exim pid=3468 terminating with rc=1




Bug#860317: upgrade to latest stretch version breaks

2017-04-19 Thread Andreas Metzler
On 2017-04-17 "Brent S. Elmer Ph.D."  wrote:
[...]
> paniclog and mainlog contains this:

> 2017-04-17 14:30:26 IPv6 socket creation failed: Address family not
> supported by protocol

This looks like 610918, i.e. having changed Debian's default default
setup to disable IPv6 without adapting exim4 configuration accordingly.

Are you able to manually start a daemon instance?
update-exim4.conf && exim4 -bd -d

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-18 Thread Brent S. Elmer Ph.D.
On Tue, 2017-04-18 at 18:50 +0200, Andreas Metzler wrote:
> On 2017-04-17 "Brent S. Elmer Ph.D."  wrote:
> > On Sat, 2017-04-15 at 13:33 +0200, Andreas Metzler wrote:
> > > On 2017-04-14 "Brent S. Elmer"  wrote:
> 
> [...]
> > > > Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail
> > > > Transport Agent...
> > > > Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
> > > > Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
> > > > /var/log/exim4/pa…oken
> > > > Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
> > > > /run/exim4/exim.…tory
> > > > Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never
> > > > wrote its
> > > > PI…ing.
> > > > Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim
> > > > Mail
> > > > Transport…ent.
> 
> Hello,
> 
> you have set
> QUEUERUNNER='nodaemon'
> in /etc/default/exim4, haven't you?
> 
> cu Andreas

No, it is 'combined'.  I don't think I have ever done anything to
change it.



Bug#860317: upgrade to latest stretch version breaks

2017-04-18 Thread Andreas Metzler
Control: retitle -1 daemon startup under systemd fails when exim is configured 
without daemon process
Control: severity -1 serious
Control: tags -1 pending

On 2017-04-17 Davide Prina  wrote:
> On 17/04/2017 15:49, Andreas Metzler wrote:
>> Could you post th contents of /etc/default/exim4?

> $ cat /etc/default/exim4
[...]
> QUEUERUNNER='nodaemon'
[...]

Thanks for bearing with me. That seems to be the necessary part for
reproducing this.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-18 Thread Andreas Metzler
On 2017-04-17 "Brent S. Elmer Ph.D."  wrote:
> On Sat, 2017-04-15 at 13:33 +0200, Andreas Metzler wrote:
>> On 2017-04-14 "Brent S. Elmer"  wrote:
[...]
>>> Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail
>>> Transport Agent...
>>> Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
>>> Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
>>> /var/log/exim4/pa…oken
>>> Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
>>> /run/exim4/exim.…tory
>>> Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never
>>> wrote its
>>> PI…ing.
>>> Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim Mail
>>> Transport…ent.

Hello,

you have set
QUEUERUNNER='nodaemon'
in /etc/default/exim4, haven't you?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-17 Thread Brent S. Elmer Ph.D.
On Sat, 2017-04-15 at 13:33 +0200, Andreas Metzler wrote:
> On 2017-04-14 "Brent S. Elmer"  wrote:
> > Package: exim4
> > Version: 4.89-1
> > Severity: normal
> > I upgraded packages in stretch and there was a problem upgrading
> > exim4.  When I
> > try to do a reinstall of exim4 to try to fix it using synaptic, I
> > get:
> 
> [...]
> > Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail
> > Transport Agent...
> > Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
> > Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
> > /var/log/exim4/pa…oken
> > Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
> > /run/exim4/exim.…tory
> > Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never
> > wrote its
> > PI…ing.
> > Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim Mail
> > Transport…ent.
> 
> Anything in the exim logfiles?
> 
> cu Andreas
> 

paniclog and mainlog contains this:

2017-04-17 14:30:26 IPv6 socket creation failed: Address family not
supported by protocol



Bug#860317: upgrade to latest stretch version breaks

2017-04-17 Thread Davide Prina

Hi Andreas,

On 17/04/2017 15:49, Andreas Metzler wrote:


Could you post th contents of /etc/default/exim4?


$ cat /etc/default/exim4
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from 
/etc/ppp/ip-up.d/exim4

#QUEUERUNNER='combined'
QUEUERUNNER='nodaemon'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# options for daemon listening on port 25
SMTPLISTENEROPTIONS=''

Ciao
Davide



Bug#860317: upgrade to latest stretch version breaks

2017-04-17 Thread Andreas Metzler
On 2017-04-17 Davide Prina  wrote:
> On 16/04/2017 11:42, Andreas Metzler wrote:
[...]
> # systemctl start exim4
> Job for exim4.service failed because of unavailable resources or another
> system error.
> See "systemctl status exim4.service" and "journalctl -xe" for details.

>> update-exim4.conf && exim4 -bd -d

> # update-exim4.conf && exim4 -bd -d
[...]
> 22421 pid written to /run/exim4/exim.pid
> 22421 changed uid/gid: running as a daemon
> 22421   uid=102 gid=107 pid=22421
> 22421   auxiliary group list: 107
> 22421 LOG: MAIN
> 22421   exim 4.89 daemon started: pid=22421, no queue runs, listening for
> SMTP on [127.0.0.1]:25 [::1]:25
> 22421 set_process_info: 22421 daemon(4.89): no queue runs, listening for
> SMTP on [127.0.0.1]:25 [::1]:25
> 22421 daemon running with uid=102 gid=107 euid=102 egid=107
> 22421 Listening...


> I have tried to send a mail and it work


I still do not understand the error. Could you post th contents of
/etc/default/exim4?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-17 Thread Davide Prina

Hi Andreas,

On 16/04/2017 11:42, Andreas Metzler wrote:

On 2017-04-16 Davide Prina  wrote:

Package: exim4
Version: 4.89-1


[...]

Apr 16 11:06:06 davide systemd[1]: Starting LSB: exim Mail Transport
Agent...
Apr 16 11:06:07 davide exim4[3884]: Starting MTA:.
Apr 16 11:06:07 davide systemd[1]: exim4.service: PID file
/run/exim4/exim.pid not readable (yet?) after start: No such file or
directory
Apr 16 11:06:07 davide systemd[1]: Failed to start LSB: exim Mail Transport

[...]


$ systemctl status exim4.service

[...]

apr 16 09:42:10 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with
result 'resources'.




$ journalctl -xe

[...]

--
-- The result is failed.
Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Unit entered
failed state.
Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with
result 'resources'.

[...]



this whole bunch of debug info from different commands does not seem to
belong together. The time stamps do not match. (11:06:07 vs 09:42:10 vs
09:41:32)


I take them from different try, but the errors are always the same.
I try to find a workaround, but I failed.


$ cat /var/log/exim4/mainlog

[...]

2017-04-16 09:39:33 1czemS-0006A8-F3 Completed


Anything in paniclog?


# LANG=C ls -l /var/log/exim4/paniclog
ls: cannot access '/var/log/exim4/paniclog': No such file or directory


Does "exim4 -bV" report any errors?


# exim4 -bV
Exim version 4.89 #2 built 09-Mar-2017 16:49:47
Copyright (c) University of Cambridge, 1995 - 2017
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 
- 2017

Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM 
DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm 
dbmjz dbmnz dnsdb dsearch nis nis0 passwd

Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated


Are you able to manually start a daemon instance?


# systemctl start exim4
Job for exim4.service failed because of unavailable resources or another 
system error.

See "systemctl status exim4.service" and "journalctl -xe" for details.


update-exim4.conf && exim4 -bd -d


# update-exim4.conf && exim4 -bd -d
Exim version 4.89 uid=0 gid=0 pid=22421 D=fbb95cfd
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM 
DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm 
dbmjz dbmnz dnsdb dsearch nis nis0 passwd

Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Compiler: GCC [6.3.0 20170221]
Library version: Glibc: Compile: 2.24
Runtime: 2.24
Library version: GnuTLS: Compile: 3.5.8
 Runtime: 3.5.8
Library version: PCRE: Compile: 8.39
   Runtime: 8.39 2016-06-14
Total 13 lookups
WHITELIST_D_MACROS: "OUTGOING"
TRUSTED_CONFIG_LIST: "/etc/exim4/trusted_configs"
changed uid/gid: forcing real = effective
  uid=0 gid=0 pid=22421
  auxiliary group list: 
seeking password data for user "uucp": cache not available
getpwnam() succeeded uid=10 gid=10
configuration file is /var/lib/exim4/config.autogenerated
log selectors = cffc 0e320202
cwd=/home/davide 3 args: exim4 -bd -d
trusted user
admin user
seeking password data for user "mail": cache not available
getpwnam() succeeded uid=8 gid=8
DSN: hubbed_hosts propagating DSN
DSN: nonlocal propagating DSN
DSN: real_local propagating DSN
DSN: system_aliases propagating DSN
DSN: userforward propagating DSN
DSN: procmail propagating DSN
DSN: maildrop propagating DSN
DSN: lowuid_aliases propagating DSN
DSN: local_user propagating DSN
DSN: mail4root propagating DSN
user name "root" extracted from gecos field "root"
originator: uid=0 gid=0 login=root name=root
22421 listening on 127.0.0.1 port 25
22421 listening on ::1 port 25
22421 pid written to /run/exim4/exim.pid
22421 changed uid/gid: running as a daemon
22421   uid=102 gid=107 pid=22421
22421   auxiliary group list: 107
22421 LOG: MAIN
22421   exim 4.89 daemon started: pid=22421, no queue runs, listening 
for SMTP on [127.0.0.1]:25 [::1]:25
22421 set_process_info: 22421 daemon(4.89): no queue runs, listening for 
SMTP on [127.0.0.1]:25 [::1]:25

22421 daemon running with uid=102 gid=107 euid=102 egid=107
22421 Listening...


I have tried to send a mail and it work

Ciao
Davide



Bug#860317: upgrade to latest stretch version breaks

2017-04-16 Thread Andreas Metzler
On 2017-04-16 Davide Prina  wrote:
> Package: exim4
> Version: 4.89-1

[...]
> Apr 16 11:06:06 davide systemd[1]: Starting LSB: exim Mail Transport
> Agent...
> Apr 16 11:06:07 davide exim4[3884]: Starting MTA:.
> Apr 16 11:06:07 davide systemd[1]: exim4.service: PID file
> /run/exim4/exim.pid not readable (yet?) after start: No such file or
> directory
> Apr 16 11:06:07 davide systemd[1]: Failed to start LSB: exim Mail Transport
[...]

> $ systemctl status exim4.service
[...]
> apr 16 09:42:10 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with
> result 'resources'.


> $ journalctl -xe
[...]
> --
> -- The result is failed.
> Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Unit entered
> failed state.
> Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with
> result 'resources'.
[...]

Hello,

this whole bunch of debug info from different commands does not seem to
belong together. The time stamps do not match. (11:06:07 vs 09:42:10 vs
09:41:32)

> $ cat /var/log/exim4/mainlog
[...]
> 2017-04-16 09:39:33 1czemS-0006A8-F3 Completed

Anything in paniclog? Does "exim4 -bV" report any errors? Are you able
to manually start a daemon instance?
update-exim4.conf && exim4 -bd -d

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-16 Thread Davide Prina

Package: exim4
Version: 4.89-1

Dear Maintainer,

I have the same problem


during upgrade/dist-upgrade or package installation I got this error:

# LANG=en_EN apt -u upgrade
[...]
Setting up exim4-daemon-light (4.89-1) ...
Job for exim4.service failed because of unavailable resources or another 
system error.

See "systemctl status exim4.service" and "journalctl -xe" for details.
invoke-rc.d: initscript exim4, action "start" failed.
● exim4.service - LSB: exim Mail Transport Agent
   Loaded: loaded (/etc/init.d/exim4; generated; vendor preset: enabled)
   Active: failed (Result: resources) since Sun 2017-04-16 11:06:07 
CEST; 6ms ago

 Docs: man:systemd-sysv-generator(8)
  Process: 3884 ExecStart=/etc/init.d/exim4 start (code=exited, 
status=0/SUCCESS)


Apr 16 11:06:06 davide systemd[1]: Starting LSB: exim Mail Transport 
Agent...

Apr 16 11:06:07 davide exim4[3884]: Starting MTA:.
Apr 16 11:06:07 davide systemd[1]: exim4.service: PID file 
/run/exim4/exim.pid not readable (yet?) after start: No such file or 
directory
Apr 16 11:06:07 davide systemd[1]: Failed to start LSB: exim Mail 
Transport Agent.

Apr 16 11:06:07 davide systemd[1]: exim4.service: Unit entered failed state.
Apr 16 11:06:07 davide systemd[1]: exim4.service: Failed with result 
'resources'.

dpkg: error processing package exim4-daemon-light (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of exim4:
 exim4 depends on exim4-daemon-light | exim4-daemon-heavy | 
exim4-daemon-custom; however:

  Package exim4-daemon-light is not configured yet.
  Package exim4-daemon-heavy is not installed.
  Package exim4-daemon-custom is not installed.

dpkg: error processing package exim4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-daemon-light
 exim4
E: Sub-process /usr/bin/dpkg returned an error code (1)




$ systemctl status exim4.service
● exim4.service - LSB: exim Mail Transport Agent
   Loaded: loaded (/etc/init.d/exim4; generated; vendor preset: enabled)
   Active: failed (Result: resources) since Sun 2017-04-16 09:42:10 
CEST; 1h 10min ago

 Docs: man:systemd-sysv-generator(8)
  Process: 30201 ExecStart=/etc/init.d/exim4 start (code=exited, 
status=0/SUCCESS)


apr 16 09:42:10 davide systemd[1]: Starting LSB: exim Mail Transport 
Agent...

apr 16 09:42:10 davide exim4[30201]: Starting MTA:.
apr 16 09:42:10 davide systemd[1]: exim4.service: PID file 
/run/exim4/exim.pid not readable (yet?) after start: No such file or 
directory
apr 16 09:42:10 davide systemd[1]: Failed to start LSB: exim Mail 
Transport Agent.
apr 16 09:42:10 davide systemd[1]: ^[[0;1;39mexim4.service: Unit entered 
failed state.
apr 16 09:42:10 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with 
result 'resources'.



$ journalctl -xe
[...]
-- Subject: Unit exim4.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit exim4.service has begun starting up.
Apr 16 09:41:32 davide exim4[29501]: Starting MTA:.
Apr 16 09:41:32 davide systemd[1]: exim4.service: PID file 
/run/exim4/exim.pid not readable (yet?) after start: No such file or 
directory
Apr 16 09:41:32 davide systemd[1]: Failed to start LSB: exim Mail 
Transport Agent.

-- Subject: Unit exim4.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit exim4.service has failed.
--
-- The result is failed.
Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Unit entered 
failed state.
Apr 16 09:41:32 davide systemd[1]: ^[[0;1;39mexim4.service: Failed with 
result 'resources'.

[...]


# ls -l /run/exim4/
totale 0



# LANG=en_EN apt install --reinstall exim4
[...]
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for exim4:amd64


I have see bug #854896, but I don't think it is the same problem:

ip6 is enabled:

$ ping ::1
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.043 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.058 ms
[...]

$ ip addr
[...]
inet6 fe80::5ae6:3341:7f38:c2e1/64 scope link
[...]

I try to reconfigure exim4

I try to set domainame (previously was (none))


$ cat /var/log/exim4/mainlog
2017-04-16 07:35:36 1czcqW-0004au-4l <= root@davide.prina U=root P=local 
S=72806
2017-04-16 07:35:36 1czcqW-0004au-4l => davide  
R=local_user T=mail_spool

2017-04-16 07:35:36 1czcqW-0004au-4l Completed
2017-04-16 08:07:04 1czdKy-0005z8-Nm <= daemon@davide.prina U=daemon 
P=local S=67278
2017-04-16 08:07:05 1czdKy-0005z8-Nm => davide  
R=local_user T=mail_spool

2017-04-16 08:07:05 1czdKy-0005z8-Nm Completed
2017-04-16 09:39:32 1czemS-0006A8-F3 <= root@davide.prina U=root P=local 
S=2767
2017-04-16 09:39:33 1czemS-0006A8-F3 => davide  
R=local_user T=mail_spool

2017-04-16 09:39:33 1czemS-0006A8-F3 

Bug#860317: upgrade to latest stretch version breaks

2017-04-15 Thread Andreas Metzler
On 2017-04-14 "Brent S. Elmer"  wrote:
> Package: exim4
> Version: 4.89-1
> Severity: normal

> I upgraded packages in stretch and there was a problem upgrading exim4.  When 
> I
> try to do a reinstall of exim4 to try to fix it using synaptic, I get:

[...]
> Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail Transport Agent...
> Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
> Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
> /var/log/exim4/pa…oken
> Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
> /run/exim4/exim.…tory
> Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never wrote its
> PI…ing.
> Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim Mail
> Transport…ent.

Anything in the exim logfiles?

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#860317: upgrade to latest stretch version breaks

2017-04-14 Thread Brent S. Elmer
Package: exim4
Version: 4.89-1
Severity: normal

I upgraded packages in stretch and there was a problem upgrading exim4.  When I
try to do a reinstall of exim4 to try to fix it using synaptic, I get:

E: Internal Error, No file name for exim4:amd64

When I upgrade or reinstall any other random package, configuration of exim4
gives errors:

(Reading database ... 666472 files and directories currently installed.)
Preparing to unpack .../anacron_2.3-23_amd64.deb ...
Unpacking anacron (2.3-23) over (2.3-23) ...
Processing triggers for systemd (232-22) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up exim4-daemon-light (4.89-1) ...
Job for exim4.service failed because of unavailable resources or another system
error.
See "systemctl status exim4.service" and "journalctl -xe" for details.
invoke-rc.d: initscript exim4, action "start" failed.
● exim4.service - LSB: exim Mail Transport Agent
   Loaded: loaded (/etc/init.d/exim4; generated; vendor preset: enabled)
   Active: failed (Result: resources) since Fri 2017-04-14 08:30:06 CDT; 5ms
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 27992 ExecStart=/etc/init.d/exim4 start (code=exited,
status=0/SUCCESS)
  CPU: 145ms

Apr 14 08:30:06 brente systemd[1]: Starting LSB: exim Mail Transport Agent...
Apr 14 08:30:06 brente exim4[27992]: Starting MTA: exim4.
Apr 14 08:30:06 brente exim4[27992]: ALERT: exim paniclog
/var/log/exim4/pa…oken
Apr 14 08:30:06 brente systemd[1]: exim4.service: PID file
/run/exim4/exim.…tory
Apr 14 08:30:06 brente systemd[1]: exim4.service: Daemon never wrote its
PI…ing.
Apr 14 08:30:06 brente systemd[1]: Failed to start LSB: exim Mail
Transport…ent.
Apr 14 08:30:06 brente systemd[1]: exim4.service: Unit entered failed state.
Apr 14 08:30:06 brente systemd[1]: exim4.service: Failed with result
'resou…es'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package exim4-daemon-light (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up anacron (2.3-23) ...
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and overrides
insserv: warning: script 'vpnagentd_init' missing LSB tags and overrides
dpkg: dependency problems prevent configuration of exim4:
 exim4 depends on exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-
custom; however:
  Package exim4-daemon-light is not configured yet.
  Package exim4-daemon-heavy is not installed.
  Package exim4-daemon-custom is not installed.

dpkg: error processing package exim4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 exim4-daemon-light
 exim4

Not all changes and updates succeeded. For further details of the failure,
please expand the 'Details' panel below.





-- Package-specific info:
Exim version 4.89 #2 built 09-Mar-2017 16:49:47
Copyright (c) University of Cambridge, 1995 - 2017
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2017
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM DNSSEC Event 
OCSP PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='local'
dc_other_hostnames='localhost.localdomain'
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost=''
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost=''
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname=''
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:localhost.localdomain

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.2.170124 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of