sudo service networking stop took less than a second, the echos are in
the /var/log/upstart/networking.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting for 10
Ok. I don't have any further theories at the moment as to what might be
causing this. Setting the bug back to 'new' for now.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've traced it to the
ifdown -a --exclude=lo
line in /etc/init/networking.conf
I've scheduled the shutdown to 10:08:00 and here is part of the log (nothing
except ifdown between these echos)
Thu Oct 3 10:08:01 EEST 2013
netw post 3
Thu Oct 3 10:08:11 EEST 2013
netw post end
--
You received
ifdown -a --exclude=lo
is instant on the running system.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- initctl waiting for 10 seconds before finishing in /etc/init.d/umountnfs.sh
+ initctl - ifdown waiting for 10 seconds before finishing
This command returns only once all of the jobs that are marked 'stop on
unmounted-remote-filesystems' have a chance to stop. Do you know what
jobs on your system are affected by this? Normally it will return quite
quickly. Unless you're using NFS, it's possible that
/etc/init/networking.conf is
No, I don't use NFS. Anything else I can add?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting for 10 seconds before finishing in
/etc/init.d/umountnfs.sh
To manage
What does /var/log/upstart/networking.log contain after reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting for 10 seconds before finishing in
It just doesn't exist. I have this:
$ grep log /etc/fstab
tmpfs /var/log tmpfs defaults 0 0
I'll try commenting it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting
Still doesn't exist even after creating /var/log/upstart And there are
some other upstart logs in there already. Nothing suspicious inside them
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also the networking script is the only one that runs
$ grep unmounted-remote-filesystems *
networking.conf:stop on unmounted-remote-filesystems
rc.conf:emits unmounted-remote-filesystems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've added an echo line to the very beginning of
/etc/init/networking.conf:post-stop script and I don't see it in these
10 seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
The echo wouldn't output to the screen, it would be logged to
/var/log/upstart/networking.log. Anything there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting for 10
And if you manually run 'sudo service networking stop' from a running
system, how long does that take to return?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting for 10
Oh, it must be executing all the scripts on unmounted-remote-
filesystems, isn't it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230056
Title:
initctl waiting for 10 seconds before finishing in
14 matches
Mail list logo
