You are browsing a read-only backup copy of Wikitech. The primary site can be found at wikitech.wikimedia.org

Monitoring/systemd unit state: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Dzahn
(Created page with "The "systemd unit state" Icinga checks tests if there are any failed systemd units. If this alerts you should ssh to the server in question and run '''systemctl list-...")
 
imported>Phamhi
No edit summary
Line 1: Line 1:
The "systemd unit state" [[Icinga]] checks tests if there are any failed [[systemd]] units.
The "systemd unit state" [[Icinga]] checks tests if there are any failed [[systemd]] units.


If this alerts you should ssh to the server in question and run '''systemctl list-units --state=failed''' to check which unit is the one that has issues.
For this type of alerts, you should ssh to the server in question and run '''systemctl list-units --state=failed''' to check which unit is the one that has issues.


Try manually starting it with '''systemctl start <unit name>'''.
Try manually starting it with '''systemctl start <unit name>'''.

Revision as of 13:30, 3 September 2019

The "systemd unit state" Icinga checks tests if there are any failed systemd units.

For this type of alerts, you should ssh to the server in question and run systemctl list-units --state=failed to check which unit is the one that has issues.

Try manually starting it with systemctl start <unit name>.

You can use systemctl status <unit name>, journalctl -u <unit name> and journalctl -xn to see more details and logs to figure out why it failed.

Sometimes the failure has been fixed already and you just need to clear the list of failed units with systemctl reset-failed.

Also see: