On 12/16/2014 06:13 PM, Julien Cristau wrote:
I'm pretty sure what you ran into is a different issue, see
https://bugs.debian.org/771943.
Cheers,
Julien
You're right. It looks more like the bug you mentioned.
Best regards,
Jochen
--
To UNSUBSCRIBE, email to
On Mon, Dec 15, 2014 at 13:34:28 +0100, Jochen Bartl wrote:
Hi *,
I ran into the same problem. The boot time has increased almost by one
minute since an upgrade recently.
$ sudo systemd-analyze blame
1min 1.970s networking.service
1.158s systemd-udev-settle.service
Hi *,
I ran into the same problem. The boot time has increased almost by one
minute since an upgrade recently.
$ sudo systemd-analyze blame
1min 1.970s networking.service
1.158s systemd-udev-settle.service
1.145s uml-utilities.service
409ms tor.service
...
Control: tag -1 moreinfo
On Lu, 01 dec 14, 18:15:22, tv.deb...@googlemail.com wrote:
I did so, when switching to VT 9 the screen is spamed with the systemd
message about starting LSB. I typed blindly journalctl -alb and
noticed that a shell session was indeed active behind the spam wall !
On Wed, 10 Dec 2014 12:23:15 +0200 Andrei POPESCU
andreimpope...@gmail.com wrote:
Control: tag -1 moreinfo
On Lu, 01 dec 14, 18:15:22, tv.deb...@googlemail.com wrote:
I did so, when switching to VT 9 the screen is spamed with the systemd
message about starting LSB. I typed blindly
On 2014-12-01 16:32, Michael Biebl wrote:
Does the system itself boot correctly?
Yes.
How does your /etc/network/interfaces look like?
Default configuration. Like Stefano Zacchiroli's, without last two IPv6
lines:
Dear all,
same happening here:
Debian Jessie/Unstable amd64 up-to-date.
systemd: Version : 215-7
shorewall installed and configured
NO nfs mount of any kind
NO network mount of any kind
NetworkManager NOT installed (/etc/network/interfaces used)
NO local custom init script
Additionally
On Lu, 01 dec 14, 14:12:01, tv.deb...@googlemail.com wrote:
I can reinstall systemd as init and make the system fail again (outside of
office hours ;-) ) if provided with direction as to how collect additional
information.
Please enable the debug console on VT9 (boot with
On Mon, 1 Dec 2014 13:35:04 +0200 Andrei POPESCU
andreimpope...@gmail.com wrote:
On Lu, 01 dec 14, 14:12:01, tv.deb...@googlemail.com wrote:
I can reinstall systemd as init and make the system fail again
(outside of
office hours ;-) ) if provided with direction as to how collect
Package: systemd
Version: 215-7
I can't help, don't even know if this is systemd related,
but I've noticed about 15 seconds delay while looking at:
[ *** ] A start job is running for LSB: Raise network interfaces.
since recent ifupdown 0.7.50 upgrade.
apt-get --reinstall install
Am 01.12.2014 um 16:57 schrieb Alex Mayer:
Package: systemd
Version: 215-7
I can't help, don't even know if this is systemd related,
but I've noticed about 15 seconds delay while looking at:
[ *** ] A start job is running for LSB: Raise network interfaces.
since recent ifupdown
I'm having the same issue,... so maybe it comes from #766943?
I've only checked the fix for that on the server nodes (where that delay
of 1-2 mins doesn't really get noticed) - not on my desktop node.
Cheers,
Chris.
smime.p7s
Description: S/MIME cryptographic signature
Am 01.12.2014 um 17:48 schrieb Christoph Anton Mitterer:
I'm having the same issue,... so maybe it comes from #766943?
Very likely, yes. If you use DHCP, it can easily take a few seconds for
your network to be configured.
And now that /etc/init.d/networking both handles allow-hotplug and auto
On Mon, 2014-12-01 at 18:00 +0100, Michael Biebl wrote:
Very likely, yes. If you use DHCP, it can easily take a few seconds for
your network to be configured.
And now that /etc/init.d/networking both handles allow-hotplug and auto
interfaces and blocks for ifup to complete for those
Am 01.12.2014 um 18:08 schrieb Christoph Anton Mitterer:
On Mon, 2014-12-01 at 18:00 +0100, Michael Biebl wrote:
Very likely, yes. If you use DHCP, it can easily take a few seconds for
your network to be configured.
And now that /etc/init.d/networking both handles allow-hotplug and auto
On Mon, 2014-12-01 at 18:55 +0100, Michael Biebl wrote:
Not quite sure what you mean with other fix? Can you elaborate?
I mean the udevsettle, which apparently causes this delay now...
I just see it coming that gazillions of people cause to whine about that
delay :(
For jessie we decided to
I stumbled over this bug while investigating the same symptoms on my
laptop with testing.
After a loss of power I rebooted and it seemingly hung on fsck (last
visible line was something with systemd-fsck), but on rebooting in
recovery I got the
[ *** ] A start job is running for LSB: Raise
Today, after upgrading kde, sysvinit-core was replaced with systemd-sysv
208-8. Reboot gives the same error.
Boot becomes normal after auto entries were committed out in
/etc/network/interfaces (except lo). Not workable file is attached.
--
sergio.
# This file describes the network interfaces
Am 04.09.2014 um 01:43 schrieb sergio:
Today, after upgrading kde, sysvinit-core was replaced with systemd-sysv
208-8. Reboot gives the same error.
Boot becomes normal after auto entries were committed out in
/etc/network/interfaces (except lo). Not workable file is attached.
Could you
On 09/04/2014 04:29 AM, Michael Biebl wrote:
Could you please send me all files from /etc/network/ and
/etc/dhcp/ (as tarball).
There are no custom files in /etc/network, do you really need them?
% ls -R /etc/network
/etc/network:
if-down.d/ if-post-down.d/ if-pre-up.d/ if-up.d/
On Sat, Jul 26, 2014 at 11:43:51PM +0200, Michael Biebl wrote:
I think we should do two things:
1/ document in the release notes / systemd FAQ that restarting services
from hooks script (ifupdown, dhclient, etc) is problematic.
2/ change
Am 10.07.2014 17:05, schrieb Stefano Zacchiroli:
On Wed, Jul 09, 2014 at 05:31:57PM +0200, Michael Biebl wrote:
So, try to guard your restarts like this:
===
if [ -d /run/systemd/system ]; then
systemctl list-jobs | grep -q network.target exit 0
fi
service shorewall restart
On Wed, Jul 09, 2014 at 05:31:57PM +0200, Michael Biebl wrote:
So, try to guard your restarts like this:
===
if [ -d /run/systemd/system ]; then
systemctl list-jobs | grep -q network.target exit 0
fi
service shorewall restart
service shorewall6 restart
===
This did the trick!
Thanks for your analysis, it explains what's happening.
On Wed, Jul 09, 2014 at 01:18:33AM +0200, Michael Biebl wrote:
Am 09.07.2014 01:14, schrieb Michael Biebl:
So, what to do about this: I'd say it's a bug to (re)start a SysV init
script from an if-up.d hook without actually checking if
Am 09.07.2014 13:51, schrieb Stefano Zacchiroli:
I've tried this, and it does make the boot complete successfully.
However, as a consequence, the shorewall service is not running after
boot (because for some reason it fails to properly start the first
time), and will never be running again
On Wed, Jul 09, 2014 at 02:04:49PM +0200, Michael Biebl wrote:
What's the output of
ls -la /etc/rc?.d/???shorewall
and
ls -la /etc/rc?.d/???shorewall6
$ ls -la /etc/rc?.d/???shorewall
lrwxrwxrwx 1 root root 19 apr 27 15:43 /etc/rc0.d/K01shorewall -
../init.d/shorewall
lrwxrwxrwx 1
Am 09.07.2014 16:45, schrieb Stefano Zacchiroli:
On Wed, Jul 09, 2014 at 02:04:49PM +0200, Michael Biebl wrote:
What's the output of
ls -la /etc/rc?.d/???shorewall
and
ls -la /etc/rc?.d/???shorewall6
$ ls -la /etc/rc?.d/???shorewall
lrwxrwxrwx 1 root root 19 apr 27 15:43
Package: systemd
Version: 204-14
Severity: serious
I've rebooted today my laptop (Debian testing) and it failed to boot, hanging
forever on the message:
[ *** ] A start job is running for LSB: Raise network interfaces.
with the 3 asterisks moving back and forth.
I've been using systemd-sysv
Am 08.07.2014 21:20, schrieb Stefano Zacchiroli:
Package: systemd
Version: 204-14
Severity: serious
I've rebooted today my laptop (Debian testing) and it failed to boot, hanging
forever on the message:
[ *** ] A start job is running for LSB: Raise network interfaces.
Did you actually
On Tue, Jul 08, 2014 at 09:32:43PM +0200, Michael Biebl wrote:
Did you actually wait forever, i.e. at least 90 seconds which is the
usual timeout for devices to appear or services to start?
Obviously I didn't wait *forever* :), but yes, I did wait past usual
network timeouts. To be sure, I've
On Tue, Jul 08, 2014 at 10:50:27PM +0200, Stefano Zacchiroli wrote:
#!/bin/sh
[...]
service $FIREWALL restart
service $FIREWALL6 restart
After a couple of killall local-firewall (one for each service
invocation,
Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
Now the questions/comments:
- I've had that script since ever, basically, and it used to work fine
in the past, both before and after switching to systemd as init. I'm
not sure why/when it stopped working.
- As a mere user, the above
Am 09.07.2014 01:14, schrieb Michael Biebl:
So, what to do about this: I'd say it's a bug to (re)start a SysV init
script from an if-up.d hook without actually checking if the service is
actually already runnig.
Because you simply disregard any dependencies which have been specified
in the
Am 09.07.2014 01:14, schrieb Michael Biebl:
Am 08.07.2014 22:50, schrieb Stefano Zacchiroli:
Now the questions/comments:
- I've had that script since ever, basically, and it used to work fine
in the past, both before and after switching to systemd as init. I'm
not sure why/when it
Am 09.07.2014 01:28, schrieb Michael Biebl:
Running within the context of an if-up.d hook you make an explicit
assumption that $network is already provided, which is probably reasonable.
Strictly speaking though, the LSB $network facility is defined in
/etc/insserv.conf when the networking
35 matches
Mail list logo
