You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Invoke-IcingaCheckDiskHealth fails with: Cannot convert value "Fibre Channel" to type "System.Int32". Error: "Input string was not in a correct format."
#342
Closed
K0nne opened this issue
Apr 28, 2023
· 2 comments
· Fixed by #345
I found lots of IfW Eventlog entries, which indicate the presence of an error on all of our hyperv systems.
Framework and plugins are version 1.10.1.
This is the eventlog entry:
Failed to execute API call
An API call could not be processed due to an internal exception.
Icinga for Windows exception report:
Exception Message:
Cannot convert value "Fibre Channel" to type "System.Int32". Error: "Input string was not in a correct format."
Command Origin:
Internal
Script Line Number:
6389
Exact Position:
At C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-plugins\compiled\icinga-powershell-plugins.ifw_compilation.psm1:6389 char:9
+ $DiskInfo.Add(
+ ~~~~~~~~~~~~~~
StackTrace:
at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception)
at lambda_method(Closure , Object[] , StrongBox`1[] , InterpretedFrame )
Call Stack:
Command Arguments
------- ---------
Get-IcingaExceptionString {ExceptionObject=Cannot convert value "Fibre ...
Write-IcingaEventMessage {Namespace=RESTApi, EventId=2051, ExceptionOb...
New-IcingaForWindowsRESTThread {RequireAuth=, ThreadId=2}
Object details:
No additional object details provided.
This is the section in question:
The text was updated successfully, but these errors were encountered:
K0nne
changed the title
Invoke-IcingaCheckDiskHealthfails with: Cannot convert value "Fibre Channel" to type "System.Int32". Error: "Input string was not in a correct format."
Invoke-IcingaCheckDiskHealth fails with: Cannot convert value "Fibre Channel" to type "System.Int32". Error: "Input string was not in a correct format."
Apr 28, 2023
Hello,
I found lots of IfW Eventlog entries, which indicate the presence of an error on all of our hyperv systems.
Framework and plugins are version 1.10.1.
This is the eventlog entry:
This is the section in question:
The text was updated successfully, but these errors were encountered: