Skip to content
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

The check output is somewhat confusing #704

Open
granatelbart opened this issue Mar 26, 2024 · 4 comments
Open

The check output is somewhat confusing #704

granatelbart opened this issue Mar 26, 2024 · 4 comments
Assignees
Labels
Question Further information is requested

Comments

@granatelbart
Copy link

Hello all,

i update my icinga and icingaweb to the newest version.

Framework 1.11.1
Plugin 1.11.1
Hyper-V 1.3.0
cluster-1.3.0

2024-03-26 23_55_12-Zustand __ Icinga Web – Mozilla Firefox

I have various problems.

  1. if i run Invoke-IcingaCheckUNCPath powershell crashed
  2. just on one Hyper-v I have problems with HyperVOverCommitment. The check output is somewhat confusing.
    2024-03-27 00_00_22-HyperVOverCommitment auf DATHSDHV04 DHV CLUSTER __ Icinga Web – Mozilla Firefox

I allready reinstalled the icinga and removed it from icinga-director but it didn't make a difference.

@granatelbart
Copy link
Author

Before I forget, I've transitioned to IcingaDB.

@oxzi
Copy link
Member

oxzi commented Mar 27, 2024

Thanks for reporting your issue.

First, is this related to Icinga DB? Did the check previously worked with IDO and how does the check's output look in Icinga Web 2 under the monitoring module?

Based on the provided screenshots, I would guess there's something wrong with your check configuration. This issue looks somewhat similar to #684.

@granatelbart
Copy link
Author

IcingaDB is actually running, but IDO is experiencing the same issue.

I don't think the check-config is the problem.
I have 6 Hyper-V servers running, and one of them is experiencing the issue.

Today, I encountered the same problem with disk health checks on 4 machines. After restarting the Icinga framework, everything worked fine again.

@yhabteab yhabteab transferred this issue from Icinga/icingadb Mar 27, 2024
@LordHepipud
Copy link
Collaborator

Thank you for the issue. This should be resolved with v1.12.0, as we made an update to the internal checker core which now properly interprets the difference between 0 and null while working with units.

The update of the Framework would be enough for the fix to apply, in case the cause is like I mentioned,

@LordHepipud LordHepipud self-assigned this Mar 29, 2024
@LordHepipud LordHepipud added the Question Further information is requested label Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants