Systemd: how to debug on boot fail
Contents
 |
|
| Software version | 208-6 |
|---|---|
| Operating System | Debian 8 |
| Website | |
| Last Update | 27/07/2014 |
| Others | |
1 Introduction
systemd[1] is a system and service manager for Linux, compatible with SysV and LSB init scripts. Systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux control groups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic.
When I decided to migrate to Systemd on Debian, it unfortunately worked at the first time. That's why I need to deep dive into Systemd issues and understand why it wasn't working.
2 Usage
First of all, you have to search at failed services:
 systemctl
|
> systemctl --state=failed |
To get then more informations on a service:
| systemctl
|
systemctl status <servicename> |
Try to know more on the specific PID (may not work in some cases:
| journalctl
|
> journalctl -b _PID= |
Generally, it is because of modules that doesn't load properly or shouldn't load. Make your changes, try to start the problematic services:
| systemctl
|
> systemctl start <servicename> |
Now things should be ok
