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

3ware: VERIFYING is a normal operation #37

Closed
wants to merge 1 commit into from
Closed

3ware: VERIFYING is a normal operation #37

wants to merge 1 commit into from

Conversation

waja
Copy link

@waja waja commented Oct 23, 2013

The code of check_raid contains an obvious bug in trying
to do a string-compare on a regexp. In

    /usr/lib/nagios/plugins/check_raid
    check_tw_cli(), line 738:

    } elsif ($s eq 'INITIALIZING|VERIFYING') {

The effect is that both status (INITIALIZING and VERIFYING)
will not be recognized and be reported as UNKNOWN. Also
the VERIFYING state will happen as part of a normal operation.
That is especially true if the auto-verification feature
is enabled. To avoid noise this state should be classified
as OK.

Patch was submitted by Harald Wilhelmi harald.wilhelmi@tngtech.com
in Debian Bug #689297 (http://bugs.debian.org/689297)

The code of check_raid contains an obvious bug in trying
to do a string-compare on a regexp. In

        /usr/lib/nagios/plugins/check_raid
        check_tw_cli(), line 738:

        } elsif ($s eq 'INITIALIZING|VERIFYING') {

The effect is that both status (INITIALIZING and VERIFYING)
will not be recognized and be reported as UNKNOWN. Also
the VERIFYING state will happen as part of a normal operation.
That is especially true if the auto-verification feature
is enabled. To avoid noise this state should be classified
as OK.

Patch was submitted by Harald Wilhelmi <harald.wilhelmi@tngtech.com>
in Debian Bug #689297 (http://bugs.debian.org/689297)
@glensc
Copy link
Owner

glensc commented Nov 7, 2013

can you provide data for test input?

please see CONTRIBUTING.md how to provide data for test inputs

@glensc
Copy link
Owner

glensc commented Nov 7, 2013

btw, this is already fixed in cd25534 released as 3.0.1

@waja
Copy link
Author

waja commented Nov 9, 2013

This results in a WARNING, which seems not the same like an OK. As Harald argued with auto-verification this results into periodic noise, but this is not an abnormal condition. Same goes even for the resync of the md software raid.

@glensc
Copy link
Owner

glensc commented Nov 10, 2013

I'm going to close this PR, regex bug is fixed.

making rechecks as WARNING vs OK, is constant request, and they are controversial. so need to make it configurable via command line option to satisfy both parties (ones wanting it to became WARNING and others to stay at OK)

for example:

@glensc glensc closed this Nov 10, 2013
@glensc
Copy link
Owner

glensc commented Nov 10, 2013

ab3471f

@waja
Copy link
Author

waja commented Nov 10, 2013

Enhancing ab3471f for the 'verify' state (I spotted at least 3 occurences in the code) would be great.

@glensc
Copy link
Owner

glensc commented Nov 10, 2013

You mean use the same commandline parameter for verify states?

@waja
Copy link
Author

waja commented Nov 10, 2013

at least an option to configure that too, maybe also use this option ... resync and verify are both administrativ jobs where normaly no issue with the array itself are on going.

@waja
Copy link
Author

waja commented Nov 11, 2013

totally great!

@waja waja deleted the 689297 branch November 11, 2013 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants