nbuchwitz / check_jitsi Goto Github PK

# netstat -tapn | grep 8080
tcp6       0      0 127.0.0.1:8080                 :::*                    LISTEN      8262/java

org.jitsi.videobridge.rest.private.jetty.host=::in /etc/jitsi/videobridge/sip-communicator.properties is needed to not just bind to 127.0.0.1.

Now you are able to connect remote:

# netstat -tapn | grep 8080
tcp6       0      0 :::8080                 :::*                    LISTEN      8338/java

Hi and kudos on the plugin!
While running it from the local jitsi server the plugin works as it should, but when calling it from the monitoring server (or any other server as a script) I get the following error:

./check_jitsi.py -H domainname.local -p 5347 -m health
UNKNOWN - Could not connect to JVB API: Failed to resolve hostname or service is not listenings

I have checked the port to be open from any by modifying the prosody.conf.lua file and adding 0.0.0.0 for this port. is there any other port or configuration to be made to allow it to connect?

Also when trying _telnet domainname.local 5347 I get connected.

The existing command definition in icinga/ should also provided as Icinga Director basket file.

Hi
The Plugin output looks like this:

  ./check_jitsi.py -H jitsi1.nts.ch  -m conferences -w 10 -c 30
  OK - 0 conferences |conferences=0;;10;30

Accoring to the icinga performance scheme, it should look like this:

  ./check_jitsi.py -H jitsi1.nts.ch  -m conferences -w 10 -c 30
  OK - 0 conferences |conferences=10;39;0;

See: https://icinga.com/docs/icinga1/latest/en/perfdata.html
'label'=value[UOM];[warn];[crit];[min];[max]