| Summary: | AssertionError in systemd-analyze when invoked while boot is still in progress | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Middendorf <lukas+fedora> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 16 | CC: | chepioq, dr.diesel, fkooman, harald, johannbg, johannbg, lpoetter, metherid, mike, mku, mschmidt, nikbeier, notting, plautrba, pratyush.a.sahay, twoerner |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-05-29 10:34:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
*** Bug 714001 has been marked as a duplicate of this bug. *** 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. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Package: systemd-36-3.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- run "systemd-analyze" after booting Package: systemd-37-3.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- just running systemd-analyze without parameters Is this still a problem or can this bug be closed? I still had systemd-analyze crash on me the other day for the same reason. 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) 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. Upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=6070fe66ac2f317e7e85e5685f0916d1e2b73a28 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) I typed systemd-analyse and hit enter Package: systemd-37-19.fc16 OS Release: Fedora release 16 (Verne) Running systemd-analyze time after install and restart Package: systemd-analyze-44-8.fc17 OS Release: Fedora release 17 (Beefy Miracle) systemd-44-9.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/systemd-44-9.fc17 systemd-37-20.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/systemd-37-20.fc16 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). 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) 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. 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. |
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: