since this breaks randomly user created sytemd units *unexpected* when tey are working fine over some fedora releases when will that be backported? in this shape there is no way to consider F25 on production machines and then look what falls left and right -------- Weitergeleitete Nachricht -------- Betreff: Re: [systemd-devel] F25: NAMESPACE spawning: Too many levels of symbolic links Datum: Thu, 16 Mar 2017 19:06:11 +0100 Von: Reindl Harald <h.reindl> An: Mailing-List systemd <systemd-devel.org> Am 16.03.2017 um 18:21 schrieb Michal Sekletar: > On Thu, Mar 16, 2017 at 4:29 PM, Reindl Harald <h.reindl> wrote: >> with systemd-229-18.fc24.x86_64 no problem at all - after upgrade to F25 >> "/usr/bin/vmware-networks" while this is just a phyiscal file and was not >> touched >> >> [root@rh:~]$ rpm -q systemd >> systemd-231-14.fc25.x86_64 >> >> Mar 16 16:25:23 rh systemd: vmware-vmnet.service: Failed at step NAMESPACE >> spawning /usr/bin/vmware-networks: Too many levels of symbolic links >> Mar 16 16:25:24 rh systemd: vmware-vmnet.service: Control process exited, >> code=exited status=226 >> Mar 16 16:25:24 rh systemd: Failed to start VMware Virtual Machine Ethernet. >> Mar 16 16:25:24 rh systemd: vmware-vmnet.service: Unit entered failed state. >> Mar 16 16:25:24 rh systemd: vmware-vmnet.service: Failed with result >> 'exit-code'. >> >> [root@rh:~]$ stat /usr/bin/vmware-networks >> File: '/usr/bin/vmware-networks' >> Size: 1189920 Blocks: 2328 IO Block: 4096 regular file >> Device: 901h/2305d Inode: 1308258 Links: 1 >> Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) >> Access: 2017-03-13 13:50:05.693010420 +0100 >> Modify: 2017-03-13 13:50:05.734010674 +0100 >> Change: 2017-03-13 13:50:05.764010860 +0100 >> Birth: - >> >> [root@rh:~]$ cat /etc/systemd/system/vmware-vmnet.service >> [Unit] >> Description=VMware Virtual Machine Ethernet >> After=vmware-modules.service >> Requires=vmware-modules.service >> Before=network.service systemd-networkd.service >> >> [Service] >> Type=forking >> ExecStart=/usr/bin/vmware-networks --start >> ExecStartPost=-/usr/sbin/sysctl -e -w net.ipv4.conf.vmnet8.forwarding=1 >> ExecStartPost=-/usr/sbin/sysctl -e -w net.ipv4.conf.vmnet8.log_martians=0 >> ExecStop=/usr/bin/vmware-networks --stop >> >> ReadOnlyDirectories=/usr >> InaccessibleDirectories=-/boot >> InaccessibleDirectories=-/home >> InaccessibleDirectories=-/media >> InaccessibleDirectories=-/data >> InaccessibleDirectories=-/mnt >> InaccessibleDirectories=-/mnt/data >> InaccessibleDirectories=-/root >> >> [Install] >> WantedBy=multi-user.target > > Is any of inaccessible directories actually symlink? If so then I > believe you are hitting, yes - /data on this machine while it's on others sharing that unit a physical directory > https://github.com/systemd/systemd/issues/3867 > > This is fixed upstream, but patches for this were not backported to > Fedora 25 yet. Here are Fedora bugs mentioning similar symptoms, > > https://bugzilla.redhat.com/show_bug.cgi?id=1399991 > https://bugzilla.redhat.com/show_bug.cgi?id=1414157
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.