You are not logged in.
Recently I've started having bluetoothd, systemd-timesyncd and systemd-timedated failing with the same error,
Main process exited, code=exited, status=226/NAMESPACE
A search of the forums for "systemd 226/NAMESPACE" only turns up a thread called What does "status=226/NAMESPACE" mean?, where it turned out that /var/tmp was symlinked to /tmp. Needless to say, mine isn't, otherwise I wouldn't be asking here. Also systemd doesn't seem to document the meaning of its 'status' codes, so there basically isn't any information to go on. What's causing this error and how to fix it? [Bonus points for documentation of systemd's error codes]
Last edited by PBS (2016-10-01 16:38:12)
Offline
I hadn't noticed this previously:
systemd[476]: systemd-timesyncd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-timesyncd: Too many levels of symbolic links
systemd[1]: systemd-timesyncd.service: Main process exited, code=exited, status=226/NAMESPACE
The "Failed at step NAMESPACE spawning" part is quite common, but the message printed after it is usually one of
Operation not permitted
No such file or directory
Permission denied
Whereas the message I've got is "Too many levels of symbolic links". What has too many symbolic links?
Offline
Do you have any other directories symlinked (e.g homedir)?
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
/root is symlinked to /home/root, but no other home directories are. That shouldn't make a difference?
Offline
systemd-timesyncd.service has "ProtectHome=yes" which means it protects /root too. I'm not sure if it handles symlinks though.
All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.
Offline
I changed /root back to being a normal directory¹ and now everything works. Cheers!
Not sure why it worked until now, either systemd or some unit files must have changed.
_______________
¹ If you're wondering why /root was a link in the first place, it was to stop root's bash history leaking out of the encrypted /home partition.
Offline