Bug 1201725

Can you attach the full boot log (journalctl -b) and systemctl status systemd-update-done.service ldconfig.service ? Do you have any special setup like read-only /etc?

It just disappeared as suddenly as it appeared. I can't reproduce it any more.
I don't have a read-only /etc.
journal shows nothing at all related to any ldconfig or linker cache things.

Created attachment 1003807 [details]
output of `journalctl -b` shortened to when systemd starts

And out of nothing It happened again:

$ systemctl status --full systemd-update-done.service ldconfig.service
● systemd-update-done.service - Update is Completed
   Loaded: loaded (/usr/lib/systemd/system/systemd-update-done.service; static)
   Active: active (exited) since Do 2015-03-19 12:06:37 CET; 2min 36s ago
     Docs: man:systemd-update-done.service(8)
  Process: 740 ExecStart=/usr/lib/systemd/systemd-update-done (code=exited, status=0/SUCCESS)
 Main PID: 740 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-update-done.service

● ldconfig.service - Rebuild Dynamic Linker Cache
   Loaded: loaded (/usr/lib/systemd/system/ldconfig.service; static)
   Active: active (exited) since Do 2015-03-19 12:06:37 CET; 2min 36s ago
     Docs: man:ldconfig(8)
  Process: 621 ExecStart=/sbin/ldconfig -X (code=exited, status=0/SUCCESS)
 Main PID: 621 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/ldconfig.service


So no note of ldconfig.service at all. No errors, nothing.

You asked me whether /etc was read-only. this is the details:
$ lsblkid
NAME                                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                                             8:0    0 465,8G  0 disk  
├─sda1                                          8:1    0     1M  0 part  
├─sda2                                          8:2    0     1G  0 part  /boot
└─sda3                                          8:3    0   300G  0 part  
  └─luks-some-UUID 253:0    0   300G  0 crypt /var

where the luks partition provides separate /var, /home and / mount points. No other partitions involved.

This job is run whenever /usr is updated. So any package update or change there will cause it to run.

> So no note of ldconfig.service at all. No errors, nothing.
It seems that this log is limited to log notice or higher. There are no systemd log messages at level info.

Maybe there's no problem. It would be helpful if you
1. got an actual log where the time that systemd actually starts the ldconfig.service job and where it finishes is shown
2. compared that time to running /sbin/ldconfig -X by hand.

>This job is run whenever /usr is updated. So any package update or change there will cause it to run.

Seems like there really is no problem. I never noticed that before. Is it possible that this behavior changed not long ago? Or that ldconfig just takes longer than before?

The service to (sometimes) run ldconfig on boot is relatively new (systmed-215).

ldconfig *might* be taking longer than before, but haven't really established that yet.

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.

The damn thing universally hold off boot up from live media for no less than 30 seconds, along with aforementioned screwing around on SSDs ! And that on system where package manager always performs ldconfig when it's needed. Whoever came up with this stuff should go into shame corner.

The hack to prevent it on live media is here: https://github.com/manjaro/release-plan/issues/17
On other systems that garbage probably should be masked.

Are you seeing this issue in a recent Fedora installation? Which version of ldconfig, systemd, …? If yes I'll change the Fedora version number, otherwise this bug will get closed.

PS: Your words could be chosen more friendly.

(In reply to Christian Stadelmann from comment #9)
> Are you seeing this issue in a recent Fedora installation? Which version of
> ldconfig, systemd, …? If yes I'll change the Fedora version number,
> otherwise this bug will get closed.

No, I use what was called "openSUSE Factory" and now - "The Tumbleweed Product" which tries to use the very latest packages, including systemd. I write here, because
1) this is where I got the first explanation of what's happening;
2) Red Hat is pretty much upstream of systemd and Fedora is where those genius ideas get tested.

> PS: Your words could be chosen more friendly.

When system that usually boots in about 10 seconds starts to fart around for 30-40 there are no friendlier words than this. After all, "the fast and efficient boot up" is one of major reasons why systemd got _universally_ adopted in the first place.

And if Fedora uses some kind of tricks to avoid that happening out of the box while other distroes don't, I really insist on adding those to systemd's source.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.

I haven't seen this issue any more. It only happened two or three times, then it was gone. You should see the same behaviour. Thus I don't think this issue is too problematic.