(reference the upstream wiki rather than maintaining a stale copy of it)

(40 intermediate revisions by 6 users not shown)

Line 5:

Line 5:

If you are experiencing a problem with system boot up due to [[Systemd]], please see the [[Bugs/Common|common bugs]] document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.

If you are experiencing a problem with system boot up due to [[Systemd]], please see the [[Bugs/Common|common bugs]] document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.

−

Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain.

# Add systemd.log_level=debug to the kernel command line to log systemd with debug output enabled.

+

−

# Add systemd.log_target=kmsg to the kernel command line to let systemd buffer to be written to the kernel log buffer.

+

−

# Run /bin/systemd --test --system from command line to test run init as systemd.

+

−

= Information to include in your report =

+

* Run <code>systemctl list-jobs</code>

−

{{Anchor|AllInfo}}

+

To identify slow boot and look for the jobs that are "running" those jobs are the ones where boot waits for completion on and the ones that listed as "waiting" will be executed only after those which are "running" are completed.

−

== All bug reports ==

+

* Run <code>systemctl list-units -t service --all</code>

−

In all cases, the following should be mentioned and attached to your bug report:

+

To list all available services and their current status

−

* The exact kernel command-line used if not default. Typically from the bootloader configuration file (e.g. {{filename|/etc/grub.conf}}) or from {{filename|/proc/cmdline}}

To identify slow boot and look for the jobs that are "running" those jobs are the ones where boot waits for completion on and the ones that listed as "waiting" will be executed only after those which are "running" are completed.

+

−

* Run {{command|systemctl status ssh.service}}

−

To examine the current runtime status of a service. ( In the above example the ssh service )

+

* Run <code>systemctl show -p "Wants" multi-user.target</code>

−

* Run {{command|systemctl show -p "Wants" multi-user.target}}

+

To see which services a target pulls in. ( In the above example the multi-user.target )

−

To figure out which services a target pulls in. ( In the above example the multi-user.target )

−

* Run {{command|systemd --test --system '--unit='multi-user.target}}

+

* Run <code>systemd --test --system --unit=multi-user.target</code>

To examine what gets started when when booted into a specific target. ( In the above example the multi-user.target )

To examine what gets started when when booted into a specific target. ( In the above example the multi-user.target )

−

== Additional systemd boot parameters ==

+

= Systemd boot parameters =

The following boot parameters are also available to further assist with debugging boot issues.

The following boot parameters are also available to further assist with debugging boot issues.

−

; systemd.unit= : Overrides the unit to activate on boot. This may be used to temporarily boot into a different boot unit, for example rescue.target or emergency.service. ( Defaults to default.target. )

+

; systemd.unit= : Overrides the unit to activate on boot. This may be used to temporarily boot into a different boot unit, for example rescue.target or emergency.target. ( Defaults to default.target. )

Latest revision as of 12:45, 15 June 2012

Foreword

If you are experiencing a problem with system boot up due to Systemd, please see the common bugs document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware.

To identify slow boot and look for the jobs that are "running" those jobs are the ones where boot waits for completion on and the ones that listed as "waiting" will be executed only after those which are "running" are completed.

Run systemctl list-units -t service --all

To list all available services and their current status

Run systemctl list-units -t service

To show all active services

Run systemctl status sshd.service

To examine the current runtime status of a service. (In the above example the ssh service)

Run systemctl list-units -t target --all

To show all available targets.

Run systemctl list-units -t target

To show all active targets.

Run systemctl show -p "Wants" multi-user.target

To see which services a target pulls in. ( In the above example the multi-user.target )

Run systemd --test --system --unit=multi-user.target

To examine what gets started when when booted into a specific target. ( In the above example the multi-user.target )

The following boot parameters are also available to further assist with debugging boot issues.

systemd.unit=

Overrides the unit to activate on boot. This may be used to temporarily boot into a different boot unit, for example rescue.target or emergency.target. ( Defaults to default.target. )

systemd.dump_core=

Takes a boolean argument. If true systemd dumps core when it crashes. Otherwise no core dump is created. ( Defaults to true )

systemd.crash_shell=

Takes a boolean argument. If true systemd spawns a shell when it crashes. Otherwise no core dump is created. Defaults to false, for security reasons, as the shell is not protected by any password authentication.

systemd.crash_chvt=

Takes an integer argument. If positive systemd activates the specified virtual terminal when it crashes. ( Defaults to -1 )

Takes a boolean argument. If true shows terse service status updates on the console during bootup. ( Defaults to true )

systemd.sysv_console=

Takes a boolean argument. If true output of SysV init scripts will be directed to the console. ( Defaults to true, unless quiet is passed as kernel command line option in which case it defaults to false. )

systemd.log_target=

Set log target. Argument must be one of console, syslog, kmsg, syslog-or-kmsg, null.