Difference between revisions of "Rocky 9.x Debugging systemd issues"

From Notes_Wiki
(Created page with "Home > Rocky Linux or CentOS > Rocky Linux 9.x > System Administration > Rocky 9.x systemd or systemctl > Rocky 9.x Debugging systemd issues At times we may need to debug systemd if we dont know what is going on or especially if some command is running via systemd but we dont know which unit/service is responsible for running this command. In such cases enable debug option in systemd using: # Edit '<tt>/...")
 
m
 
Line 11: Line 11:
#:</pre>
#:</pre>
# Then logs should come to /var/log/messages for additional debugging.
# Then logs should come to /var/log/messages for additional debugging.
Refer:
* https://serverfault.com/questions/803844/how-to-debug-systemd-unit-execstart




[[Main Page|Home]] > [[Rocky Linux or CentOS]] > [[Rocky Linux 9.x]] > [[Rocky 9.x System Administration|System Administration]] > [[Rocky 9.x systemd or systemctl]] > [[Rocky 9.x Debugging systemd issues]]
[[Main Page|Home]] > [[Rocky Linux or CentOS]] > [[Rocky Linux 9.x]] > [[Rocky 9.x System Administration|System Administration]] > [[Rocky 9.x systemd or systemctl]] > [[Rocky 9.x Debugging systemd issues]]

Latest revision as of 05:03, 10 April 2024

Home > Rocky Linux or CentOS > Rocky Linux 9.x > System Administration > Rocky 9.x systemd or systemctl > Rocky 9.x Debugging systemd issues

At times we may need to debug systemd if we dont know what is going on or especially if some command is running via systemd but we dont know which unit/service is responsible for running this command. In such cases enable debug option in systemd using:

  1. Edit '/etc/systemd/system.conf' and set:
    LogLevel=debug
  2. Reload systemd for changes to take effect:
    systemctl deamon-reload
  3. Then logs should come to /var/log/messages for additional debugging.

Refer:


Home > Rocky Linux or CentOS > Rocky Linux 9.x > System Administration > Rocky 9.x systemd or systemctl > Rocky 9.x Debugging systemd issues