Installation läuft durch, danach hapert es

arneschreiber · 2023-05-26T09:08:17+00:00

Moin zusammen, nachdem ich jetzt einige Male die Installation durchlaufen lassen habe und das Problem nicht gelöst bekomme, hoffe ich, dass einer von euch m...

Alf06

arneschreiber I'm reviewing my changes I had to make for a "running meet":
( i not installed jibri in my environment)

videobridge in /etc/jitsi/videobridge/application.conf
verify correct port is set:
http-servers {
#The HTTP server which hosts services intended for 'public' use
#(e.g. websockets for the bridge channel connection)
public {
#See JettyBundleActivatorConfig in Jicoco for values
,#original = port = 8081
port = 9090
-review in this file, correct domain, hostname, password are set too.
if you set in /srv/jitsi-meet/config.js a websocket usage ( // Websocket URL
// websocket: 'wss://jitsi-meet.example.com/xmpp-websocket', )
there was a need on my setup to modify nginx in /usr/share/grommunio-common/nginx/locations.d/grommunio-meet.conf: ( will get reverted on next package update - so create a safe copy of your changes )
from:
location /meet/xmpp-websocket {
=> to: location = /meet/xmpp-websocket {

to increase the logging of the videobridge create a new file /etc/jitsi/videobridge/logging.properties:
handlers= java.util.logging.ConsoleHandler
java.util.logging.ConsoleHandler.level = ALL
java.util.logging.ConsoleHandler.formatter = net.java.sip.communicator.util.ScLogFormatter
net.java.sip.communicator.util.ScLogFormatter.programname=JVB
.level=INFO
org.jitsi.videobridge.xmpp.ComponentImpl.level=FINE
org.jitsi.impl.neomedia.MediaStreamImpl.level=WARNING

the log output may show you more information about problems.

finally it will depend on how you like to use meet.
in my environment i added a coturn to stabilize meetings with >2 members and had to implement more settings as shown above.

arneschreiber

Alf06
Hi Alf,
i updated the configuration the way you described, but there was no change. I don't have websockets enabled. The whole installation is out of the box, expecting the given changes above.
I think, only the startup-description from the .service-file is missing.

from log:
May 28 18:10:43 mail jvb.sh[2627]: INFO: Performed a successful health check in PT0.000012S. Sticky failure: false
May 28 18:10:43 mail jvb.sh[2627]: May 28, 2023 6:10:43 PM org.jitsi.utils.logging2.LoggerImpl log
May 28 18:10:43 mail jvb.sh[2627]: WARNING: Cannot set presence extensions: no previous presence available.

Alf06

arneschreiber
Hi Arne,
ok, standard installation by install/setup.
review the file = /etc/prosody/conf.d/$Domain.cfg.lua, which is created by setup.
out of this file you need to collect the name of your components, and the used component_secret.
then check file = /etc/jitsi/jicofo/jitsi-jicofo.conf that got created with package install, if settings for JICOFO_HOSTNAME, JICOFO_AUTH_DOMAIN and JICOFO_AUTH_PASSWORD are set as in cfg.lua file. correct if needed.
do the same with /etc/jitsi/videobridge/jitsi-videobridge.conf.

edit /srv/jitsi-meet/config.js, which is not modified by setup, and adjust settings for domain, muc and bosh (and websockets if you want to enable it).
with this file you can manage the behavior of your meet-installation.

after your modifications restart prosody, nginx, jitsi-jicofo, jitsi-videobridge

Testing via browser:
https://your.domain.com/meet/http-bind - should return something like <body xmlns:stream= ...
with websockets in config.js enabled only: https://your.domain.com/meet/xmpp-websocket - should return: It works! Now point your WebSocket client to this URL to connect to Prosody."

review your log for other issues during restart.

arneschreiber

Alf06
Hi Alf,
thanks for the tipps. I reconfigured the files according to your guide, but it still remains not working.
I found the following messages in the log:
May 30 07:49:17 mail jvb.sh[103668]: WARNING: Failed to join the MUCs.
May 30 07:49:17 mail jvb.sh[103668]: org.jivesoftware.smackx.muc.MultiUserChatException$NotAMucServiceException: Can not join 'jvbbrewery@mail.DOMAIN.TLD', because 'mail.DOMAIN.TLD' does not provide a MUC (XEP-45) service.
May 30 07:49:17 mail jvb.sh[103668]: at org.jivesoftware.smackx.muc.MultiUserChat.enter(MultiUserChat.java:355)
May 30 07:49:17 mail jvb.sh[103668]: at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:543)
May 30 07:49:17 mail jvb.sh[103668]: at org.jivesoftware.smackx.muc.MultiUserChat.createOrJoin(MultiUserChat.java:518)
May 30 07:49:17 mail jvb.sh[103668]: at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.join(MucClient.java:735)
May 30 07:49:17 mail jvb.sh[103668]: at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.access$200(MucClient.java:662)
May 30 07:49:17 mail jvb.sh[103668]: at org.jitsi.xmpp.mucclient.MucClient.joinMucs(MucClient.java:348)
May 30 07:49:17 mail jvb.sh[103668]: at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:645)
May 30 07:49:17 mail jvb.sh[103668]: at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
May 30 07:49:17 mail jvb.sh[103668]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
May 30 07:49:17 mail jvb.sh[103668]: at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
May 30 07:49:17 mail jvb.sh[103668]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
May 30 07:49:17 mail jvb.sh[103668]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
May 30 07:49:17 mail jvb.sh[103668]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
May 30 07:49:17 mail jvb.sh[103668]: at java.base/java.lang.Thread.run(Thread.java:829)
....
May 30 07:49:18 mail jvb.sh[103668]: INFO: Started @2278ms
May 30 07:49:22 mail jvb.sh[103668]: May 30, 2023 7:49:22 AM org.jitsi.utils.logging2.LoggerImpl log
May 30 07:49:22 mail jvb.sh[103668]: WARNING: Cannot set presence extensions: no previous presence available.
May 30 07:49:27 mail jvb.sh[103668]: May 30, 2023 7:49:27 AM org.jitsi.utils.logging2.LoggerImpl log
May 30 07:49:27 mail jvb.sh[103668]: INFO: Performed a successful health check in PT0.000899S. Sticky failure: false
May 30 07:49:27 mail jvb.sh[103668]: May 30, 2023 7:49:27 AM org.jitsi.utils.logging2.LoggerImpl log
May 30 07:49:27 mail jvb.sh[103668]: WARNING: Cannot set presence extensions: no previous presence available.
May 30 07:49:32 mail jvb.sh[103668]: May 30, 2023 7:49:32 AM org.jitsi.utils.logging2.LoggerImpl log
May 30 07:49:32 mail jvb.sh[103668]: WARNING: Cannot set presence extensions: no previous presence available.
May 30 07:49:37 mail jvb.sh[103668]: May 30, 2023 7:49:37 AM org.jitsi.utils.logging2.LoggerImpl log
May 30 07:49:37 mail jvb.sh[103668]: INFO: Performed a successful health check in PT0.00002S. Sticky failure: false
May 30 07:49:37 mail jvb.sh[103668]: May 30, 2023 7:49:37 AM org.jitsi.utils.logging2.LoggerImpl log
May 30 07:49:37 mail jvb.sh[103668]: WARNING: Cannot set presence extensions: no previous presence available.

when i try to access the http-bind-service as mentioned above, the following message is given:
<body xmlns:stream="http://etherx.jabber.org/streams" xmlns="http://jabber.org/protocol/httpbind" type="terminate" condition="item-not-found"/>

Alf06

arneschreiber Hi Arne,
check /etc/jitsi/videobridge/application.conf
section =
configs {
xmpp-server-1 {
hostname="localhost"
-> domain = "auth.your.domain.TLD"
username = "focus"
-> password = "YOURSECRET3" #pw from prosody
-> muc_jids = "JvbBrewery@internal.auth.your.domain.TLD",
and websocket part:
websockets {
enabled=true
server-id="default-id"
#Optional, even when 'enabled' is set to true
#tls=true
-> tls=true
-> domain="your.domain.TLD"

seems like there is the issue.

arneschreiber

Alf06
Hi Alf,
i modified the configuration, but a conference still cannot be established. Microphone and camera can be activated, but after clicking the "Konferenz beitreten"-button the error still comes up.

log after restarting prosody:
May 31 16:30:12 mail jvb.sh[2719]: INFO: Performed a successful health check in PT0.000002S. Sticky failure: false
May 31 16:30:14 mail systemd[1]: Stopping Jabber/XMPP Server...
May 31 16:30:15 mail prosodyctl[62878]: WARNING: Use of prosodyctl start/stop/restart/reload is not recommended
May 31 16:30:15 mail prosodyctl[62878]: if Prosody is managed by an init system - use that directly instead.
May 31 16:30:15 mail prosodyctl[62878]: e.g. systemctl stop prosody
May 31 16:30:15 mail jvb.sh[2719]: May 31, 2023 4:30:15 PM org.jivesoftware.smack.AbstractXMPPConnection callConnectionClosedOnErrorListener
May 31 16:30:15 mail jvb.sh[2719]: WARNING: Connection XMPPTCPConnection[focus@auth.mail.DOMAIN.TLD/N-k7IvVs] (0) closed with error
May 31 16:30:15 mail jvb.sh[2719]: org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
May 31 16:30:15 mail jvb.sh[2719]: <stream:error><system-shutdown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>Received SIGTERM</text></stream:error>
May 31 16:30:15 mail jvb.sh[2719]: at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:981)
May 31 16:30:15 mail jvb.sh[2719]: at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:913)
May 31 16:30:15 mail jvb.sh[2719]: at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:936)
May 31 16:30:15 mail jvb.sh[2719]: at java.base/java.lang.Thread.run(Thread.java:829)
May 31 16:30:15 mail jvb.sh[2719]: May 31, 2023 4:30:15 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:15 mail jvb.sh[2719]: WARNING: Closed on error:
May 31 16:30:15 mail jvb.sh[2719]: org.jivesoftware.smack.XMPPException$StreamErrorException: system-shutdown You can read more about the meaning of this stream error at http://xmpp.org/rfcs/rfc6120.html#streams-error-conditions
May 31 16:30:15 mail jvb.sh[2719]: <stream:error><system-shutdown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text>Received SIGTERM</text></stream:error>
May 31 16:30:15 mail jvb.sh[2719]: at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(XMPPTCPConnection.java:981)
May 31 16:30:15 mail jvb.sh[2719]: at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$700(XMPPTCPConnection.java:913)
May 31 16:30:15 mail jvb.sh[2719]: at org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(XMPPTCPConnection.java:936)
May 31 16:30:15 mail jvb.sh[2719]: at java.base/java.lang.Thread.run(Thread.java:829)
May 31 16:30:15 mail prosodyctl[62878]: Stopped
May 31 16:30:15 mail systemd[1]: prosody.service: Deactivated successfully.
May 31 16:30:15 mail systemd[1]: Stopped Jabber/XMPP Server.
May 31 16:30:15 mail systemd[1]: Starting Jabber/XMPP Server...
May 31 16:30:15 mail prosodyctl[62880]: WARNING: Use of prosodyctl start/stop/restart/reload is not recommended
May 31 16:30:15 mail prosodyctl[62880]: if Prosody is managed by an init system - use that directly instead.
May 31 16:30:15 mail prosodyctl[62880]: e.g. systemctl start prosody
May 31 16:30:15 mail prosodyctl[62880]: Started
May 31 16:30:15 mail systemd[1]: Started Jabber/XMPP Server.
May 31 16:30:17 mail jvb.sh[2719]: May 31, 2023 4:30:17 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:17 mail jvb.sh[2719]: WARNING: Cannot set presence extension: not connected.
May 31 16:30:18 mail jvb.sh[2719]: May 31, 2023 4:30:18 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:18 mail jvb.sh[2719]: INFO: Connected.
May 31 16:30:18 mail jvb.sh[2719]: May 31, 2023 4:30:18 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:18 mail jvb.sh[2719]: INFO: Logging in.
May 31 16:30:18 mail jvb.sh[2719]: May 31, 2023 4:30:18 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:18 mail jvb.sh[2719]: INFO: Authenticated, b=false
May 31 16:30:18 mail jvb.sh[2719]: May 31, 2023 4:30:18 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:18 mail jvb.sh[2719]: INFO: Leaving a MUC we already occupy.
May 31 16:30:18 mail jvb.sh[2719]: May 31, 2023 4:30:18 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:18 mail jvb.sh[2719]: WARNING: Error while trying to leave a MUC:
May 31 16:30:18 mail jvb.sh[2719]: org.jivesoftware.smack.XMPPException$XMPPErrorException: XMPP error reply received from jvbbrewery@internal.auth.mail.DOMAIN.TLD/6b21a8f0-e5c3-41d9-9ec8-fb7d1c67f2e9: XMPPError: item-not-found - cancel
May 31 16:30:18 mail jvb.sh[2719]: at org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:171)
May 31 16:30:18 mail jvb.sh[2719]: at org.jivesoftware.smack.XMPPException$XMPPErrorException.ifHasErrorThenThrow(XMPPException.java:165)
May 31 16:30:18 mail jvb.sh[2719]: at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:284)
May 31 16:30:18 mail jvb.sh[2719]: at org.jivesoftware.smack.StanzaCollector.nextResultOrThrow(StanzaCollector.java:228)
May 31 16:30:18 mail jvb.sh[2719]: at org.jivesoftware.smackx.muc.MultiUserChat.leave(MultiUserChat.java:795)
May 31 16:30:18 mail jvb.sh[2719]: at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.leave(MucClient.java:699)
May 31 16:30:18 mail jvb.sh[2719]: at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.join(MucClient.java:729)
May 31 16:30:18 mail jvb.sh[2719]: at org.jitsi.xmpp.mucclient.MucClient$MucWrapper.access$200(MucClient.java:662)
May 31 16:30:18 mail jvb.sh[2719]: at org.jitsi.xmpp.mucclient.MucClient.joinMucs(MucClient.java:348)
May 31 16:30:18 mail jvb.sh[2719]: at org.jitsi.xmpp.mucclient.MucClient.lambda$getConnectAndLoginCallable$7(MucClient.java:645)
May 31 16:30:18 mail jvb.sh[2719]: at org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:167)
May 31 16:30:18 mail jvb.sh[2719]: at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
May 31 16:30:18 mail jvb.sh[2719]: at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
May 31 16:30:18 mail jvb.sh[2719]: at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
May 31 16:30:18 mail jvb.sh[2719]: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
May 31 16:30:18 mail jvb.sh[2719]: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
May 31 16:30:18 mail jvb.sh[2719]: at java.base/java.lang.Thread.run(Thread.java:829)
May 31 16:30:18 mail jvb.sh[2719]: May 31, 2023 4:30:18 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:18 mail jvb.sh[2719]: INFO: Joined MUC: jvbbrewery@internal.auth.mail.DOMAIN.TLD
May 31 16:30:22 mail jvb.sh[2719]: May 31, 2023 4:30:22 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:30:22 mail jvb.sh[2719]: INFO: Performed a successful health check in PT0.000002S. Sticky failure: false

log after restarting jicofo
May 31 16:31:46 mail systemd[1]: Stopping JItsi COnference FOcus...
May 31 16:31:46 mail systemd[1]: jitsi-jicofo.service: Main process exited, code=exited, status=143/n/a
May 31 16:31:46 mail systemd[1]: jitsi-jicofo.service: Failed with result 'exit-code'.
May 31 16:31:46 mail systemd[1]: Stopped JItsi COnference FOcus.
May 31 16:31:46 mail systemd[1]: Started JItsi COnference FOcus.

log after restarting videobridge
May 31 16:32:53 mail systemd[1]: Stopping Jitsi Videobridge...
May 31 16:32:53 mail systemd[1]: jitsi-videobridge.service: Deactivated successfully.
May 31 16:32:53 mail systemd[1]: Stopped Jitsi Videobridge.
May 31 16:32:53 mail systemd[1]: Started Jitsi Videobridge.
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: WARNING: A deprecated command line argument (--apis) is present. Please use the config file to control the REST API instead (see rest.md). Support for --apis will be removed in a future version.
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: INFO: Initialized newConfig: merge of /etc/jitsi/videobridge/application.conf: 1,application.conf @ jar:file:/usr/share/jitsi/videobridge/jitsi-videobridge.jar!/application.conf: 1,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/ice4j-3.0-46-g64a7ca8.jar!/reference.conf: 1,reference.conf @ jar:file:/usr/share/jitsi/videobridge/lib/jitsi-media-transform-1.0-271-g9a84b31.jar!/reference.conf: 1
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: INFO: loading config file at path /etc/jitsi/videobridge/sip-communicator.properties
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: INFO: Error loading config file: java.io.FileNotFoundException: /etc/jitsi/videobridge/sip-communicator.properties (No such file or directory)
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: INFO: Initialized legacyConfig: sip communicator props (no description provided)
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: INFO: Reloading the Typesafe config source (previously reloaded 0 times).
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:54 mail jvb.sh[63192]: INFO: Starting jitsi-videobridge version 2.1.SNAPSHOT
May 31 16:32:54 mail jvb.sh[63192]: May 31, 2023 4:32:54 PM org.ice4j.ice.harvest.MappingCandidateHarvesters initialize
May 31 16:32:54 mail jvb.sh[63192]: INFO: Using AwsCandidateHarvester.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.ice4j.ice.harvest.MappingCandidateHarvesters maybeAdd
May 31 16:32:55 mail jvb.sh[63192]: INFO: Discarding a mapping harvester: org.ice4j.ice.harvest.AwsCandidateHarvester@5fc44c29
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.ice4j.ice.harvest.MappingCandidateHarvesters initialize
May 31 16:32:55 mail jvb.sh[63192]: INFO: Initialized mapping harvesters (delay=520ms). stunDiscoveryFailed=false
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Initializing a new MucClient for [ org.jitsi.xmpp.mucclient.MucClientConfiguration id=xmpp-server-1 domain=auth.mailDOMAIN.TLD hostname=localhost port=null username=focus mucs=[JvbBrewery@internal.auth.mail.DOMAIN.TLD] mucNickname=6b21a8f0-e5c3-41d9-9ec8-fb7d1c67f2e9 disableCertificateVerification=true]
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: LastNReducer with reductionScale: 0.75 recoverScale: 1.25 impactTime: PT1M minLastN: 1 maxEnforcedLastN: 40
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: TaskPools detected 6 processors, creating the CPU pool with that many threads
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: WARNING: Disabling certificate verification!
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Running with open files limit 65000 (hard 65000), thread limit 65000 (hard 65000).
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Starting with 60 second interval.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Started with interval=10000, timeout=PT30S, maxDuration=PT3S, stickyFailures=false.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Not starting CallstatsService, disabled in configuration.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Starting public http server
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Dispatching a thread to connect and login.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Base URL: wss://mail.DOMAIN.TLD/colibri-ws/default-id
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.eclipse.jetty.util.log.Log initialized
May 31 16:32:55 mail jvb.sh[63192]: INFO: Logging initialized @1489ms to org.eclipse.jetty.util.log.JavaUtilLog
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Registering servlet at /colibri-ws/*, baseUrl = wss://mail.DOMAIN.TLD/colibri-ws/default-id
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.eclipse.jetty.server.Server doStart
May 31 16:32:55 mail jvb.sh[63192]: INFO: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.19+0-suse-150000.3.96.1-x8664
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Connected.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Logging in.
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.eclipse.jetty.server.handler.ContextHandler doStart
May 31 16:32:55 mail jvb.sh[63192]: INFO: Started o.e.j.s.ServletContextHandler@4bee18dc{/,null,AVAILABLE}
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.eclipse.jetty.server.AbstractConnector doStart
May 31 16:32:55 mail jvb.sh[63192]: INFO: Started ServerConnector@4303b7f0{HTTP/1.1, (http/1.1)}{0.0.0.0:9090}
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.eclipse.jetty.server.Server doStart
May 31 16:32:55 mail jvb.sh[63192]: INFO: Started @1648ms
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Starting private http server
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Authenticated, b=false
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.eclipse.jetty.server.Server doStart
May 31 16:32:55 mail jvb.sh[63192]: INFO: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.19+0-suse-150000.3.96.1-x8664
May 31 16:32:55 mail jvb.sh[63192]: May 31, 2023 4:32:55 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:32:55 mail jvb.sh[63192]: INFO: Joined MUC: jvbbrewery@internal.auth.mail.DOMAIN.TLD
May 31 16:32:56 mail jvb.sh[63192]: May 31, 2023 4:32:56 PM org.glassfish.jersey.server.wadl.WadlFeature configure
May 31 16:32:56 mail jvb.sh[63192]: WARNING: JAXBContext implementation could not be found. WADL feature is disabled.
May 31 16:32:56 mail jvb.sh[63192]: May 31, 2023 4:32:56 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
May 31 16:32:56 mail jvb.sh[63192]: WARNING: A provider org.jitsi.rest.Health registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Health will be ignored.
May 31 16:32:56 mail jvb.sh[63192]: May 31, 2023 4:32:56 PM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
May 31 16:32:56 mail jvb.sh[63192]: WARNING: A provider org.jitsi.rest.Version registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.rest.Version will be ignored.
May 31 16:32:56 mail jvb.sh[63192]: May 31, 2023 4:32:56 PM org.eclipse.jetty.server.handler.ContextHandler doStart
May 31 16:32:56 mail jvb.sh[63192]: INFO: Started o.e.j.s.ServletContextHandler@7b2ccba5{/,null,AVAILABLE}
May 31 16:32:56 mail jvb.sh[63192]: May 31, 2023 4:32:56 PM org.eclipse.jetty.server.AbstractConnector doStart
May 31 16:32:56 mail jvb.sh[63192]: INFO: Started ServerConnector@5b12012e{HTTP/1.1, (http/1.1)}{127.0.0.1:8082}
May 31 16:32:56 mail jvb.sh[63192]: May 31, 2023 4:32:56 PM org.eclipse.jetty.server.Server doStart
May 31 16:32:56 mail jvb.sh[63192]: INFO: Started @2507ms
May 31 16:33:05 mail jvb.sh[63192]: May 31, 2023 4:33:05 PM org.jitsi.utils.logging2.LoggerImpl log
May 31 16:33:05 mail jvb.sh[63192]: INFO: Performed a successful health check in PT0.001435S. Sticky failure: false

Alf06

arneschreiber
nice, MUC seems to be fine, same for colibri socket 9090,
but where is the 'bug' now? should be the last little adjustment.
plz check logs in /var/log/grommunio, seems some file is not referenced yet.
check /var/log/prosody/prosody.err for issues.
what is the error list once you join meeting with enabled browsers developer tool?

arneschreiber

Alf06
Hi Alf,
there are no new entries in the (error)logfiles in /var/log/grommunio. I found the the following output in the prosody-log:
May 31 23:55:49 mod_bosh info New BOSH session, assigned it sid '70d4b51c-0c47-413d-9b3b-09ce82a8f95e'
May 31 23:55:49 bosh70d4b51c-0c47-413d-9b3b-09ce82a8f95e info Authenticated as kahz-8hduigvqp5e@mail.DOMAIN.TLD
May 31 23:55:50 c2s563987b93960 info Client connected
May 31 23:55:50 c2s563987b93960 info Client disconnected: connection closed
May 31 23:55:55 c2s563987c24540 info Client connected
May 31 23:55:55 c2s563987c24540 info Client disconnected: connection closed
May 31 23:56:00 c2s563987cc0d50 info Client connected
May 31 23:56:00 c2s563987cc0d50 info Client disconnected: connection closed
May 31 23:56:02 bosh70d4b51c-0c47-413d-9b3b-09ce82a8f95e info BOSH client disconnected: session close

the debug-console printed out the following error:
(anonymous) @ ProudDuosPlanIncreasingly:25
Logger.js:154 2023-05-31T22:41:58.931Z [modules/xmpp/strophe.ping.js] <as.startInterval>: XMPP pings will be sent every 10000 ms
Logger.js:154 2023-05-31T22:41:58.931Z [modules/xmpp/xmpp.js] <Ur.connectionHandler>: (TIME) Strophe connected: 1408.800000011921
Logger.js:154 2023-05-31T22:41:58.931Z [modules/xmpp/xmpp.js] <Ur.connectionHandler>: My Jabber ID: i1viscy42zjp_rnz@mail.DOMAIN.TLD/aJcWxOiI
Logger.js:154 2023-05-31T22:42:00.066Z [features/base/redux] <Object.persistState>: redux state persisted. 4fd3cfa9bd5918c8263798ad03450126 -> 646de2c4c25852feac083b5ee9c104de
Logger.js:154 2023-05-31T22:42:00.411Z [modules/RTC/RTCUtils.js] onUserMediaSuccess
Logger.js:154 2023-05-31T22:42:00.455Z [features/local-recording] <Object.setMicDevice>: Switch microphone to 93f486496628de63b7561f7ccea42da21f81db037307e552e1491bc199d09b23
Logger.js:154 2023-05-31T22:42:03.815Z [modules/xmpp/xmpp.js] <Ur.createRoom>: JID i1viscy42zjp_rnz@mail.DOMAIN.TLD/aJcWxOiI using MUC nickname 6df3eb65
Logger.js:154 2023-05-31T22:42:03.815Z [modules/xmpp/ChatRoom.js] <new Us>: Joined MUC as proudduosplanincreasingly@conference.mail.DOMAIN.TLD/6df3eb65
Logger.js:154 2023-05-31T22:42:03.816Z [modules/e2eping/e2eping.js] <new Qa>: Initializing e2e ping; pingInterval=10000, analyticsInterval=60000.
Logger.js:154 2023-05-31T22:42:03.816Z [modules/connectivity/ParticipantConnectionStatus.js] <new oi>: RtcMuteTimeout set to: 10000
Logger.js:154 2023-05-31T22:42:03.818Z [modules/statistics/AvgRTPStatsReporter.js] <new hc>: Avg RTP stats will be calculated every 15 samples
Logger.js:154 2023-05-31T22:42:03.818Z [JitsiConference.js] <new jc>: backToP2PDelay: 5
Logger.js:154 2023-05-31T22:42:03.819Z [JitsiConference.js] <new jc>: End-to-End Encryption is supported
Logger.js:154 2023-05-31T22:42:03.822Z [JitsiConference.js] <jc._doReplaceTrack>: doReplaceTrack - no JVB JingleSession
Logger.js:154 2023-05-31T22:42:03.823Z [JitsiConference.js] <jc.doReplaceTrack>: doReplaceTrack - no P2P JingleSession
Logger.js:154 2023-05-31T22:42:03.823Z [JitsiConference.js] <jc.doReplaceTrack>: doReplaceTrack - no JVB JingleSession
Logger.js:154 2023-05-31T22:42:03.824Z [JitsiConference.js] <jc.doReplaceTrack>: doReplaceTrack - no P2P JingleSession
Logger.js:154 2023-05-31T22:42:03.837Z [modules/xmpp/moderator.js] <Ls.setFocusUserJid>: Focus jid set to: focus@auth.mail.DOMAIN.TLD
Logger.js:154 2023-05-31T22:42:03.838Z [modules/xmpp/moderator.js] <Ls.createConferenceIq>: Session ID: null machine UID: 6626cf721eed399288244fe17c7ea897
Logger.js:154 2023-05-31T22:42:03.844Z [conference.js] Initialized with 2 local tracks
Logger.js:154 2023-05-31T22:42:03.873Z [modules/RTC/RTCUtils.js] <vi.<anonymous>>: Got media constraints: {"video":false,"audio":{"autoGainControl":true,"deviceId":"93f486496628de63b7561f7ccea42da21f81db037307e552e1491bc199d09b23","echoCancellation":true,"noiseSuppression":true}}
Logger.js:154 2023-05-31T22:42:03.877Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Focus error, retry after 1000 Script: null Line: null Column: null StackTrace: Error: Focus error, retry after 1000
at Ls.allocateConferenceFocusError (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:382464)
at https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:381505
at I.Handler.handler (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:180796)
at I.Handler.run (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:176095)
at https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:184533
at Object.forEachChild (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:167763)
at I.Connection.dataRecv (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:184382)
at M.Bosh.onRequestStateChange (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:204366)
r @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.js:532
window.onerror @ middleware.js:110
callErrorHandler @ GlobalOnErrorHandler.js:61
Ls._allocateConferenceFocusError @ moderator.js:382

it seems to belong to the focus-settings.

Alf06

arneschreiber

try this:
1)
/etc/jitsi/jicofo/sip-communicator.properties - new file:
org.jitsi.jicofo.BRIDGE_MUC=JvbBrewery@internal.auth.mail.DOMAIN.TLD
org.jitsi.jicofo.SHORT_ID=55555
#workaround for certificate errors
org.jitsi.jicofo.ALWAYS_TRUST_MODE_ENABLED=true

2)
/etc/jitsi/jicofo/jicofo.conf - new file:
jicofo {
xmpp: {
client: {
client-proxy: focus.mail.DOMAIN.TLD
}
trusted-domains: [ "recorder.mail.DOMAIN.TLD" ]
}
bridge: {
brewery-jid: "JvbBrewery@internal.auth.mail.DOMAIN.TLD"
}
authentication: {
enabled: true
type: XMPP
login-url: mail.DOMAIN.TLD
}
jigasi: {
brewery-jid: "JigasiBrewery@internal.auth.mail.DOMAIN.TLD"
}
}

3)
/etc/jitsi/videobridge/sip-communicator.properties - new file
#Enable broadcasting stats/presence in a MUC
org.jitsi.videobridge.ENABLE_STATISTICS=true
org.jitsi.videobridge.STATISTICS_TRANSPORT=muc,colibri,pubsub

#Connect to the first XMPP server
org.jitsi.videobridge.xmpp.user.xmppserver1.HOSTNAME=localhost
org.jitsi.videobridge.xmpp.user.xmppserver1.DOMAIN=auth.mail.DOMAIN.TLD
org.jitsi.videobridge.xmpp.user.xmppserver1.USERNAME=jvb
org.jitsi.videobridge.xmpp.user.xmppserver1.PASSWORD=YOURSECRET-component_secret value of prosody
org.jitsi.videobridge.xmpp.user.xmppserver1.MUC_JIDS=JvbBrewery@internal.auth.mail.DOMAIN.TLD
org.jitsi.videobridge.xmpp.user.xmppserver1.MUC=JvbBrewery@internal.auth.mail.DOMAIN.TLD
org.jitsi.videobridge.xmpp.user.xmppserver1.MUC_NICKNAME=your-muc-nickname-value-out-of-application.conf
org.jitsi.videobridge.xmpp.user.xmppserver1.DISABLE_CERTIFICATE_VERIFICATION=true

arneschreiber

Alf06
Hi Alf,
i added the conf-files, but the error still remains.

log from developer-console:
render @ react-dom.production.min.js:286
ple.renderEntryPoint @ index.web.js:54
(anonymous) @ test:25
Logger.js:154 2023-06-01T11:06:25.027Z [modules/UI/videolayout/LargeVideoManager.js] hover in local
Logger.js:154 2023-06-01T11:06:25.802Z [modules/xmpp/moderator.js] <Ls.createConferenceIq>: Session ID: null machine UID: 6626cf721eed399288244fe17c7ea897
Logger.js:154 2023-06-01T11:06:25.828Z [JitsiMeetJS.js] <Object.getGlobalOnErrorHandler>: UnhandledError: Focus error, retry after 2000 Script: null Line: null Column: null StackTrace: Error: Focus error, retry after 2000
at Ls.allocateConferenceFocusError (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:382464)
at https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:381505
at I.Handler.handler (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:180796)
at I.Handler.run (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:176095)
at https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:184533
at Object.forEachChild (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:167763)
at I.Connection.dataRecv (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:184382)
at M.Bosh.onRequestStateChange (https://mail.DOMAIN.TLD/meet/libs/lib-jitsi-meet.min.js?v=139:2:204366)
r @ Logger.js:154
getGlobalOnErrorHandler @ JitsiMeetJS.js:532
window.onerror @ middleware.js:110
callErrorHandler @ GlobalOnErrorHandler.js:61
Ls.allocateConferenceFocusError @ moderator.js:382
(anonymous) @ moderator.js:309
(anonymous) @ strophe.umd.js:2716
run @ strophe.umd.js:1875

Alf06

arneschreiber Hi Arne,
check /srv/jitsi-meet/config.js if focus setting is enabled and correct adjusted:
// focus: 'focus.jitsi-meet.example.com',
-> focus: 'focus.mail.DOMAIN.TLD',

and focusUserJid: 'focus@auth.mail.DOMAIN.TLD',

arneschreiber

Alf06
Hi Alf,
both was already set.

Alf06

arneschreiber
It remains a mystery - what setting is still bad.
I would now need to validate and verify all settings and know more about the environment.
meet consists of 5 components with lot of config files.
one bug can affect all.

Alf06

arneschreiber
with last update of meet i received same 'join meeting' issue in some of my meet environments.

the modifications i had to made to get it back running:
file = /usr/share/grommunio-common/nginx/locations.d/grommunio-meet.conf

- location /meet/xmpp-websocket {
modified to : location = /meet/xmpp-websocket {
- location ~ ^/meet/colibri-ws/(.) {
modified to : location ~ ^/colibri-ws/(.) {
as my environment has a loadbalancer in frontend that redirects /colibri-ws only.

and /srv/jitsi-meet/static/close2.html got reverted to a non functional closepage again.

(restart of nginx is required)

« Previous Page