Also here I tend to remove all lines with INFO messages to narrow it even further down. Now examine the logfiles and focus on the timing around the moment where the error was enforced. Step 3: Restart the services in order: prosody, jitsi-videobridge2 and jicofo and rather soon proceed with the steps to force the error, Step 2: Stop all 3 services and Remove ALL files from the log-directories (like above),
#Jitsi community how to
Do this several times to make sure you you know how to force the error! Step 1: If an error occurs, try to find the steps to reproduce the error. If you cannot find a cause for your problem, then a second phase should be considered to investigate more… Investigation second part: check output when initialising/utilising a video conference Now aall lines with INFO messages can be removed to narrow the search even further down. Now, the logfiles are not filling up anymore and they are not very large, which makes a first analysis more comfortable. 1 minute and then Stop all 3 services again(!). Step 3: Restart the services in order: prosody, jitsi-videobridge2 and jicofo Step 2: Remove ALL files from the log-directories, Step 1: Stop all 3 services prosody, jitsi-videobridge2 and jicofo (or single service on jibri), To investigate logfiles can be daunting, I suggest following approache(s): Investigation first part: check logfiles when services are started but idle 69 on port 26333Īpr 15 13:18:37 jibri launch.sh: Only local connections are allowed.Īpr 15 13:18:37 jibri launch.sh: Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code. └─749 java .file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/jibri/jibri.jar -config /etc/jitsi/jibri/config.jsonĪpr 15 13:16:18 jibri systemd: Started Jibri Process.Īpr 15 13:16:20 jibri launch.sh: SLF4J: Failed to load class "".Īpr 15 13:16:20 jibri launch.sh: SLF4J: Defaulting to no-operation (NOP) logger implementationĪpr 15 13:16:20 jibri launch.sh: SLF4J: See for further details.Īpr 15 13:18:37 jibri launch.sh: Starting ChromeDriver. Loaded: loaded (/etc/systemd/system/rvice disabled vendor preset: enabled)Īctive: active (running) since Wed 13:16:18 CEST 1 day 11h ago └─3200 java -Xmx3072m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp .SC_HO
Process: 3192 ExecStart=/etc/init.d/jicofo start (code=exited, status=0/SUCCESS) Loaded: loaded (/etc/init.d/jicofo generated)Īctive: active (running) since Wed 15:08:05 CEST 1 day 9h ago └─1105 java -Xmx3072m -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -Dnet.jav Process: 1106 ExecStartPost=/bin/bash -c echo $MAINPID > /var/run/jitsi-videobridge/jitsi-videobridge.pid (code=exitedĬGroup: /system.slice/rvice Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Wed 13:11:15 CEST 1 day 11h ago Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Wed 15:19:58 CEST 1 day 9h ago When the server is running, we can check their status and the results look something like: After server reboot, these services should start in order like: /etc/init.d/prosody start This server depends mainly on 3 services: prosody, videobridge2 (sometimes called jvb) and jicofo. It is important to understand the services that are involved: It is more helpful to find more specific information from the logfiles that are generated. If things go awry, then the search is on! It is one thing to try the black box and if it doesn’t work (or part of it doesn’t) start searching the community forum or your favorite search engine. So now we have a server for Jitsi Meet and possibly also anotherone with Jibri and we expect to start videoconferences, recordings and youtube-streams… OR AT LEAST WE THINK WE HAVE!
0 kommentar(er)
