# Nagios State Unkown

**URL:** <https://forums.percona.com/t/nagios-state-unkown/4076>\
**Category:** Percona Monitoring Plugins\
**Created:** [February 25, 2015, 7:33am UTC](https://forums.percona.com/t/nagios-state-unkown/4076 "2015-02-25T07:33:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mat](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@mat](https://forums.percona.com/u/mat)\
**Post date:** [February 25, 2015, 7:33am UTC](https://forums.percona.com/t/nagios-state-unkown/4076/1 "2015-02-25T07:33:00Z")

</div>

Good day

we have a small problem with the percona monitoring plugins for nagios.

We use for a MySQL Galera Cluster several checks with pmp-check-mysql-status.

Primary Cluster  
pmp-check-mysql-status -x wsrep\_cluster\_status -C ‘==’ -T str -c non-Primary -L local

Node State  
pmp-check-mysql-status -x wsrep\_local\_state\_comment -C ‘!=’ -T str -w Synced -L local

Cluster Size  
pmp-check-mysql-status -x wsrep\_cluster\_size -C “\<=” -w 2 -c 1 -L local

Flow Control  
pmp-check-mysql-status -x wsrep\_flow\_control\_paused -w 0.1 -c 0.9 -L local

The Problem is if the database offline or not reachable or the login is wrong, the check change it state to unkown. But we want for this case an critical if the check cannot be processed.

So i could modify the script itself but it’s a very dirty solution and i didn’t find another solution at the moment.

What would be the best practice way?