Bug#766943: systemd: server no longer gets networking after switching to systemd

Christoph Anton Mitterer calestyo at scientia.net
Mon Oct 27 06:06:02 GMT 2014


On Mon, 2014-10-27 at 06:56 +0100, Christoph Anton Mitterer wrote: 
> # systemctl -l status sks.service 
> ● sks.service - (null)
>    Loaded: loaded (/etc/init.d/sks)
>    Active: active (running) since Mon 2014-10-27 06:52:22 CET; 4min 21s ago
>   Process: 1991 ExecStart=/etc/init.d/sks start (code=exited, status=0/SUCCESS)
...
> Oct 27 06:52:23 kronecker sks[1991]: 2014-10-27 06:52:23 Failed to listen on 2a01:4f8:a0:4024::2:2:11370: Failure("Failure while binding socket.  Probably another socket bound to this address")

FYI: I've reported the problem, that sks returns success, even though it
couldn't start up successfully as: #766949.


Cheers,
Chris.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5313 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141027/0770f853/attachment-0002.bin>


More information about the Pkg-systemd-maintainers mailing list