Bug 701669 - AssertionError in systemd-analyze when invoked while boot is still in progress
Summary: AssertionError in systemd-analyze when invoked while boot is still in progress
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 16
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 714001 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-03 14:11 UTC by Lukas Middendorf
Modified: 2012-06-05 23:10 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-29 10:34:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lukas Middendorf 2011-05-03 14:11:50 UTC
Description of problem:
I have some file systems which are managed as automount points by systemd. When one of them requires a fsck it is possible to log in and invoke systemd-analyze before the fsck and the boot process is done.

systemd-analyze then outputs
Traceback (most recent call last):
  File "/usr/bin/systemd-analyze", line 82, in <module>
    initrd_time, start_time, finish_time = acquire_start_time()
  File "/usr/bin/systemd-analyze", line 35, in acquire_start_time
    assert startup_time <= finish_time
AssertionError

Version-Release number of selected component (if applicable):
systemd-26-1.fc15.i686

How reproducible:
didn't try

Steps to Reproduce:
1. set up a file system as systemd automount
2. make sure a file system check is forced for the file system
3. reboot
4. log in and invoke "systemd-analyze" while fsck is still running
  
Actual results:
Traceback (most recent call last):
  File "/usr/bin/systemd-analyze", line 82, in <module>
    initrd_time, start_time, finish_time = acquire_start_time()
  File "/usr/bin/systemd-analyze", line 35, in acquire_start_time
    assert startup_time <= finish_time
AssertionError

Expected results:
A sane error message


Additional info:

Comment 1 Michal Schmidt 2011-06-17 08:01:20 UTC
*** Bug 714001 has been marked as a duplicate of this bug. ***

Comment 2 Andy Lawrence 2011-10-08 13:12:48 UTC
Package: systemd-36-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
Ran systemd-analyze just after boot as a regular user.

Comment 3 Fedora Admin XMLRPC Client 2011-10-20 16:27:08 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Harald Hoyer 2011-11-03 15:38:39 UTC
Package: systemd-36-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
run "systemd-analyze" after booting

Comment 5 François Kooman 2011-11-20 21:00:04 UTC
Package: systemd-37-3.fc16
Architecture: x86_64
OS Release: Fedora release 16 (Verne)

Comment
-----
just running systemd-analyze without parameters

Comment 6 Jóhann B. Guðmundsson 2012-01-24 13:09:32 UTC
Is this still a problem or can this bug be closed?

Comment 7 Michael Cronenworth 2012-01-24 14:06:49 UTC
I still had systemd-analyze crash on me the other day for the same reason.

Comment 8 nikbeier 2012-02-22 14:26:40 UTC
systemd default target was set to multi-user.target
RAM-disk and rhgb removed from grub/kernel command line.
pc rebooted, logged in at the console

Then systemd-analyze fails. But if I switch to the rescue target, systemd-analyze works again.

with graphical target, the system hangs, perhaps waiting for plymouth to finish, when Gnome is about to start. so that might be related.


Package: systemd-37-13.fc16
OS Release: Fedora release 16 (Verne)

Comment 9 Michal Schmidt 2012-02-22 17:39:10 UTC
The assertion triggers when you manage to run systemd-analyze before the system has finished booting from systemd's point of view.

For instance, getty may be already running, but sendmail can be taking a minute to start. For systemd this means that multi-user.target has not yet started. You can recognize such a situation in the output of "systemctl list-jobs".

We should fix systemd-analyze, but it is really a developer tool and we won't even install it by default in F17, so it's low priority.

Comment 11 dominique 2012-04-22 15:51:27 UTC
I want launch systemd-analyse time in console, and I have this error message

Package: systemd-analyze-44-4.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 12 Matthias Kuhn 2012-05-17 15:00:40 UTC
I typed systemd-analyse and hit enter

Package: systemd-37-19.fc16
OS Release: Fedora release 16 (Verne)

Comment 13 Pratyush Sahay 2012-05-17 16:52:40 UTC
Running systemd-analyze time after install and restart

Package: systemd-analyze-44-8.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 14 Fedora Update System 2012-05-18 23:38:48 UTC
systemd-44-9.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/systemd-44-9.fc17

Comment 15 Fedora Update System 2012-05-18 23:57:25 UTC
systemd-37-20.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/systemd-37-20.fc16

Comment 16 Fedora Update System 2012-05-19 18:34:01 UTC
Package systemd-44-9.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-44-9.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-8127/systemd-44-9.fc17
then log in and leave karma (feedback).

Comment 17 Pratyush Sahay 2012-05-24 11:08:06 UTC
Running systemd-analyze time just after login, when time taking processes like sendmail are still active in the boot process.

Package: systemd-analyze-44-8.fc17
OS Release: Fedora release 17 (Beefy Miracle)

Comment 18 Fedora Update System 2012-05-29 10:34:42 UTC
systemd-44-12.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 19 Fedora Update System 2012-06-05 23:10:30 UTC
systemd-37-25.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.