-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Faulty drive/degraded state doesn't trigger anything #94
Comments
Is the array showing up as degraded in |
@hairmare yes it is, this file exists and its content is "1" |
@paraenggu PTAL |
@Hyrla sorry for the late reply, I overlooked this one. A degraded drive should at least fire two triggers:
In your case above:
Cloud you please post the relevant latest values of the affected host? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
I setup this wonderful plugin successfully. However, there is not alerts triggered even if I manually set a disk to faulty state.
My Zabbix Agent is used in passive mode so I just changed "Zabbix Agent (active)" to "Zabbix Agent" in discovery templates settings.
Here's the output of few debug commands :
su -c 'zabbix_agentd -t rabe.raid.md.raid-device.discovery' -s /bin/bash zabbix
rabe.raid.md.raid-device.discovery [t|{"data":[{"{#MD_RAID_RAID_DEV_NAME}":"md0"}]}]
mdadm -D /dev/md0
My host's items discovered screenshot
https://i.ibb.co/FVcQpMM/Capture-d-cran-de-2020-03-29-17-04-49.png
My host's triggers for MD RAID active
https://i.ibb.co/g9qs4rj/Capture-d-cran-de-2020-03-29-17-08-21.png
Am I doing anything wrong ?
Thank you :)
The text was updated successfully, but these errors were encountered: