28 lines
932 B
Plaintext
28 lines
932 B
Plaintext
|
CRITICAL: Service app.service state=failed substate=failed restarts=12
|
||
|
|
|
||
|
|
Service state:
|
||
|
|
app.service - Example application
|
||
|
|
Loaded: loaded (/etc/systemd/system/app.service; enabled)
|
||
|
|
Active: failed (Result: exit-code)
|
||
|
|
|
||
|
|
Systemd properties:
|
||
|
|
Id=app.service
|
||
|
|
ActiveState=failed
|
||
|
|
SubState=failed
|
||
|
|
Result=exit-code
|
||
|
|
NRestarts=12
|
||
|
|
|
||
|
|
Recent start/stop/failure log lines since 1 hour ago:
|
||
|
|
May 11 09:05:01 host systemd[1]: app.service: Main process exited, status=1/FAILURE
|
||
|
|
May 11 09:05:01 host systemd[1]: app.service: Failed with result 'exit-code'.
|
||
|
|
|
||
|
|
Evidence:
|
||
|
|
Thresholds: warning=3 restarts critical=10 restarts since="1 hour ago"
|
||
|
|
|
||
|
|
Recommended next steps:
|
||
|
|
- Inspect the unit file and drop-in overrides
|
||
|
|
- Review application logs around the restart timestamps
|
||
|
|
- Check dependencies such as network, storage, database, or secrets
|
||
|
|
- Verify recent configuration or package changes
|
||
|
|
- Do not restart blindly; attach this output to the incident ticket
|