Own server health check: /about/health gives 404 not found

Since one of the servers hanged a couple of times while serving video I’ve tried to make a health check in order to redirect traffic through the spare one. But when accessing to the page:
https://my_jitsi_server.com/about/health I found the 404 not found and the message:
“you can create new conversation here”
Any idea what is going on? That page /about/health still exists?
In particular in the jitsi site:
https://meet.jit.si/about/health
Gives a blank page.
Is there any other way for sanity check of the server?

Alejandro

Can you share your config?

Checking the health of the components should be made on localhost, that is not publicly available by default.
Like curl -v http://localhost:8080/about/health or curl -v http://localhost:8888/about/health if enabled …

Thanks @damencho .
So I’ve tried:
curl -v http://localhost:8080/about/health

  • Trying 127.0.0.1…
  • connect to 127.0.0.1 port 8080 failed: Connection refused
  • Trying 127.0.0.1…
  • connect to 127.0.0.1 port 8080 failed: Connection refused
  • Trying 127.0.0.1…
  • connect to 127.0.0.1 port 8080 failed: Connection refused
  • Failed to connect to localhost port 8080: Connection refused
  • Closing connection 0
    curl: (7) Failed to connect to localhost port 8080: Connection refused

and:
curl http://localhost:8888/about/health

Error 404 Not Found

HTTP ERROR 404

Problem accessing /about/health. Reason:

 Not Found

Powered by Jetty:// 9.4.15.v20190215
Is there something to be enabled/installed to get this healthcheck working?

Sure @bbaldino , which file? I am new to jitsi.

It would be both /etc/jitsi/videobridge/sip-communicator.properties and /etc/jitsi/videobridge/jvb.conf. Warning that there are likely values in there you’ll want to censor (e.g. passwords and maybe domains).

@bbaldino

my sip-communicator.properties:

org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true
org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.jitsi.net:443
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc
org.jitsi.videobridge.xmpp.user.shard.HOSTNAME=localhost
org.jitsi.videobridge.xmpp.user.shard.DOMAIN=auth.www.myserver.com
#org.jitsi.videobridge.xmpp.user.shard.DOMAIN=www.myserver.com
org.jitsi.videobridge.xmpp.user.shard.USERNAME=jvb
org.jitsi.videobridge.xmpp.user.shard.PASSWORD=dR5H8r3u
org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.auth.www.myserver.com
#org.jitsi.videobridge.xmpp.user.shard.MUC_JIDS=JvbBrewery@internal.www.myserver.com
org.jitsi.videobridge.xmpp.user.shard.MUC_NICKNAME=5c7e5a46-803b-4b43-a354-e3263f99fe45

And jvb.conf does not exist.

Ok, can you attach your jvb.log as well? From /var/log/jitsi/

@bbaldino, it is pretty long, but I noticed that it repeats the same info that goes like this (tell me if it is enough or you need more):

2020-09-24 23:02:12.195 INFO: [18] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.005S. Sticky failure: false
2020-09-24 23:02:22.190 INFO: [18] Videobridge.createConference#320: create_conf, id=61078cfb7f6aaed8 gid=null logging=false
2020-09-24 23:02:22.194 INFO: [18] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.004S. Sticky failure: false
2020-09-24 23:02:32.191 INFO: [18] Videobridge.createConference#320: create_conf, id=893104ec437197a4 gid=null logging=false
2020-09-24 23:02:32.195 INFO: [18] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.004S. Sticky failure: false
2020-09-24 23:02:42.191 INFO: [18] Videobridge.createConference#320: create_conf, id=43ff3871e74dcfc2 gid=null logging=false
2020-09-24 23:02:42.196 INFO: [18] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.005S. Sticky failure: false
2020-09-24 23:02:51.620 INFO: [16] VideobridgeExpireThread.expire#144: Running expire()
2020-09-24 23:02:52.191 INFO: [18] Videobridge.createConference#320: create_conf, id=8e6e0586dbcb1f21 gid=null logging=false
2020-09-24 23:02:52.197 INFO: [18] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.006S. Sticky failure: false

Actually I need the logs from when the bridge first starts up–it should have a print there about starting the http servers. Can you restart the bridge (service jitsi-videobridge2 restart) and then attach jvb.log?

here it is, from the moment it restarted:

2020-09-24 23:07:52.196 INFO: [18] Videobridge.createConference#320: create_conf, id=828ab21a2fcf7613 gid=null logging=false

2020-09-24 23:07:52.204 INFO: [18] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.008S. Sticky failure: false

2020-09-24 23:07:57.261 INFO: [1] NewConfig$1.invoke#88: Loaded NewConfig with origin: merge of system properties,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-155-gb6af7e9.jar!/reference.conf: 1

2020-09-24 23:07:57.275 INFO: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties

2020-09-24 23:07:57.284 INFO: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties

2020-09-24 23:07:57.287 INFO: [1] JitsiConfig$Companion.reload#40: Reloading.

2020-09-24 23:07:57.335 INFO: [1] NewConfig$1.invoke#88: Loaded NewConfig with origin: merge of system properties,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-155-gb6af7e9.jar!/reference.conf: 1

2020-09-24 23:07:57.335 INFO: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties

2020-09-24 23:07:57.336 INFO: [1] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties

2020-09-24 23:07:57.422 INFO: [11] ConfigurationActivator.start#45: Registered the LegacyConfigurationServiceShim in OSGi.

2020-09-24 23:07:57.427 INFO: [11] AbstractVersionActivator.start#91: VersionService registered: JVB 2.1.202-g5f9377b9

2020-09-24 23:07:57.459 INFO: [11] AbstractJettyBundleActivator.start#613: Not starting the Jetty service for org.jitsi.videobridge.rest.RESTBundleActivator(port=8080)

2020-09-24 23:07:57.527 INFO: [11] AbstractJettyBundleActivator.start#613: Not starting the Jetty service for org.jitsi.videobridge.websocket.WebSocketBundleActivator(port=-1)

2020-09-24 23:07:57.605 INFO: [11] UlimitCheck.printUlimits#115: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).

2020-09-24 23:07:57.609 INFO: [11] VideobridgeExpireThread.start#92: Starting with 60 second interval.

2020-09-24 23:07:57.619 WARNING: [11] Videobridge.start#906: No authorized source regexp configured. Will accept requests from any source.

2020-09-24 23:07:58.034 INFO: [11] JitsiConfig$Companion.reload#40: Reloading.

2020-09-24 23:07:58.052 INFO: [11] NewConfig$1.invoke#88: Loaded NewConfig with origin: merge of system properties,system properties,reference.conf @ jar:file:/usr/share/jitsi-videobridge/jitsi-videobridge.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi-videobridge/lib/jitsi-media-transform-1.0-155-gb6af7e9.jar!/reference.conf: 1

2020-09-24 23:07:58.053 INFO: [11] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties

2020-09-24 23:07:58.053 INFO: [11] LegacyConfigFileLoader$Companion.load#40: Attempting to load legacy config file at path /etc/jitsi, videobridge, sip-communicator.properties

2020-09-24 23:07:58.088 INFO: [11] AbstractHealthCheckService.start#96: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.

2020-09-24 23:07:58.150 INFO: [11] OctoRelayService.start#45: Octo relay is disabled

2020-09-24 23:07:58.371 INFO: [22] org.ice4j.ice.harvest.StunMappingCandidateHarvester.discover: Discovered public address 184.73.199.169:36423/udp from STUN server 129.213.15.174:443/udp using local address 172.31.33.181:0/udp

2020-09-24 23:07:58.371 INFO: [18] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Using org.ice4j.ice.harvest.StunMappingCandidateHarvester, face=/172.31.33.181, mask=/184.73.199.169

2020-09-24 23:07:58.372 INFO: [18] org.ice4j.ice.harvest.MappingCandidateHarvesters.initialize: Initialized mapping harvesters (delay=295ms). stunDiscoveryFailed=false

2020-09-24 23:07:58.907 INFO: [20] [hostname=localhost id=shard] MucClient$1.connected#266: Connected.

2020-09-24 23:07:58.907 INFO: [20] [hostname=localhost id=shard] MucClient.lambda$getConnectAndLoginCallable$7#648: Logging in.

2020-09-24 23:07:59.058 INFO: [20] [hostname=localhost id=shard] MucClient$MucWrapper.join#751: Joined MUC: jvbbrewery@internal.auth.www.my_server.com

What version of the bridge are you running?

ii jitsi-meet 2.0.4627-1 all WebRTC JavaScript video conferences
ii jitsi-meet-prosody 1.0.4127-1 all Prosody configuration for Jitsi Meet
ii jitsi-meet-web 1.0.4127-1 all WebRTC JavaScript video conferences
ii jitsi-meet-web-config 1.0.4127-1 all Configuration for web serving of Jitsi Meet
ii jitsi-videobridge2 2.1-202-g5f9377b9-1 all WebRTC compatible Selective Forwarding Unit (SFU)

Oh, that’s from back in May and we’ve had some things change around this code since then. Would you be up for doing an upgrade?

Sure @bbaldino!
Can you give me some tips on how to do it? This is ubuntu 18.04.
I will look the forum for upgrade instructions.