Teampeak3 Nagios Plugin

[Elbandi]

hi,

thux.de wrote the nagios checker plugin for teamspeak 2. I rewrite the checker for teamspeak 3 based on that code.

Elbandi

[The_Third]

First of all thx for this adapatation of the TS2 check plugin.

I may have some question about the use of this plugin. I checked a lot on the web but there is no topic about this specific plugin.

I am on CentOS and I have nagios 3.2.1 installed.

-The check_teamspeak3 file is in my check library with all the other check_XXX (/etc/local/nagios/libexec)

-I've added the check definition in my command.cfg file.

 command_line    $USER1$/check_teamspeak3 -H $HOSTADDRESS$ -t 10011 -s $ARG1$  -w $ARG2$ -c $ARG1$

-I've defined the service in my localhost.cfg file (yeah my ts server is running on the nagios host)

define service{
        use                               local-service        
        host_name                          localhost
        normal_check_interval             1
        service_description              ts3
        check_command                   check_teamspeak3!7777!50!70
        notifications_enabled           0
        }

And I get this message no matter what I change in both files :
CRITICAL: current users:0 on server:10011:queryduration:0.00blabla

Do I have to add the command definition in the nrpe.cfg file too? What did I miss in the config?

PS : I changed the lib target in the script from use lib "/usr/lib/nagios/plugins/" ; to use lib "/usr/local/nagios/etc/libexec"

This line is supposed to specify where is the check library righ?

If you need more information don't hesitate to ask.

Regards

[doodie]

I do have the same problem, too: No matter how I call the plugin, the state is CRITICAL always

I use the current beta version of Teamspeak 3 Server on Debian Lenny and tryed this:

server9:/usr/lib/nagios/plugins# ./check_teamspeak3 -H 'localhost'
CRITICAL: current users: 0 on server: 10011 ; queryduration: 0.000954 | users=0;maxusers=0;bytessend=0;bytesreceived=0;uptime=0

Any suggestions? Did this work for anyone?

I monitor the TCP ports 10011 and 30033 with check_tcp currently, but a slot and a vserver monitoring would be great in addition.

Does anyone have an idea how to use check_udp to monitor the vservers UDP ports? I don't know the string to send and expect.

[Elbandi]

telnet to 10011, and use the hostinfo command. paste the result pls.

[doodie]

server9:~# telnet localhost 10011
Trying ::1...
Trying 127.0.1.1...
Connected to localhost.
Escape character is '^]'.
TS3
hostinfo
error id=2568 msg=insufficient\sclient\spermissions failed_permid=4355
quit
error id=0 msg=ok
Connection closed by foreign host.

This is the result of an out of the box TS3 server setup.

[The_Third]

I got the exact same thing as doodie.

My guess is that the query can't be done correctly because of some rights issue.

[doodie]

Sure, but I really don't want to view my host info to everybody. The plugin should support the login command with user and password.

I've added some more parameters to support a user login now

But I think I'll make a clean rewrite of the whole plugin by time...

[Elbandi]

Thx doodie. I update the first comment with your version, and change one thing: if maxuser is 0, the result is a error.

[Air SeaTac]

Sorry to drag up an old thread but I'm obviously not understanding this Nagios plugin, what follows is the output from manual use, my commands.cfg entry & my windows.cfg entry (asterisks used deliberately) -

./check_teamspeak3 -H ******** -u **** -p *******
OK: current users: 1 on server: 10011 ; queryduration: 0.229957 | users=1;maxusers=512;bytessend=111968857;bytesrece ived=47580477;uptime=155420

# 'check_teamspeak3' command definition
define command{
command_name check_teamspeak3
command_line $USER1$/check_teamspeak3 -H $ARG1$ -u $ARG2$ -p $ARG3$
}

define service{
use generic-service
host_name *****
service_description TeamSpeak 3 Test
servicegroups front_end_services
check_command check_teamspeak3!****!****!****
notifications_enabled 1
}

With this setup I'm getting 'Critical' on the Nagios web page, how is that since manual use produces valid output?

[moeilijk]

The first command definition looks a little different. The first argument should be $HOSTADDRESS$ according to the nagios examples.

My working setup has

define command{
command_name check_teamspeak3
command_line $USER1$/check_teamspeak3 -H $HOSTADDRESS$ -u $ARG1$ -p $ARG2$
}

With a matching service block

define service{
use generic-service
host_name hostname
service_description TeamSpeak 3
check_command check_teamspeak3!username!password
}

With hostname, username and password obviously matching your config