Bug#805385: marked as done (systemd: Systemd does not wait for ifup to finish before starting services)

Your message dated Tue, 17 Nov 2015 17:06:30 +0100 with message-id <564b5086.4090...@debian.org> and subject line Re: Bug#805385: systemd: Systemd does not wait for ifup to finish before starting services has caused the Debian Bug report #805385, regarding systemd: Systemd does not wait for ifup

Bug#805385: systemd: Systemd does not wait for ifup to finish before starting services

Am 17.11.2015 um 16:39 schrieb Claudio: > Package: systemd > Version: 215-17+deb8u2 > Severity: important > > Dear Maintainer, > > Systemd does not wait for the ifup process to finish before starting the > services. > This is particularly relevant when having multiple interfaces and services

Bug#805385: systemd: Systemd does not wait for ifup to finish before starting services

# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface

Bug#805385: systemd: Systemd does not wait for ifup to finish before starting services

Package: systemd Version: 215-17+deb8u2 Severity: important Dear Maintainer, Systemd does not wait for the ifup process to finish before starting the services. This is particularly relevant when having multiple interfaces and services configured to bind only to a specific ip/interface.

Bug#802897: (no subject)

Seems strange, because if I enter wrong passphrase, I am prompted for it once more without any problems. -- Yours sincerely, Jayson Willson ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#805042: journal is killed every minute by watchdog

Am 13.11.2015 um 18:29 schrieb Michael Biebl: > Might be an incomplete fix for #1505 and maybe we need something like > https://github.com/systemd/systemd/issues/1804 I don't get this issue with daily build from trunk-ci. So I'm not sure if it's worth investigating further and fixing that in a

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

Ritesh Raj Sarraf [2015-11-14 15:18 +0530]: > > > IPForward=yes > > > > I believe this is the problem. Because we do not enable iptables > > support in networkd, then it cannot set this flag. This should be unrelated. This is a sysctl, not iptables. > I am not sure on how this works in

Processed: Re: Bug#805042: journal is killed every minute by watchdog

Processing control commands: > severity -1 serious Bug #805042 [systemd] journal is killed every minute by watchdog Severity set to 'serious' from 'important' -- 805042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805042 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#805042: journal is killed every minute by watchdog

On Tue, Nov 17, 2015 at 06:11:09PM +0100, Michael Biebl wrote: > Am 13.11.2015 um 18:29 schrieb Michael Biebl: > > Might be an incomplete fix for #1505 and maybe we need something like > > https://github.com/systemd/systemd/issues/1804 > > I don't get this issue with daily build from trunk-ci. >

Bug#805344: systemd: ListenStream=6566 in saned.socket only causes systemd to listen on [::]:6566

Did you check if it is actually not reachable over IPv4? IPv6 sockets can also accept IPv4 connections unless configured not to do so. This is controlled system-wide via /proc/sys/net/ipv6/bindv6only which is "0" on my computer (which is the default according to man:systemd.socket(5)). And

Bug#805344: systemd: ListenStream=6566 in saned.socket only causes systemd to listen on [::]:6566

I was trying to run sane network scanning through socket activation, but with the provided saned.socket file systemd only listens on a v6 socket. I have to explicitly change ListenStream to 0.0.0.0:6656 to make it listen on v4. Did you check if it is actually not reachable over IPv4? IPv6

Bug#805344: systemd: ListenStream=6566 in saned.socket only causes systemd to listen on [::]:6566

Jens Georg writes: > I was trying to run sane network scanning through socket activation, but > with the provided saned.socket file systemd only listens on a v6 socket. > I have to explicitly change ListenStream to 0.0.0.0:6656 to make it > listen on v4. Did you check if

Bug#802897: race condition in systemd boot with cryptsetup password prompt

I believe my system is affected by this issue. I have tried the workaround posted by Jayson Willson. It seems to help sometimes, but I believe there is still a race condition. Most often, the system waits for me to enter a passphrase. I have seen it wait for several minutes without

Bug#804832: systemd-networkd fails to configure IPv4 Bridge Network

Thanks Martin. For the issue in itself, it now looks like something specific to systemd. I'll see if I can take it up with upstream devs. Thanks, Ritesh On Tue, 2015-11-17 at 17:44 +0100, Martin Pitt wrote: > Ritesh Raj Sarraf [2015-11-14 15:18 +0530]: > > > > IPForward=yes > > > > > > I