Bug#790448: [systemd] Regression from 215-18: Shutdown delayed for minutes waiting for automounted CIFS

[Gavrilov Aleksey]

I did so, but it also did not help.
Later, I thought that it is necessary to localize the error in a clean 
environment.
I created a virtual machine in proxmox. And to my surprise it worked 
correctly.
After that I thought that the problem in my pc.
I also created a clean installation. Here, the error itself has shown.

After that I decided to review the logs.
The kvm I have noticed that these lines are the sequence.
...

Apr 01 12:07:11 test-bug-debian-790448 systemd-networkd[349]: lo              : gained carrier
Apr 01 12:07:11 test-bug-debian-790448 systemd-networkd[349]: eth0            : link configured
Apr 01 12:07:11 test-bug-debian-790448 systemd-networkd[349]: eth0            : gained carrier
Apr 01 12:07:11 test-bug-debian-790448 systemd-networkd[349]: eth0            : DHCPv4 address 192.168.204.202/24 via 192.168.204.4
Apr 01 12:07:11 test-bug-debian-790448 systemd-networkd[349]: eth0            : link configured

...
And on my pc they are scattered throughout the file and have strange 
messages from the kernel.
...

Apr 01 11:32:19 debian kernel: r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168e-3.fw
Apr 01 11:32:19 debian systemd-networkd[179]: eth0            : link configured
Apr 01 11:32:19 debian kernel: r8169 0000:02:00.0 eth0: link down
Apr 01 11:32:19 debian kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Apr 01 11:32:19 debian kernel: r8169 0000:02:00.0 eth0: link down

...

Apr 01 11:32:21 debian systemd-networkd[179]: eth0            : gained carrier
Apr 01 11:32:21 debian kernel: r8169 0000:02:00.0 eth0: link up
Apr 01 11:32:21 debian kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

...
Yes, on my pc with a clean installation of the network address is not 
assigned.
I manually assigned "dhcpclient eth0"


On 25.03.2016 18:26, Michael Biebl wrote:
> Am 25.03.2016 um 11:02 schrieb Gavrilov Aleksey:
>> Did 3 launch systems with different settings.
> Look at the logs for "Found ordering cycle".
> You have dependency cycles, which result in various services not being
> started.
> Most likely the culprit is "ferm.service". I'd start removing this
> service and then test if that you still have dependency cycles.
>
>

-- 

Sincerely, Gavrilov Aleksey
System Administrator
Ltd. "Hearst Shkulev Digital Rugion"
tel .: 8 (351) 729-94-90, ext. 345
mob. +7 999 581 7934
gavrilov at info74.ru
Chelyabinsk, st. Melkombinat February 1st Precinct, 18, office 208
for TRC `Rodnik`

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160401/b6a613d3/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian_kvm.log
Type: text/x-log
Size: 60054 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160401/b6a613d3/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debian_my_pc.log
Type: text/x-log
Size: 189833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160401/b6a613d3/attachment-0003.bin>