Page 2 of 2
Re: Offloading mysql - performance tuning - size of servers
Posted: Wed Jan 09, 2019 3:06 pm
by junkertf
Hello,
Thank you for the fast answer. I will make that settings.
how about the error i became when i want monitor the worker?
[root@myhuslhqbpxisrvuat libexec]# ./check_gearman2 -H localhost -q myhuslhqbpngmgu -t 60 -s check
check_gearman CRITICAL - Job failed: _client_do(GEARMAN_TIMEOUT) occured during gearman_client_run_tasks() -> libgearman/client.cc:174
[root@myhuslhqbpxisrvuat libexec]# ./check_gearman2 -H localhost -q localhost -t 3 -s check
check_gearman CRITICAL - Job failed: _client_do(GEARMAN_TIMEOUT) occured during gearman_client_run_tasks() -> libgearman/client.cc:174
Thank you, best regards,
Ferenc
Re: Offloading mysql - performance tuning - size of servers
Posted: Wed Jan 09, 2019 4:15 pm
by ssax
Check Job Server Queues: (Checking from the XI server)
Code: Select all
./check_gearman2 -H 127.0.0.1 -q check_results
./check_gearman2 -H 127.0.0.1 -q eventhandler
./check_gearman2 -H 127.0.0.1 -q host
./check_gearman2 -H 127.0.0.1 -q localhost
./check_gearman2 -H 127.0.0.1 -q myhuslhqbpngmgu
./check_gearman2 -H 127.0.0.1 -q service
./check_gearman2 -H 127.0.0.1 -q worker_myhuslhqbpinagt.hu.money.ge.com
./check_gearman2 -H 127.0.0.1 -q worker_myhuslhqbpngmgu.hu.money.ge.com
Code: Select all
./check_gearman2 -H 127.0.0.1 -q worker_myhuslhqbpinagt.hu.money.ge.com -t 30 -s check
./check_gearman2 -H 127.0.0.1 -q worker_myhuslhqbpngmgu.hu.money.ge.com -t 30 -s check
Code: Select all
./check_gearman2 -H XI_IP_ADDRESSS -q check_results
./check_gearman2 -H XI_IP_ADDRESSS -q eventhandler
./check_gearman2 -H XI_IP_ADDRESSS -q host
./check_gearman2 -H XI_IP_ADDRESSS -q localhost
./check_gearman2 -H XI_IP_ADDRESSS -q myhuslhqbpngmgu
./check_gearman2 -H XI_IP_ADDRESSS -q service
./check_gearman2 -H XI_IP_ADDRESSS -q worker_myhuslhqbpinagt.hu.money.ge.com
./check_gearman2 -H XI_IP_ADDRESSS -q worker_myhuslhqbpngmgu.hu.money.ge.com
Code: Select all
./check_gearman2 -H XI_IP_ADDRESSS -q worker_myhuslhqbpinagt.hu.money.ge.com -t 30 -s check
./check_gearman2 -H XI_IP_ADDRESSS -q worker_myhuslhqbpngmgu.hu.money.ge.com -t 30 -s check
Code: Select all
usage:
check_gearman [ -H=<hostname>[:port] ]
[ -t=<timeout> ]
[ -w=<jobs warning level> ] default: 10
[ -c=<jobs critical level> ] default: 100
[ -W=<worker warning level> ] default: 25
[ -C=<worker critical level> ] default: 50
[ -q=<queue> ]
to send a test job:
[ -u=<unique job id> ] default: check
[ -s=<send text> ]
[ -e=<expect text> ]
[ -a send async ] will ignore -e
[ -h print help ]
[ -v verbose output ]
[ -V print version ]
- You may set thresholds to 0 to disable them.
- Thresholds are only for server checks, worker checks are availability only
perfdata format when checking job server:
'queue waiting'=current waiting jobs;warn;crit;0 'queue running'=current runnin g jobs 'queue worker'=current num worker;warn;crit;0
Note: set your pnp RRD_STORAGE_TYPE to MULTIPLE to support changeing numbers of queues.
see http://docs.pnp4nagios.org/de/pnp-0.6/tpl_custom for detailed informat ion
perfdata format when checking mod gearman worker:
worker=10 jobs=1508c
Note: Job thresholds are per queue not totals.
Examples:
Check job server:
%>./check_gearman -H localhost -q host
check_gearman OK - 0 jobs running and 0 jobs waiting. Version: 0.14
Check worker:
%> ./check_gearman -H <job server hostname> -q worker_<worker hostname> -t 10 -s check
check_gearman OK - host has 5 worker and is working on 0 jobs