Open ankar84 opened 2 years ago
I have the exact same behavior. Jitsi is running in docker containers. The Jitsi Stats worked fine for more than 12 month. Yesterday I make an update of the docker containers to the latest image. Jitsi works fine, but jitsi stats stoped working after the update.
When i call the URL i get an 404 Error:
curl -v http://127.0.0.1:8080/colibri/stats
* Expire in 0 ms for 6 (transfer 0x55caa6efafb0)
* Trying 127.0.0.1...
* TCP_NODELAY set
* Expire in 200 ms for 4 (transfer 0x55caa6efafb0)
* Connected to 127.0.0.1 (127.0.0.1) port 8080 (#0)
> GET /colibri/stats HTTP/1.1
> Host: 127.0.0.1:8080
> User-Agent: curl/7.64.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Cache-Control: must-revalidate,no-cache,no-store
< Content-Type: text/html;charset=iso-8859-1
< Content-Length: 510
< Server: Jetty(9.4.44.v20210927)
<
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 404 Not Found</title>
</head>
<body><h2>HTTP ERROR 404 Not Found</h2>
<table>
<tr><th>URI:</th><td>/colibri/stats</td></tr>
<tr><th>STATUS:</th><td>404</td></tr>
<tr><th>MESSAGE:</th><td>Not Found</td></tr>
<tr><th>SERVLET:</th><td>org.glassfish.jersey.servlet.ServletContainer-78dc4696</td></tr>
</table>
<hr/><a href="https://eclipse.org/jetty">Powered by Jetty:// 9.4.44.v20210927</a><hr/>
</body>
</html>
* Connection #0 to host 127.0.0.1 left intact
I have the same issue, my docker image is build from jvb :stable-6726 and this update breaks those stats, I've been using those stats for metric collection for a long time also and broke overnight while updating to latest.
also does anyone know what is the actual behaviour of this setting? thank you!
rest {
shutdown {
enabled = false
}
}
jitsi-videobridge2/stable,now 2.1-595-g3637fda4-1
videobridge {
ice {
udp {
port = 10000
}
tcp {
enabled = false
port = 4443
}
}
apis {
xmpp-client {
configs {
shard1 {
HOSTNAME = "jitsihostname.here"
DOMAIN = "auth.meet.jitsi"
USERNAME = "jvb"
PASSWORD = "securepassword"
MUC_JIDS = "jvbbrewery@internal-muc.meet.jitsi"
MUC_NICKNAME = "muc_nickname"
DISABLE_CERTIFICATE_VERIFICATION = true
}
}
}
rest {
enabled = true
}
}
rest {
shutdown {
enabled = false
}
}
stats {
enabled = true
}
websockets {
enabled = true
domain = "jitsidomaine.here:443"
tls = true
server-id = "ip.ip.ip.ip"
}
http-servers {
private {
host = 0.0.0.0
}
public {
host = 0.0.0.0
port = 9090
}
}
octo {
enabled = true
bind-address = "0.0.0.0"
public-address = "ip.ip.ip.ip"
bind-port = "4096"
region = "xyz"
}
}
ice4j {
harvest {
mapping {
stun {
addresses = [ "meet-jit-si-turnrelay.jitsi.net:443" ]
}
}
}
}
fixed by setting up
COLIBRI_REST_ENABLED=true SHUTDOWN_REST_ENABLED=true
I found the problem in my configuration. In my docker-compose.yml in the jvb videobridge section, the environment settings
Solved here.. thx @f-asa
@ghborger solved it thanks, many docs are outdated on that
fixed by setting up
COLIBRI_REST_ENABLED=true SHUTDOWN_REST_ENABLED=true
Hi, thanks for the solution, for a non-docker installation do you know where should I put these configurations in ? here /etc/jitsi/videobridge/config
?
Description
We on Ubuntu 18.04. We were on 2.0.6293 (2021-09-10) and updated to 2.0.6433 (2021-10-07). Jitsi-videobridge was 2.1-551-g2ad6eb0b-1 and now 2.1-570-gb802be83-1
We have
JAVA_SYS_PROPS="-Dconfig.file=/etc/jitsi/videobridge/jvb.conf
in our /etc/jitsi/videobridge/config file.We had
JVB_OPTS="--apis=rest,"
in our /etc/jitsi/videobridge/config file. Also (and most important) we have this in /etc/jitsi/videobridge/jvb.conf fileSo, according to https://github.com/jitsi/jitsi-videobridge/blob/master/doc/statistics.md and mostly https://github.com/jitsi/jitsi-videobridge/blob/master/doc/rest.md we should be enabled Colibri REST API that way (jvb.conf file)
But after update we get
JVB_OPTS="--apis=,"
in our /etc/jitsi/videobridge/config file! And all conference statistic gone. I mentioned it here https://github.com/jitsi/jitsi-meet/issues/10415So, now I have 2 questions:
rest
in--apis
?Current behavior
Statistics gone during update to recent jitsi-videobridge2 packet.
rest
is alwaysenable = true
in jvb.conf file but I get this results: withJVB_OPTS="--apis=rest,"
in our /etc/jitsi/videobridge/config file I getcurl -s --noproxy "*" http://127.0.0.1:8080/colibri/stats
with
JVB_OPTS="--apis=,"
in our /etc/jitsi/videobridge/config file I getcurl -s --noproxy "*" http://127.0.0.1:8080/colibri/stats
Here is open ports with both
JVB_OPTS="--apis=,"
andJVB_OPTS="--apis=rest,"
in our /etc/jitsi/videobridge/confignetstat -tulnp
I see this https://github.com/jitsi/jitsi-videobridge/pull/1738 and this https://github.com/jitsi/jitsi-videobridge/pull/1736 that means devs plans to get rid of
JVB_OPTS
Expected Behavior
REST API should be enabled after updated if it was enabled before update.
Possible Solution
I don't know.
Steps to reproduce
Environment details
Ubuntu 18.04 Jitsi Meet 2.0.6433 (2021-10-07) jitsi-videobridge2 2.1-570-gb802be83-1