-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timers check on rhel7 failing on readahead service #20
Comments
There was a feature request that this inactive (dead) timer should be reported. Would you please take a look at this issue: #6 (comment) |
Ok, I read the request, but I dont understand why a dead timer should be taken as an error. If the field for NEXT is set to N/A it is because the timer service is not enabled, or.. as in my case, a pre-requisite is not met, so the service is not suppoed to be running. |
I must admit that I am very unsure how to deal with this issue. Your reasoning sounds perfectly understandable. I believe, however, that there are situations in which someone wants to check, that the NEXT field is never N/A. Maybe we should introduce a new option for example |
I am ok with an option, so that it will not check disabled timers - so that wont break existing configs, but I feel it should be the default to not check disabled timers. |
I have now seen a situation where the service is enabled, but still N/A - which is when the service is enabled but has not yet run successfully once. example for service enabled but failed first run:
|
Thank you for reporting this. Would it be possible to share the output of the command |
I have had problems putting a server in the same state as this again, but I think I have one now. The service is now systemd-readahead-done.timer and it has the following properties: [root@serverb]# systemctl show systemd-readahead-done.timer |
Thank you very much! |
I also found the correct service, just after boot it shows the issue:
and the properties for this service:
|
Using check_systemd 2.3.1.
Fully patched RHEL7.9 server has this issue. It is a virtualised server on a vmware platform.
It keeps failing on a service, which it should not, as it is n/a in the next field, correct?
[root@server1 plugins]# systemctl status systemd-readahead-done.timer
● systemd-readahead-done.timer - Stop Read-Ahead Data Collection 10s After Completed Startup
Loaded: loaded (/usr/lib/systemd/system/systemd-readahead-done.timer; indirect; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-01-03 10:45:35 CET; 22h ago
ConditionVirtualization=no was not met
Docs: man:systemd-readahead-replay.service(8)
[root@server1 plugins]# systemctl list-timers --all
NEXT LEFT LAST PASSED UNIT ACTIVATES
Tue 2022-01-04 10:58:02 CET 1h 48min left Mon 2022-01-03 10:58:02 CET 22h ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
n/a n/a n/a n/a systemd-readahead-done.timer systemd-readahead-done.service
2 timers listed.
[root@server1 plugins]# /usr/lib64/nagios/plugins/check_systemd.py -t -n -vvv
SYSTEMD CRITICAL - systemd-readahead-done.timer
critical: systemd-readahead-done.timer
| count_units=319 data_source=cli units_activating=0 units_active=215 units_failed=0 units_inactive=104
The text was updated successfully, but these errors were encountered: