Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
systemd
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Debian systemd Team
systemd
Commits
a635f431
Commit
a635f431
authored
10 years ago
by
Martin Pitt
Browse files
Options
Downloads
Patches
Plain Diff
debian/README.Debian: Document how to debug boot or shutdown problems with the debug shell
Closes: #766039
parent
ce68230f
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
debian/README.Debian
+28
-0
28 additions, 0 deletions
debian/README.Debian
debian/changelog
+2
-0
2 additions, 0 deletions
debian/changelog
with
30 additions
and
0 deletions
debian/README.Debian
+
28
−
0
View file @
a635f431
...
...
@@ -20,3 +20,31 @@ install -d -g systemd-journal /var/log/journal
setfacl -R -nm g:adm:rx,d:g:adm:rx /var/log/journal
-- Tollef Fog Heen <tfheen@debian.org>, Wed, 12 Oct 2011 08:43:50 +0200
Debugging boot/shutdown problems
================================
The "debug-shell" service starts a root shell on VT 9 which is available very
early during boot and very late during shutdown. You can temporarily enable
this when booting the system does not get sufficiently far to get a desktop or
even the text console logins (getty), or when shutdown hangs eternally.
For boot problems the recommended way is to append "systemd.debug-shell" to the
kernel command line in the bootloader.
For shutdown problems, run "systemctl start debug-shell" as root, then shut
down.
WARNING: Please avoid "systemctl enable debug-shell" as this will start the
debug shell permanently which is a SECURITY HOLE as it allows unauthenticated
and unrestricted root access to your computer if you forget to disable it!
Please only enable it if you cannot pass "systemd.debug-shell" to the boot
loader for some reason, and then immediately run "systemctl disable debug-shell"
again.
Once the boot/shutdown problem happened, switch to VT9 (Ctrl+Alt+F9). There you
can use the usual systemctl or journalctl commands, or any other Linux shell
command to list or kill processes. For example, run "systemctl", find units
which are not in the expected state (e. g. "failed" for boot or still "active"
during shutdown), and then get more detailled information with
"systemctl status -l something.service" to get a service's status and recent
logging.
This diff is collapsed.
Click to expand it.
debian/changelog
+
2
−
0
View file @
a635f431
...
...
@@ -15,6 +15,8 @@ systemd (215-6) UNRELEASED; urgency=medium
* Replace our Debian hwdb.bin location patch with what got committed
upstream. Run hwdb update with the new --usr option to keep current
behaviour.
* debian/README.Debian: Document how to debug boot or shutdown problems with
the debug shell. (Closes: #766039)
-- Martin Pitt <mpitt@debian.org> Sun, 12 Oct 2014 17:29:00 +0200
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment