Description of problem: multiple errors are reported at boot, mainly related to this message: "Too many levels of symbolic links" The list of services that are impacted on my system are: Nov 30 09:16:44 klimt systemd[1055]: bluetooth.service: Failed at step NAMESPACE spawning /usr/libexec/bluetooth/bluetoothd: Too many levels of symbolic links Nov 30 09:16:45 klimt systemd[1557]: systemd-hostnamed.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-hostnamed: Too many levels of symbolic links Nov 30 09:16:49 klimt systemd[1795]: systemd-localed.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-localed: Too many levels of symbolic links Version-Release number of selected component (if applicable): How reproducible: Just boot Steps to Reproduce: 1. 2. 3. Actual results: Expected results: No errors. Some of the errors have actually nasty side effect, like the example wrong language setup for my keyboard at login screen, that makes thing hard if you password has symbols in it Additional info: The full output of `journalctl -xb | gist` is here https://gist.github.com/anonymous/3466cfe1dda5715fddf570c355956fee Note: logs show some known issue with vbox modules, but I'm not expecting them to be the issue here.
One of the funny things is that the keyboard layout is correct when I decrypt my disk, but not at the user login prompt.
Do you have any of standard directories (/etc/, /var/, /tmp/, /root/, /home) as a symlink pointing to some other location?
Hi Michal, yes, I have /home linking to a folder in a different partition.
(In reply to Paolo Antinori from comment #3) > Hi Michal, yes, I have /home linking to a folder in a different partition. That will be a culprit. IIRC, there has been some work upstream done to get this fixed. I will look up those patches and I will backport them to Fedora.
Great, thank you!
after nothing changed over 3 weeks: https://bugzilla.redhat.com/show_bug.cgi?id=1436362
frankly that seems to be reported on 2016-11-30 03:40:51 EST which means 4 montsh which is nearly a fedora release cycle and when i asked weeks ago on the systemd-list there where even pointed to available patches wich are not backported to fedora so either backport them or consider slow down with systemd upgrades in Fedora
WTF - https://koji.fedoraproject.org/koji/buildinfo?buildID=897802 the first systemd build since F25 was released and this bug here is still not fixed WHEN THERE EXISTS A PATCH UPSTREAM OVER MONTHS?
https://koji.fedoraproject.org/koji/buildinfo?buildID=912529 * Tue Jun 27 2017 Zbigniew J?drzejewski-Szmek <zbyszek.pl> - 231-16 - Fix an out-of-bounds write in systemd-resolved (CVE-2017-9445) and again nobody cares about this regression - WTF - either upgrade systemd to a recent version without known regressions, backport regression fixes aas available or don't upgrade systemd at all as long it's every time a gambling machine "what's broken in this fedora realease"
fuck it - either fix that problem or output *which* of the dozens of ReadOnlyDirectories/InaccessibleDirectories are the one with the symlink Jul 3 13:03:31 buildserver systemd: Starting Update ClamAV-Signatures... Jul 3 13:03:31 buildserver systemd: distribute-clamav.service: Failed at step NAMESPACE spawning /usr/bin/bash: Too many levels of symbolic links Jul 3 13:03:31 buildserver systemd: distribute-clamav.service: Main process exited, code=exited, status=226/NAMESPACE Jul 3 13:03:31 buildserver systemd: Failed to start Update ClamAV-Signatures. Jul 3 13:03:31 buildserver systemd: distribute-clamav.service: Unit entered failed state. Jul 3 13:03:31 buildserver systemd: distribute-clamav.service: Failed with result 'exit-code'.
is it now policy that bugs in systemd are never fixed within a relase even if there are patches available ohr why do you need to upgrade to F26 to get rid of this one as well as the annyoing https://bugzilla.redhat.com/show_bug.cgi?id=1441997 i guess the one below will be fixed in F27/F28 - great - NOT -------- Weitergeleitete Nachricht -------- Betreff: [systemd-devel] SystemCallFilter=~@resources broken in F26/systemd233 Datum: Sat, 23 Sep 2017 15:38:27 +0200 Von: Reindl Harald <h.reindl> Organisation: the lounge interactive design An: Mailing-List systemd <systemd-devel.org> with Fedroa 25 that was no problem, on F26 httpd, mysqld and so on are breaking [root@testserver:~]$ rpm -q systemd systemd-233-6.fc26.x86_64 [root@testserver:~]$ rpm -q glibc glibc-2.25-10.fc26.x86_64 @resources System calls for changing resource limits, memory and scheduling parameters (setrlimit(2), setpriority(2) Process 7320 (php71) of user 0 dumped core.#012#012Stack trace of thread 7320:#012#0 0x00007fe043c14f29 __getrlimit (libc.so.6)#012#1 0x00007fe043c0e771 __get_child_max (libc.so.6)#012#2 0x00007fe043be5434 __sysconf (libc.so.6)#012#3 0x0000562a0c61062e getmaxchild (bash)#012#4 0x0000562a0c5c482c initialize_job_control (bash)#012#5 0x0000562a0c597929 shell_initialize (bash)#012#6 0x0000562a0c59b03d main (bash)#012#7 0x00007fe043b2f50a __libc_start_main (libc.so.6)#012#8 0x0000562a0c59be5a _start (bash)
do you want all the mails from the fileserver where /home is a symlink because of what rsyslog did not start and as followup "system-errors.sh" did not filter out that postfix also did not start (yes /home anchored with - is here ReadOnlyDirectories for every single server software) GOD DAMNED blind on a whole machine after the F25 dist-upgrade and only by luck i realized short ago that rsyslog never was started and after kernel update *now* i "fixed" postfix too by remove that line for now you guys seem to have no idea what breakage you trigger left and right boy not fixing bugs in systemd at all
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.