I just updated a system - as in minutes ago, and log back in after it
reboots, and this is in dmesg:
[ 88.202272] systemd-readahead[484]:
open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many
levels of symbolic links
[ 88.202515] systemd-readahead[484]:
open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service)
failed: Too many levels of symbolic links
Anyone know what this is - some weird bug, a garbage message?
mark
I'm not sure why it's trying to open anything in /var/tmp to be honest. Jacked up filesystem maybe? Granted I know very little about systemd except it sucks on levels that I can't begin to explain. On 06/07/2017 10:10 AM, m.roth at 5-cent.us wrote:> I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) > failed: Too many levels of symbolic links > > Anyone know what this is - some weird bug, a garbage message? > > mark > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote:> I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) > failed: Too many levels of symbolic links > Anyone know what this is - some weird bug, a garbage message?systemd-readahead is just trying to pre-cache stuff into memory so boot time is faster. I'm not sure eaxctly what's going on here but that message is typical of having a loop in your symbolic links (which can easily happen with relative links). I'm not quite sure what *exactly* is going on, but it looks like maybe dracut temp files didn't get cleaned up properly and that they contain such a loop. I bet you can just rm -rf /var/tmp/dracut.fP4yj1. -- Matthew Miller <mattdm at fedoraproject.org> Fedora Project Leader
Matthew Miller wrote:> On Wed, Jun 07, 2017 at 10:10:14AM -0400, m.roth at 5-cent.us wrote: >> I just updated a system - as in minutes ago, and log back in after it >> reboots, and this is in dmesg: >> [ 88.202272] systemd-readahead[484]: >> open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many >> levels of symbolic links >> [ 88.202515] systemd-readahead[484]: >> open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) >> failed: Too many levels of symbolic links >> Anyone know what this is - some weird bug, a garbage message? > > systemd-readahead is just trying to pre-cache stuff into memory so boot > time is faster. I'm not sure eaxctly what's going on here but that > message is typical of having a loop in your symbolic links (which can > easily happen with relative links). > > I'm not quite sure what *exactly* is going on, but it looks like maybe > dracut temp files didn't get cleaned up properly and that they contain > such a loop. I bet you can just rm -rf /var/tmp/dracut.fP4yj1. >Thanks for the info. Now, why it shouldn't have cleaned itself up when I gave it the reboot command... I see too many (that's defined as more than zero) cases where systemd WANTS TO BOOT FAST, and doesn't wait for things to finish - sush as not getting the hostname from dhcp, and so having to hardcode the name instead. Systemd, as I've said before, seems to be targeted towards laptops. Not servers. Not workstations. *bleah* mark
On 06/07/2017 09:10 AM, m.roth at 5-cent.us wrote:> I just updated a system - as in minutes ago, and log back in after it > reboots, and this is in dmesg: > [ 88.202272] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/bin/loginctl) failed: Too many > levels of symbolic links > [ 88.202515] systemd-readahead[484]: > open(/var/tmp/dracut.fP4yj1/initramfs/usr/lib/systemd/system/dracut-emergency.service) > failed: Too many levels of symbolic links > > Anyone know what this is - some weird bug, a garbage message?Before this turns into another 200 email flame war about systemd .. this list is NOT the place to discuss if systemd is good or bad, nor whether it should be in a CentOS Linux distro or not. CentOS rebuilds source code for RHEL as released by Red Hat. If that source code uses GNOME 3.14 instead of GNOME 3.18 .. or if it uses mariadb instead of mysql .. or if it uses systemd or sysv init .. is not relevant to how we build CentOS Linux or what CentOS Linux is. If you want to influence what is in upstream RHEL (so therefore what gets released as source code, and therefore becomes part of CentOS Linux), Red Hat has mechanisms in place where that happens for both Fedora and RHEL. This is not one of those mechanisms. CentOS rebuilds the source code that is put out, nothing more. No one is making anyone use CentOS Linux, or like what it contains. If you don't like CentOS, don't use it. If you don't like systemd but want to use CentOS Linux, use CentOS-6, which does not have systemd. If you want to create a CentOS-7 variant that does not use systemd, then start a Special Interest Group and create modified packages to use something else instead, much like the this group did with Debian: https://devuan.org/ In the case of CentOS-7 .. you don't need to create a whole new distro, you can just petition the CentOS Project Board to create a Special Interest Group to get access to CentOS Project controlled resources to build packages (and get them rolled into our mirrors, etc.) to use something other than systemd. But just whining about not liking content in CentOS Linux in general, or systemd in particular, is not productive. Use CentOS if you want, if you don't that is fine. If you want something major changed .. this is open source and we provide mechanisms to make such changes (Special Interest Groups), so use them. I am NOT saying that Mark (or anyone else) is whining at this point .. I just picked the original mail in this thread to post this email reminding how CentOS Linux works and to suggest how something constructive might be done instead of another irrelevant (to CentOS Linux) 'I like or I hate systemd' thread. Thanks, Johnny Hughes -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20170607/aaae3d7f/attachment-0001.sig>
On Wed, 2017-06-07 at 11:23 -0500, Johnny Hughes wrote:> If you want to create a CentOS-7 variant that does not use systemd, > then start a Special Interest Group and create modified packages > to use something else instead ......., much like the this group did > with Debian: > > https://devuan.org/ > > In the case of CentOS-7 .. you don't need to create a whole new > distro, you can just petition the CentOS Project Board to create a > Special Interest Group to get access to CentOS Project controlled > resources to build packages (and get them rolled into our mirrors, > etc.) to use something other than systemd.Excellent idea. I'll gladly sign any such petition :-) -- Regards, Paul. England, EU. England's place is in the European Union.