[systemd-devel] F25: NAMESPACE spawning: Too many levels of symbolic links

[Reindl Harald]

Am 16.03.2017 um 18:21 schrieb Michal Sekletar:
> On Thu, Mar 16, 2017 at 4:29 PM, Reindl Harald <h.reindl at thelounge.net> 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 at 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 at 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 at 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