Zabbix running-slave check fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Monitoring Plugins |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I've just noticed running slave check fails for me(debian wheezy, percona 5.5, zabbix 2.2.3 from repos). zabbix_agentd.log reports:
ERROR 1045 (28000): Access denied for user 'zabbix'
That's inspite there are all checks like ok. Quick digging into revealed that it fails at running slave check:
if [ "$ITEM" = "running-slave" ]; then
# Check for running slave
RES=`mysql -e 'SHOW SLAVE STATUS\G' | egrep '(Slave_
I would proposed to fix like
ITEM=$1
HOST=localhost
+ HOME=/var/
DIR=`dirname $0`
RES=`${HOME} mysql -e 'SHOW SLAVE STATUS\G' | egrep '(Slave_
That works here.
tags: | added: zabbix |
Changed in percona-monitoring-plugins: | |
status: | Incomplete → In Progress |
importance: | Undecided → Medium |
milestone: | none → 1.1.4 |
Changed in percona-monitoring-plugins: | |
status: | In Progress → Fix Committed |
summary: |
- running-slave check fails + Zabbix running-slave check fails |
Changed in percona-monitoring-plugins: | |
status: | Fix Committed → Fix Released |
On Debian/Ubuntu, zabbix home dir is /var/run/zabbix instead of /var/lib/zabbix like it is on Redhat/Centos.
The documentation http:// www.percona. com/doc/ percona- monitoring- plugins/ 1.1/zabbix/ index.html# installation- instructions was corrected at some point of time in the past, to create ~zabbix/.my.cnf instead of previous /var/lib/ zabbix/ .my.cnf.
So if you place your .my.cnf under ~zabbix/ no matter what's the actual dir is, it should work.