Recording failed to start and Chrome failed to start: exited abnormally


#1

Please Provide a solution for Below issue.

I faced recording failed to start issue so i installed jibri using below llink:

After installing jibri , i started jibri using below cmd but i faced issue jibri failed to start.

sudo systemctl start jibri

after i type status cmd :

sudo service jibri status

output:

jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2018-10-23 12:10:38 IST; 5s ago
Process: 29459 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=7)
Main PID: 29463 (java)
Tasks: 70 (limit: 65000)
CGroup: /system.slice/jibri.service
├─ 5703 /usr/local/bin/chromedriver --port=10511 --log-path=/tmp/chromedriver.log
├─14137 /usr/local/bin/chromedriver --port=28140 --log-path=/tmp/chromedriver.log
├─17453 /usr/local/bin/chromedriver --port=9736 --log-path=/tmp/chromedriver.log
├─26344 /usr/local/bin/chromedriver --port=17352 --log-path=/tmp/chromedriver.log
├─29463 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/jibri/jibri.jar --config
├─29960 /usr/local/bin/chromedriver --port=11497 --log-path=/tmp/chromedriver.log
└─31651 /usr/local/bin/chromedriver --port=23235 --log-path=/tmp/chromedriver.log

Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.034 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustA
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.523 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.connected(
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.591 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.authentica
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.607:WARN:oejsh.ContextHandler:main: o.e.j.s.ServletContextHandler
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.607:WARN:oejsh.ContextHandler:main: Empty contextPath
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.607:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.647 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.c
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.677:INFO:oejsh.ContextHandler:main: Started o.e.j.s.ServletContex
Oct 23 12:10:40 trajectus-01 launch.sh[29463]: 2018-10-23 12:10:40.677:INFO:oejs.ServerConnector:main: Started ServerConnector@6719a

jicofo logs:

jicofo.log (89.2 KB)

jibri logs:

2018-10-22 15:32:58.058 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json
2018-10-22 15:32:58.596 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:
JibriConfig(recordingDirectory=/tmp/recordings, enabledStatsD=true, finalizeRecordingScriptPath=/path/to/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[xxxxxxxxxxxxx], xmppDomain=xxxxxxxxxxxxx, controlLogin=XmppCredentials(domain=auth.xxxxxxxxxxxxx, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.xxxxxxxxxxxxx, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.xxxxxxxxxxxxx, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])
2018-10-22 15:32:59.064 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.internal.InternalHttpApi will be ignored.
2018-10-22 15:32:59.314 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on xxxxxxxxxxxxx with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[xxxxxxxxxxxxx], xmppDomain=xxxxxxxxxxxxx, controlLogin=XmppCredentials(domain=auth.xxxxxxxxxxxxx, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.xxxxxxxxxxxxx, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.xxxxxxxxxxxxx, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2018-10-22 15:32:59.320 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2018-10-22 15:32:59.523 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.connected() [prod environment: auth.xxxxxxxxxxxxx@xxxxxxxxxxxxx] Xmpp connection status: connected
2018-10-22 15:32:59.603 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.authenticated() [prod environment: auth.xxxxxxxxxxxxx@xxxxxxxxxxxxx] Xmpp connection status: authenticated (resume from previous? false)
2018-10-22 15:32:59.662 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.HttpApi will be ignored.
2018-10-22 15:34:09.529 INFO: [26] org.jitsi.jibri.api.xmpp.XmppApi.handleJibriIq() Received JibriIq from environment prod environment
2018-10-22 15:34:09.533 INFO: [26] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Received start request
2018-10-22 15:34:09.540 INFO: [26] org.jitsi.jibri.api.xmpp.XmppApi.handleStartJibriIq() Sending ‘pending’ response to start IQ
2018-10-22 15:34:09.541 INFO: [40] org.jitsi.jibri.api.xmpp.XmppApi.run() Starting service
2018-10-22 15:34:09.560 INFO: [40] org.jitsi.jibri.api.xmpp.XmppApi.handleStartService() Parsed call url info: CallUrlInfo(baseUrl=[https://xxxxxxxxxxxxx] (https://xxxxxxxxxxxxx/), callName=gr3k9b, urlParams=)
2018-10-22 15:34:09.566 INFO: [40] org.jitsi.jibri.JibriManager.startFileRecording() Starting a file recording with params: FileRecordingRequestParams(callParams=CallParams(callUrlInfo=CallUrlInfo(baseUrl=https://xxxxxxxxxxxxx, callName=gr3k9b, urlParams=)), sessionId=nfjahprtndaxonbv, callLoginParams=XmppCredentials(domain=recorder.xxxxxxxxxxxxx, username=recorder, password=jibrirecorderpass)) finalize script path: /path/to/finalize_recording.sh and recordings directory: /tmp/recordings
2018-10-22 15:34:10.238 SEVERE: [40] org.jitsi.jibri.api.xmpp.XmppApi.run() Error in startService task: org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn’t exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
(Driver info: chromedriver=2.43.600233 (523efee95e3d68b8719b3a1c83051aa63aa6b10d),platform=Linux 4.15.0-36-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 145 milliseconds
Build info: version: ‘unknown’, revision: ‘unknown’, time: ‘unknown’
System info: host: ‘trajectus-01’, ip: ‘127.0.1.1’, os.name: ‘Linux’, os.arch: ‘amd64’, os.version: ‘4.15.0-36-generic’, java.version: ‘1.8.0_181’
Driver info: driver.version: ChromeDriver with stack:
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
java.lang.reflect.Constructor.newInstance(Constructor.java:423)
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$new$0(JsonWireProtocolResponse.java:53)
org.openqa.selenium.remote.JsonWireProtocolResponse.lambda$getResponseFunction$2(JsonWireProtocolResponse.java:91)
org.openqa.selenium.remote.ProtocolHandshake.lambda$createSession$0(ProtocolHandshake.java:123)
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126)
java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498)
java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464)
org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:126)
org.openqa.selenium.remote.ProtocolHandshake.createSession(ProtocolHandshake.java:73)
org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:142)
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:601)
org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:219)
org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:142)
org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:181)
org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:168)
org.jitsi.jibri.selenium.JibriSelenium.(JibriSelenium.kt:137)
org.jitsi.jibri.selenium.JibriSelenium.(JibriSelenium.kt:100)
org.jitsi.jibri.service.impl.FileRecordingJibriService.(FileRecordingJibriService.kt:109)
org.jitsi.jibri.JibriManager.startFileRecording(JibriManager.kt:121)
org.jitsi.jibri.api.xmpp.XmppApi.handleStartService(XmppApi.kt:285)
org.jitsi.jibri.api.xmpp.XmppApi.access$handleStartService(XmppApi.kt:68)
org.jitsi.jibri.api.xmpp.XmppApi$handleStartJibriIq$1.run(XmppApi.kt:200)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

2018-10-22 15:34:10.239 INFO: [40] org.jitsi.jibri.api.xmpp.XmppApi.run() Sending start service response iq:

prosody.log:

Oct 22 15:32:17 bosh91d1e9ff-76ef-4dc6-9136-0f5cafd71000 info BOSH client disconnected
Oct 22 15:32:57 c2s5609e8894ed0 info Client disconnected: closed
Oct 22 15:32:59 c2s5609e89aa410 info Client connected
Oct 22 15:32:59 c2s5609e89aa410 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Oct 22 15:32:59 c2s5609e89aa410 info Authenticated as jibri@auth.xxxxxxxxxxxxx
Oct 22 15:33:11 jcp5609e87abe30 info component disconnected: focus.xxxxxxxxxxxxx (closed)
Oct 22 15:33:11 c2s5609e8795d50 info Client disconnected: closed
Oct 22 15:33:11 c2s5609e8c65510 info Client connected
Oct 22 15:33:11 jcp5609e84da9a0 info Incoming Jabber component connection
Oct 22 15:33:11 focus.xxxxxxxxxxxxx:component info External component successfully authenticated
Oct 22 15:33:11 c2s5609e8c65510 info Stream encrypted (TLSv1.2 with ECDHE-RSA-AES256-GCM-SHA384)
Oct 22 15:33:11 c2s5609e8c65510 info Authenticated as focus@auth.xxxxxxxxxxxxx
Oct 22 15:33:56 mod_bosh info New BOSH session, assigned it sid ‘d91b10f5-b114-4dbb-8c38-2165f1404b53’
Oct 22 15:33:56 boshd91b10f5-b114-4dbb-8c38-2165f1404b53 info Authenticated as 8eefc6f0-937e-4968-9832-c7d45d583d48@xxxxxxxxxxxxx


#2

Hi @keerthireddyb,

Can you specify the OS on which you are deploying Jibri? Check for the lightdm service and if it is on, please turn it off. Chrome exited abnormally is usually related to the desktop being used by lightdm and it does not share the resource with Jibri.
Check: service lightdm status
if it is running,
service lightdm stop to turn it off. Reload Jibri service jibri restart & service jibri-xorg restart

After restarting, check the status of jibri and jibri-xorg. They should be running, then go ahead with recording.

Thanks,
Abhijit


#3

Hi @abhijitnathwani,

I am using ubuntu 18.04 OS. lightdm is not there in my system. jibri-xorg.service also not started.

$ service lightdm status

Output: Unit lightdm.service could not be found.

$ service jibri restart

Output:

jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2018-10-25 15:12:58 IST; 5s ago
Process: 7525 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=7)
Main PID: 7529 (java)
Tasks: 136 (limit: 65000)
CGroup: /system.slice/jibri.service
├─ 5703 /usr/local/bin/chromedriver --port=10511 --log-path=/tmp/chromedriver.log
├─ 7529 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/jibri/jibri.jar --confi
├─ 9494 /usr/local/bin/chromedriver --port=14914 --log-path=/tmp/chromedriver.log
├─10683 /usr/local/bin/chromedriver --port=10145 --log-path=/tmp/chromedriver.log
├─14137 /usr/local/bin/chromedriver --port=28140 --log-path=/tmp/chromedriver.log
├─16345 /usr/local/bin/chromedriver --port=27827 --log-path=/tmp/chromedriver.log
├─17149 /usr/local/bin/chromedriver --port=13408 --log-path=/tmp/chromedriver.log
├─17453 /usr/local/bin/chromedriver --port=9736 --log-path=/tmp/chromedriver.log
├─17711 /usr/local/bin/chromedriver --port=6156 --log-path=/tmp/chromedriver.log
├─22041 /usr/local/bin/chromedriver --port=28182 --log-path=/tmp/chromedriver.log
├─22382 /usr/local/bin/chromedriver --port=20808 --log-path=/tmp/chromedriver.log
├─23336 /usr/local/bin/chromedriver --port=24606 --log-path=/tmp/chromedriver.log
├─23353 /usr/local/bin/chromedriver --port=12980 --log-path=/tmp/chromedriver.log
├─25016 /usr/local/bin/chromedriver --port=14410 --log-path=/tmp/chromedriver.log
├─26344 /usr/local/bin/chromedriver --port=17352 --log-path=/tmp/chromedriver.log
├─29677 /usr/local/bin/chromedriver --port=15618 --log-path=/tmp/chromedriver.log
├─29960 /usr/local/bin/chromedriver --port=11497 --log-path=/tmp/chromedriver.log
├─30195 /usr/local/bin/chromedriver --port=12027 --log-path=/tmp/chromedriver.log

$ service jibri-xorg restart

Output:

jibri-xorg.service - Jibri Xorg Process
Loaded: loaded (/etc/systemd/system/jibri-xorg.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-10-25 15:14:30 IST; 4s ago
Process: 8058 ExecStart=/usr/bin/Xorg -nocursor -noreset +extension RANDR +extension RENDER -logfile /tmp/xorg.log -config /etc/j
Main PID: 8058 (code=exited, status=1/FAILURE)

Oct 25 15:14:30 trajectus-01 systemd[1]: jibri-xorg.service: Service hold-off time over, scheduling restart.
Oct 25 15:14:30 trajectus-01 systemd[1]: jibri-xorg.service: Scheduled restart job, restart counter is at 5.
Oct 25 15:14:30 trajectus-01 systemd[1]: Stopped Jibri Xorg Process.
Oct 25 15:14:30 trajectus-01 systemd[1]: jibri-xorg.service: Start request repeated too quickly.
Oct 25 15:14:30 trajectus-01 systemd[1]: jibri-xorg.service: Failed with result ‘exit-code’.
Oct 25 15:14:30 trajectus-01 systemd[1]: Failed to start Jibri Xorg Process.

Please provide a solution…

Thanks,
Keerthi.


#4

Hi,

There is your problem. jibri-xorg is not started hence recording will not work.
Ubuntu 18 does not use lightdm. It uses some other xorg desktop.

Find that by: $ ps aux | grep xorg
and kill the ProcessID which has xorg, with kill -9 <pid-of-xorg-service>

Fire the command again, and you should not see any xorg services.

Start the jibri & jibri-xorg again.

Note: Killing the xorg services will turn of your desktop (the gui) and you’ll be directed to login if you’re using a desktop system.

Regards,
Abhijit


#5

Hi @abhijitnathwani,

I fallow above process but jibri xorg not started again same issue came.

In ubuntu 18.04 have gdm3 xorg desktop. I type below cmd’s and related outputs.

$ ps aux | grep xorg

Output:

traject+ 1616 0.5 0.6 401104 73640 tty2 Rl+ Oct25 5:45 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
traject+ 11641 0.0 0.0 21536 1048 pts/0 S+ 10:59 0:00 grep --color=auto xorg

$ ps aux | grep gdm

Output:

root 948 0.0 0.0 308176 7956 ? Ssl Oct25 0:00 /usr/sbin/gdm3
root 962 0.0 0.0 261552 8488 ? Sl Oct25 0:00 gdm-session-worker [pam/gdm-launch-environment]
gdm 977 0.0 0.0 77000 8072 ? Ss Oct25 0:00 /lib/systemd/systemd --user
gdm 978 0.0 0.0 114432 3088 ? S Oct25 0:00 (sd-pam)
gdm 1012 0.0 0.0 197796 5376 tty1 Ssl+ Oct25 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart
gdm 1014 0.0 0.0 50224 4560 ? Ss Oct25 0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
gdm 1065 0.0 0.1 559056 13968 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-session/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart
gdm 1177 0.0 0.9 3306288 119612 tty1 Sl+ Oct25 0:34 /usr/bin/gnome-shell
gdm 1259 0.0 0.4 540004 52688 tty1 Sl+ Oct25 0:00 /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6
gdm 1273 0.0 0.0 349268 6112 ? Ssl Oct25 0:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
gdm 1278 0.0 0.0 49928 3900 ? S Oct25 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
gdm 1280 0.0 0.0 220760 7044 ? Sl Oct25 0:00 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
gdm 1286 0.0 0.0 1153800 11724 ? Ssl Oct25 0:00 /usr/bin/pulseaudio --daemonize=no
gdm 1319 0.0 0.0 361364 7592 tty1 Sl Oct25 0:00 ibus-daemon --xim --panel disable
gdm 1322 0.0 0.0 280612 5880 tty1 Sl Oct25 0:00 /usr/lib/ibus/ibus-dconf
gdm 1324 0.0 0.2 402460 27948 tty1 Sl Oct25 0:00 /usr/lib/ibus/ibus-x11 --kill-daemon
gdm 1327 0.0 0.0 278556 5832 ? Sl Oct25 0:00 /usr/lib/ibus/ibus-portal
gdm 1343 0.0 0.2 553004 28992 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings
gdm 1346 0.0 0.0 278152 5860 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
gdm 1347 0.0 0.2 402084 27120 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard
gdm 1348 0.0 0.2 726608 30308 tty1 Sl+ Oct25 0:11 /usr/lib/gnome-settings-daemon/gsd-color
gdm 1351 0.0 0.1 393704 13672 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime
gdm 1352 0.0 0.0 283736 5736 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping
gdm 1353 0.0 0.2 556472 27608 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard
gdm 1354 0.0 0.2 1138176 30344 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys
gdm 1358 0.0 0.0 201996 4648 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse
gdm 1359 0.0 0.2 649480 29224 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-power
gdm 1365 0.0 0.0 267004 8588 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications
gdm 1366 0.0 0.0 202016 4556 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill
gdm 1371 0.0 0.0 275732 5048 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
gdm 1374 0.0 0.0 305100 8224 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing
gdm 1376 0.0 0.0 377928 7896 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard
gdm 1378 0.0 0.0 332852 8088 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-sound
gdm 1384 0.0 0.2 487208 28232 tty1 Sl+ Oct25 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom
gdm 1404 0.0 0.0 204888 6572 tty1 Sl Oct25 0:00 /usr/lib/ibus/ibus-engine-simple
root 1542 0.0 0.0 415340 9200 ? Sl Oct25 0:00 gdm-session-worker [pam/gdm-password]
traject+ 1614 0.0 0.0 212128 6092 tty2 Ssl+ Oct25 0:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
traject+ 1616 0.5 0.6 401168 73680 tty2 Rl+ Oct25 5:46 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
traject+ 11777 0.0 0.0 21536 1108 pts/0 S+ 10:59 0:00 grep --color=auto gdm
root 21859 0.0 0.0 265416 8364 ? Sl 09:41 0:00 gdm-session-worker [pam/gdm-password]

$ ps aux | grep gdm3

Output:

root 948 0.0 0.0 308176 7956 ? Ssl Oct25 0:00 /usr/sbin/gdm3
gdm 1012 0.0 0.0 197796 5376 tty1 Ssl+ Oct25 0:00 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart
traject+ 1614 0.0 0.0 212128 6092 tty2 Ssl+ Oct25 0:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
traject+ 11779 0.0 0.0 21536 1108 pts/0 S+ 10:59 0:00 grep --color=auto gdm3

So i kill 948 process id at that time automatically gui not responded. after i run to start jibri and jibri-xorg through terminal but jibri xorg not started again same above issue came.

Can you please provide solution…

Thanks&Regards,
Keerthi


#6

Hi,

If you notice, 1616 is the PID for xorg. You just need to kill that. Not any other process.

Regards,
Abhijit


#7

Hi @abhijitnathwani,

  1. I kill 1616 process id at that time automatically GUI not responded. after i run to start jibri and jibri-xorg through terminal and jibri xorg activated. But again I faced recording failed to start issue.
    After click on start recording , first “Preparing to recording start” message came, after sometime one by one recording stop and recording failed to start message came.

jibri logs:

2018-10-26 13:16:31.966 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json
2018-10-26 13:16:32.501 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:
JibriConfig(recordingDirectory=/tmp/recordings, enabledStatsD=true, finalizeRecordingScriptPath=/path/to/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[xxxxxxxxxxxx], xmppDomain=xxxxxxxxxxxx, controlLogin=XmppCredentials(domain=auth.xxxxxxxxxxxx, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.xxxxxxxxxxxx, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.xxxxxxxxxxxx, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])
2018-10-26 13:16:32.961 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.internal.InternalHttpApi will be ignored.
2018-10-26 13:16:33.201 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on xxxxxxxxxxxx with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[xxxxxxxxxxxx], xmppDomain=xxxxxxxxxxxx, controlLogin=XmppCredentials(domain=auth.xxxxxxxxxxxx, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.xxxxxxxxxxxx, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.xxxxxxxxxxxx, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2018-10-26 13:16:33.207 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2018-10-26 13:16:33.419 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.connected() [prod environment: auth.xxxxxxxxxxxx@xxxxxxxxxxxx] Xmpp connection status: connected
2018-10-26 13:16:33.497 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.authenticated() [prod environment: auth.xxxxxxxxxxxx@xxxxxxxxxxxx] Xmpp connection status: authenticated (resume from previous? false)
2018-10-26 13:16:33.569 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.HttpApi will be ignored.

jicofo logs:

Jicofo 2018-10-26 13:13:54.960 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() sun.arch.data.model=64
Jicofo 2018-10-26 13:13:54.961 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() user.language=en
Jicofo 2018-10-26 13:13:54.961 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() java.specification.vendor=Oracle Corporation
Jicofo 2018-10-26 13:13:54.961 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() awt.toolkit=sun.awt.X11.XToolkit
Jicofo 2018-10-26 13:13:54.961 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() java.vm.info=mixed mode
Jicofo 2018-10-26 13:13:54.961 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() java.version=1.8.0_181
Jicofo 2018-10-26 13:13:54.961 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() java.ext.dirs=/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext
Jicofo 2018-10-26 13:13:54.962 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() sun.boot.class.path=/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-8-openjdk-amd64/jre/classes
Jicofo 2018-10-26 13:13:54.962 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() net.java.sip.communicator.SC_HOME_DIR_LOCATION=/etc/jitsi
Jicofo 2018-10-26 13:13:54.962 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() java.vendor=Oracle Corporation
Jicofo 2018-10-26 13:13:54.962 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() file.separator=/
Jicofo 2018-10-26 13:13:54.962 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() net.java.sip.communicator.impl.configuration.USE_PROPFILE_CONFIG=true
Jicofo 2018-10-26 13:13:54.963 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() net.java.sip.communicator.SC_HOME_DIR_NAME=jicofo
Jicofo 2018-10-26 13:13:54.963 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() java.vendor.url.bug=http://bugreport.sun.com/bugreport/
Jicofo 2018-10-26 13:13:54.963 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() sun.io.unicode.encoding=UnicodeLittle
Jicofo 2018-10-26 13:13:54.963 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() sun.cpu.endian=little
Jicofo 2018-10-26 13:13:54.963 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() net.java.sip.communicator.SC_LOG_DIR_LOCATION=/var/log/jitsi
Jicofo 2018-10-26 13:13:54.964 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() sun.cpu.isalist=
Jicofo 2018-10-26 13:13:54.964 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() Normal classloader
Jicofo 2018-10-26 13:13:54.964 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() failed to find jitsi-defaults.properties with class loader, will continue without it.
Jicofo 2018-10-26 13:13:54.964 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() Normal classloader
Jicofo 2018-10-26 13:13:54.965 INFO: [11] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() failed to find jitsi-default-overrides.properties with class loader, will continue without it.
Jicofo 2018-10-26 13:13:54.974 SEVERE: [11] impl.configuration.ConfigurationActivator.log() Error creating c lib instance for fixing file permissions
java.nio.file.FileSystemException: /etc/jitsi/jicofo: Operation not permitted
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileAttributeViews$Posix.setMode(UnixFileAttributeViews.java:238)
at sun.nio.fs.UnixFileAttributeViews$Posix.setPermissions(UnixFileAttributeViews.java:260)
at java.nio.file.Files.setPosixFilePermissions(Files.java:2045)
at net.java.sip.communicator.impl.configuration.ConfigurationActivator.fixPermissions(ConfigurationActivator.java:166)
at net.java.sip.communicator.impl.configuration.ConfigurationActivator.start(ConfigurationActivator.java:87)
at org.jitsi.impl.osgi.framework.BundleImpl.start(BundleImpl.java:307)
at org.jitsi.impl.osgi.framework.launch.FrameworkImpl.startLevelChanged(FrameworkImpl.java:472)
at org.jitsi.impl.osgi.framework.startlevel.FrameworkStartLevelImpl$Command.run(FrameworkStartLevelImpl.java:137)
at org.jitsi.impl.osgi.framework.AsyncExecutor.runInThread(AsyncExecutor.java:122)
at org.jitsi.impl.osgi.framework.AsyncExecutor.access$000(AsyncExecutor.java:28)
at org.jitsi.impl.osgi.framework.AsyncExecutor$1.run(AsyncExecutor.java:231)
Jicofo 2018-10-26 13:13:54.986 INFO: [11] util.NetworkUtils.().117 java.net.preferIPv6Addresses=null
Jicofo 2018-10-26 13:13:54.986 INFO: [11] util.NetworkUtils.().118 java.net.preferIPv4Stack=null
Jicofo 2018-10-26 13:13:54.991 INFO: [11] impl.netaddr.NetworkAddressManagerServiceImpl.start().92 Network Address Manager …[ STARTED ]
Jicofo 2018-10-26 13:13:54.992 INFO: [11] impl.netaddr.NetworkAddressManagerServiceImpl.start().98 Network Address Manager Service …[REGISTERED]
Jicofo 2018-10-26 13:13:54.996 INFO: [11] org.jitsi.version.AbstractVersionActivator.start().119 JiCoFo Version: JiCoFo 1.0.1.0-425
Jicofo 2018-10-26 13:13:55.200 INFO: [11] org.jitsi.jicofo.JitsiMeetGlobalConfig.init().170 Automatically grant ‘owner’ role: true
Jicofo 2018-10-26 13:13:55.200 INFO: [11] org.jitsi.jicofo.JitsiMeetGlobalConfig.init().183 Jibri requests in PENDING state will be timed out after: 90 seconds
Jicofo 2018-10-26 13:13:55.200 INFO: [11] org.jitsi.jicofo.JitsiMeetGlobalConfig.init().197 Lonely participants will be “terminated” after 20000 milliseconds
Jicofo 2018-10-26 13:13:55.224 INFO: [11] org.jitsi.jicofo.BridgeSelector.createBridgeSelectionStrategy().175 Using SingleBridgeSelectionStrategy
Jicofo 2018-10-26 13:13:55.224 INFO: [11] org.jitsi.jicofo.BridgeSelector.().145 Using org.jitsi.jicofo.BridgeSelector$SingleBridgeSelectionStrategy
Jicofo 2018-10-26 13:13:55.224 INFO: [11] org.jitsi.jicofo.BridgeSelector.init().599 Bridge failure reset threshold: 300000
Jicofo 2018-10-26 13:13:55.227 INFO: [11] org.jitsi.jicofo.JitsiMeetServices.start().351 Using a Jibri detector with MUC: JibriBrewery@internal.auth.xxxxxxxxxxxx
Jicofo 2018-10-26 13:13:55.303 INFO: [11] org.eclipse.jetty.server.Server.doStart() jetty-8.1.16.v20140903
Jicofo 2018-10-26 13:13:55.334 INFO: [11] org.eclipse.jetty.server.AbstractConnector.doStart() Started SelectChannelConnector@0.0.0.0:8888
Jicofo 2018-10-26 13:13:55.338 INFO: [1] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=localhost
Jicofo 2018-10-26 13:13:55.338 INFO: [1] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=115.248.119.203
Jicofo 2018-10-26 13:13:55.339 INFO: [1] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() org.jitsi.jicofo.jibri.PENDING_TIMEOUT=90
Jicofo 2018-10-26 13:13:55.339 INFO: [1] org.jitsi.impl.configuration.ConfigurationServiceImpl.log() org.jitsi.jicofo.jibri.BREWERY=JibriBrewery@internal.auth.xxxxxxxxxxxx
Jicofo 2018-10-26 13:13:55.343 INFO: [1] org.jitsi.xmpp.component.ComponentBase.loadConfig().202 Component org.jitsi.jicofo. config:
Jicofo 2018-10-26 13:13:55.343 INFO: [1] org.jitsi.xmpp.component.ComponentBase.loadConfig().203 ping interval: 10000 ms
Jicofo 2018-10-26 13:13:55.344 INFO: [1] org.jitsi.xmpp.component.ComponentBase.loadConfig().204 ping timeout: 5000 ms
Jicofo 2018-10-26 13:13:55.344 INFO: [1] org.jitsi.xmpp.component.ComponentBase.loadConfig().205 ping threshold: 3
Jicofo 2018-10-26 13:13:55.628 INFO: [26] org.jitsi.jicofo.xmpp.BaseBrewery.start().192 Joined brewery room: JibriBrewery@internal.auth.xxxxxxxxxxxx
Jicofo 2018-10-26 13:13:55.633 INFO: [26] org.jitsi.jicofo.ComponentsDiscovery.discoverServices().267 New component discovered: auth.xxxxxxxxxxxx, IQ Stanza (query jabber:iq:version) [to=focus@auth.xxxxxxxxxxxx/focus2457192656638,from=auth.xxxxxxxxxxxx,id=SaUt5-34,type=result,]
Jicofo 2018-10-26 13:13:55.633 INFO: [26] org.jitsi.jicofo.JitsiMeetServices.newNodeDiscovered().208 Detected XMPP server version: IQ Stanza (query jabber:iq:version) [to=focus@auth.xxxxxxxxxxxx/focus2457192656638,from=auth.xxxxxxxxxxxx,id=SaUt5-34,type=result,]
Jicofo 2018-10-26 13:13:55.644 INFO: [26] org.jitsi.jicofo.ComponentsDiscovery.discoverServices().267 New component discovered: focus.xxxxxxxxxxxx, null
Jicofo 2018-10-26 13:13:55.645 INFO: [26] org.jitsi.jicofo.ComponentsDiscovery.discoverServices().267 New component discovered: conference.xxxxxxxxxxxx, null
Jicofo 2018-10-26 13:13:55.646 INFO: [26] org.jitsi.jicofo.JitsiMeetServices.newNodeDiscovered().200 MUC component discovered: conference.xxxxxxxxxxxx
Jicofo 2018-10-26 13:13:55.654 INFO: [26] org.jitsi.jicofo.ComponentsDiscovery.discoverServices().267 New component discovered: jitsi-videobridge.xxxxxxxxxxxx, IQ Stanza (query jabber:iq:version) [to=focus@auth.xxxxxxxxxxxx/focus2457192656638,from=jitsi-videobridge.xxxxxxxxxxxx,id=SaUt5-43,type=result,]
Jicofo 2018-10-26 13:13:55.654 INFO: [26] org.jitsi.jicofo.BridgeSelector.addJvbAddress().214 Added videobridge: jitsi-videobridge.xxxxxxxxxxxx v: IQ Stanza (query jabber:iq:version) [to=focus@auth.xxxxxxxxxxxx/focus2457192656638,from=jitsi-videobridge.xxxxxxxxxxxx,id=SaUt5-43,type=result,]
Jicofo 2018-10-26 13:13:55.655 WARNING: [26] org.jitsi.jicofo.BridgeSelector.addJvbAddress().226 No pub-sub node mapped for jitsi-videobridge.xxxxxxxxxxxx
Jicofo 2018-10-26 13:13:55.674 INFO: [26] org.jitsi.jicofo.ComponentsDiscovery.discoverServices().267 New component discovered: recorder.xxxxxxxxxxxx, IQ Stanza (query jabber:iq:version) [to=focus@auth.xxxxxxxxxxxx/focus2457192656638,from=recorder.xxxxxxxxxxxx,id=SaUt5-48,type=result,]
Jicofo 2018-10-26 13:13:55.675 INFO: [26] org.jitsi.jicofo.ComponentsDiscovery.scheduleRediscovery().189 Services re-discovery interval: 30000
Jicofo 2018-10-26 13:13:55.683 INFO: [26] org.jitsi.jicofo.FocusManager.log() XMPP provider reg state: RegistrationState=Registered
Jicofo 2018-10-26 13:13:55.699 INFO: [26] org.jitsi.impl.protocol.xmpp.XmppProtocolProvider.doConnect().309 XMPP provider Jabber:focus@auth.xxxxxxxxxxxx/focus2457192656638@localhost connected (JID: focus@auth.xxxxxxxxxxxx/focus2457192656638)
Jicofo 2018-10-26 13:13:55.704 INFO: [44] org.jitsi.jicofo.JvbDoctor.log() Scheduled health-check task for: jitsi-videobridge.xxxxxxxxxxxx
Jicofo 2018-10-26 13:13:55.717 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().324 Added brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:13:55.717 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:13:55.718 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:13:55.719 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:13:55.719 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:15:01.235 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.removeInstance().368 Removed brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:15:01.236 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyInstanceOffline().163 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname went offline
Jicofo 2018-10-26 13:15:03.001 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().324 Added brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:15:03.001 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:15:03.010 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:15:03.011 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:15:03.011 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:16:31.762 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.removeInstance().368 Removed brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:16:31.762 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyInstanceOffline().163 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname went offline
Jicofo 2018-10-26 13:16:33.517 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().324 Added brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:16:33.517 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:16:33.518 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:16:33.519 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:16:33.520 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:18:02.276 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.removeInstance().368 Removed brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:18:02.280 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyInstanceOffline().163 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname went offline
Jicofo 2018-10-26 13:18:04.050 INFO: [37] org.jitsi.jicofo.xmpp.BaseBrewery.processInstanceStatusChanged().324 Added brewery instance: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname
Jicofo 2018-10-26 13:18:04.051 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:18:04.051 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true
Jicofo 2018-10-26 13:18:04.051 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.onInstanceStatusChanged().138 Received Jibri status
Jicofo 2018-10-26 13:18:04.052 INFO: [37] org.jitsi.jicofo.recording.jibri.JibriDetector.notifyJibriStatus().179 Jibri: jibribrewery@internal.auth.xxxxxxxxxxxx/jibri-nickname available: true

  1. Again login to the system that killed xorg process created with different process id and jibri-xorg automatically moved to the inactive status . so how can we handle this situation.

Can you Please provide a solution…

Thanks&Regards,
Keerthi.


#8

Hi @keerthireddyb ,
We used to have similar problems.
We did a workaround and it solved it.

  1. When jibri fails recording after some time or takes time to start and stop, it occurred to us on Ubuntu 18.04. We switched to Ubuntu 16.04 and it worked fine.
  2. For jibri xorg service, either you need to turn off your desktop manager (lightdm or gdm3), or you can allow xserver-xorg to be run by anyone if you just want to test without constantly going to console. The image below is an example of how to do it and you just need to reconfigure with dpkg.

For Ubuntu 16.04: dpkg-reconfigure x11-common
For Ubuntu 18.04: dpkg-reconfigure xserver-xorg-legacy

On a side note, use jibri version 5.1.58-1 or lower as the latest version has some issues and jicofo is unable to find it. I’ve not seen the changelog or updates after this post, but its not working till I wrote this.
Also, as mentioned in the installation video, please use jibri on other system where jitsi is not running.

Hope this solves your queries.

Regards,
Dhruvin


#9

Hi @bhattdhruvin,

Thanks for you suggestions,

  1. For jibri xorg service, either you need to turn off your desktop manager (lightdm or gdm3), or you can allow xserver-xorg to be run strong textby anyone if you just want to test without constantly going to console. The image below is an example of how to do it and you just need to reconfigure with dpkg.

For Ubuntu 16.04: dpkg-reconfigure x11-common
For Ubuntu 18.04: dpkg-reconfigure xserver-xorg-legacy

 I run the above cmd (dpkg-reconfigure xserver-xorg-legacy) but no use. again i faced same above issue.

On a side note, use jibri version 5.1.58-1 or lower as the latest version has some issues and jicofo is unable to find it. I’ve not seen the changelog or updates after this post, but its not working till I wrote this.

  In jibri installation process versions are not mentioned, how can i bring version's in jitsi installation cmd.

Also, as mentioned in the installation video, please use jibri on other system where jitsi is not running.

 Why use jibri in other system where jitsi not running? please explain. 
 Which type of problems we faced at the time of jibri and jitsi running same system?.

Thanks&regards,
Keerthi.


#10

Hello @keerthireddyb,

Before we move forward to answering your queries, I would like you to know that jibri is officially supported on platform ubuntu 16, and still has some issues on ubuntu 18.

1. For running jibri-xorg along with gdm3, please follow these steps:
Go to command line virtual terminal by pressing CTRL + ALT + F4
Log into your user with sudo access and log in as root by sudo su.

systemctl stop gdm3
ps -aux | grep xorg

note process id with xorg
kill -9 pid

then run

dpkg-reconfigure xserver-xorg-legacy

and set access to anyone.

Restart gdm3

systemctl start gdm3

This will let you run jibri-xorg along with gdm.

2. For older version of Jibri,

wget https://download.jitsi.org/unstable/jibri_5.1.58-1_all.deb
dpkg -i jibri_5.1.58-1_all.deb

You can see the current jibri version by

dpkg -l | grep jibri

3. Now, for your last query,

Check out https://github.com/jitsi/jibri/blob/master/doc/xmpp_api.md
It says that

Jibri can be configured to join multiple XMPP environments which can be used as a control surface for leveraging Jibri services

This means that one jibri configuration can be used to record multiple jitsi conferences on different domains.
This clearly says that Jibri has a headless installation, meaning jitsi is not required for jibri.

On the other hand, during jibri configuration, we add a hidden domain on jitsi side and configure a brewery room on jicofo. Jicofo will find all the mentioned hidden domains and try to join those in current jitsi conference. Thus, more than one jibri can be connected to one jitsi-meet.

And about the issue we face when we install both jitsi and jibri in same domain, the jicofo will fail to find the jibri and you’ll get a message

Recording is unavailable

At the end,
I would say you set up jibri on ubuntu 16, on a domain other than the jitsi-meet, to avoid all the problems.

Thanks and regards,
Dhruvin.


#11

Hi @bhattdhruvin,

I installed jitsi in one system (ubuntu 16.04) and jibri other ubuntu 16.04 system. but i faced recording unavailable issue.

jicofo log:

jicofo.log (290.0 KB)

jibri.log:

2018-11-01 12:51:18.677 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json
2018-11-01 12:51:19.167 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:
JibriConfig(recordingDirectory=/srv/recordings, enabledStatsD=true, finalizeRecordingScriptPath=/path/to/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[XXXXXXXXXXXXX], xmppDomain=XXXXXXXXXXXXX, controlLogin=XmppCredentials(domain=auth.XXXXXXXXXXXXX, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.XXXXXXXXXXXXX, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.XXXXXXXXXXXXX, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])
2018-11-01 12:51:19.610 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.internal.InternalHttpApi will be ignored.
2018-11-01 12:51:19.882 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on XXXXXXXXXXXXX with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[XXXXXXXXXXXXX], xmppDomain=XXXXXXXXXXXXX, controlLogin=XmppCredentials(domain=auth.XXXXXXXXXXXXX, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.XXXXXXXXXXXXX, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.XXXXXXXXXXXXX, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2018-11-01 12:51:19.891 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2018-11-01 12:51:49.914 WARNING: [22] org.jivesoftware.smackx.ping.PingManager.pingServerIfNecessary() XMPPConnection was not authenticated
2018-11-01 12:51:50.458 SEVERE: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Error connecting to xmpp environment: org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: ‘XXXXXXXXXXXXX:5222’ failed because: XXXXXXXXXXXXX/115.248.119.203 exception: java.net.SocketTimeoutException: connect timed out
2018-11-01 12:51:50.530 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.HttpApi will be ignored.

jitsi/jicofo/sip-communicator.properties:

org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=localhost
org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=XXXXXXXXXXXXX
org.jitsi.jicofo.jibri.BREWERY=JibriBrewery@internal.auth.XXXXXXXXXXXXX
org.jitsi.jicofo.jibri.PENDING_TIMEOUT=90

jitsi config:

fileRecordingsEnabled: true,
liveStreamingEnabled: true,
hiddenDomain: ‘recorder.XXXXXXXXXXXXX’,

prosody config:

Component “internal.auth.XXXXXXXXXXXXX” “muc”
modules_enabled = {
“ping”;
}
storage = “null”
muc_room_cache_size = 1000

VirtualHost “recorder.XXXXXXXXXXXXX”
modules_enabled = {
“ping”;
}
authentication = “internal_plain”

jibri config:

{
// NOTE: this is a SAMPLE config file, it will need to be configured with
// values from your environment

// Where recording files should be temporarily stored
"recording_directory":"/srv/recordings",
// The path to the script which will be run on completed recordings
"finalize_recording_script_path": "/path/to/finalize_recording.sh",
"xmpp_environments": [
    {
        // A friendly name for this environment which can be used
        //  for logging, stats, etc.
        "name": "prod environment",
        // The hosts of the XMPP servers to connect to as part of
        //  this environment
        "xmpp_server_hosts": [
            "XXXXXXXXXXXXX"
        ],
        // The xmpp domain we'll connect to on the XMPP server
        "xmpp_domain": "XXXXXXXXXXXXX",
        // Jibri will login to the xmpp server as a privileged user 
        "control_login": {
            // The domain to use for logging in
            "domain": "auth.XXXXXXXXXXXXX",
            // The credentials for logging in
            "username": "jibri",
            "password": "jibriauthpass"
        },
        // Using the control_login information above, Jibri will join 
        //  a control muc as a means of announcing its availability 
        //  to provide services for a given environment
        "control_muc": {
            "domain": "internal.auth.XXXXXXXXXXXXX",
            "room_name": "JibriBrewery",
            "nickname": "jibri-nickname"
        },
        // All participants in a call join a muc so they can exchange
        //  information.  Jibri can be instructed to join a special muc
        //  with credentials to give it special abilities (e.g. not being
        //  displayed to other users like a normal participant)
        "call_login": {
            "domain": "recorder.XXXXXXXXXXXXX",
            "username": "recorder",
            "password": "jibrirecorderpass"
        },
        // When jibri gets a request to start a service for a room, the room
        //  jid will look like:
        //  roomName@optional.prefixes.subdomain.xmpp_domain
        // We'll build the url for the call by transforming that into:
        //  https://xmpp_domain/subdomain/roomName
        // So if there are any prefixes in the jid (like jitsi meet, which
        //  has its participants join a muc at conference.xmpp_domain) then
        //  list that prefix here so it can be stripped out to generate
        //  the call url correctly
        "room_jid_domain_string_to_strip_from_start": "conference.",
        // The amount of time, in minutes, a service is allowed to continue.
        //  Once a service has been running for this long, it will be
        //  stopped (cleanly).  A value of 0 means an indefinite amount
        //  of time is allowed
        "usage_timeout": "0"
    }
]

}

please help me about this issue.

Thanks&Regards,
Keerthi.


#12

Hi @keerthireddyb,
As per the logs, it seems jicofo is unable to locate available jibri to join it into a room.
Please make sure you’ve entered the Jitsi-meet domain name in all config files, as jibri domain name is never required in any configuration file.
Please also make sure you’ve registered jibri in prosody.
Please also make sure you restart your prosody, jicofo and jitsi-videobridge services along with jibri service.

Your issue seems to be some configuration issue.
Please configure jibri as per the video given by jitsi community.

Thanks and regards,
Dhruvin


#13

Jibri cannot connect to your xmpp server on port 5222. Make sure your prosody server is listening on that interface on port 5222.


#14

Hi @damencho, @bhattdhruvin,

Again i restarted system and all (prosody,jibri,jicofo,jitsi-videobridge) services.after restarting i facing All recorders are currently busy issue.

jicofo.log:

jicofo.log (410.7 KB)

jibri.log:

2018-11-01 15:34:47.668 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json
2018-11-01 15:34:48.134 INFO: [1] org.jitsi.jibri.Main.loadConfig() Parsed config:
JibriConfig(recordingDirectory=/srv/recordings, enabledStatsD=true, finalizeRecordingScriptPath=/path/to/finalize_recording.sh, xmppEnvironments=[XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[XXXXXXXXXXXXX], xmppDomain=XXXXXXXXXXXXX, controlLogin=XmppCredentials(domain=auth.XXXXXXXXXXXXX, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.XXXXXXXXXXXXX, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.XXXXXXXXXXXXX, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)])
2018-11-01 15:34:48.559 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.internal.InternalHttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.internal.InternalHttpApi will be ignored.
2018-11-01 15:34:48.778 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() Connecting to xmpp environment on XXXXXXXXXXXXX with config XmppEnvironmentConfig(name=prod environment, xmppServerHosts=[XXXXXXXXXXXXX], xmppDomain=XXXXXXXXXXXXX, controlLogin=XmppCredentials(domain=auth.XXXXXXXXXXXXX, username=jibri, password=jibriauthpass), controlMuc=XmppMuc(domain=internal.auth.XXXXXXXXXXXXX, roomName=JibriBrewery, nickname=jibri-nickname), sipControlMuc=null, callLogin=XmppCredentials(domain=recorder.XXXXXXXXXXXXX, username=recorder, password=jibrirecorderpass), stripFromRoomDomain=conference., usageTimeoutMins=0, trustAllXmppCerts=true)
2018-11-01 15:34:48.783 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts config is enabled for this domain, all XMPP server provided certificates will be accepted
2018-11-01 15:34:48.998 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.connected() [prod environment: auth.XXXXXXXXXXXXX@XXXXXXXXXXXXX] Xmpp connection status: connected
2018-11-01 15:34:49.066 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.authenticated() [prod environment: auth.XXXXXXXXXXXXX@XXXXXXXXXXXXX] Xmpp connection status: authenticated (resume from previous? false)
2018-11-01 15:34:49.121 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRuntime() A provider org.jitsi.jibri.api.http.HttpApi registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider org.jitsi.jibri.api.http.HttpApi will be ignored.

please help me about this issue.

Thanks&Regards,
Keerthi.