Hide Forgot
Description of problem: I'm running a system where I have /home on NFS and use NIS (should be unrelated). My local network is managed by the network service. Version-Release number of selected component (if applicable): # rpm -qf /etc/init.d/sandbox policycoreutils-2.0.85-27.fc15.x86_64 rpm -q systemd systemd-22-1.fc15.x86_64 How reproducible: Unsure, but it hung each time I rebooted and the sandbox service was enabled. Disabling it, made it work again. Steps to Reproduce: 1. enable network service (systemctl enable network.service) 2. disable NetworMangager service (systemctl disable NetworkManager.service) 3. Make /home NFS mounted (I have comment=systemd.automount for my /home in /etc/fstab) 4. Reboot 5. System hangs when trying to bring up the sandbox service (probably, due to the fact that the network is not up yet) Actual results: System hangs on boot when attempting to start the sandbox service (I probably did not sit it out long enough; maybe it's just taking a very long time). Expected results: No hang on boot (maybe disable sandbox or do something otherwise reasonable). Additional info: Let me know if you need more :) Thanks!
I forgot to mention that the my current workaround is to disable the sandbox service. No idea why it was enabled in the first place :)
Any chance you can log in while this is hanging and get us an output of "ps xawf -eo pid,args,cgroup"? If you wait 3min, does the boot finish?
As far as I remember, this happens too early in the boot process. I.e. before any getty's get started. So I'm unsure how I would be able to log in an provide this info :) I'll enable the sandbox service later today and will report back what I find.
Ok, so here is what I found: This is only happening if the network service is used instead of NetworkManager. If the latter is used and the sandbox service is enabled, my /home mount fails. Probably, because /home is an NFS share with root squashing turned on and sandbox wants to do something in /home as root. Anyhow, back to the network + NFS + sandbox issue: 1. This is way too early in the boot process to be able to log in and issue any command. In fact, the only key combination which has any effect is ctrl+alt+DEL (which reboots). The only way to fix this is to boot into single user mode and disable the sandbox service. 2. Waiting 5 minutes does not change anything. It hangs and it looks like it's hanging there forever. If you have any more thoughts on this, please let me know. Thanks!
I figure this is sandbox doing bind mounts on /home. I am not even sure this can work properly if an fs without labelling is used, such as NFS. I figure netfs is spawned start from the network hook scripts and this conflicts with sandbox in some way... might be a bug that is unrelated to systemd.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Is this still a problem or can this bug be closed?
Closing this bug as notabug until confirmed otherwize If this is still an issue feel free to reopen it thanks.