LifeSize --> Jitsi


#22

it says:

root@jibri:/var/log/jitsi/jibri# journalctl -u jibri
– Logs begin at Thu 2019-02-07 12:29:09 UTC, end at Tue 2019-02-12 13:25:05 UTC. –
Feb 07 13:29:32 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[10994]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[10994]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[10994]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[11032]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[11032]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[11032]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[11052]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[11052]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[11052]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[11070]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[11070]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[11070]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.


#23

still not much, what about: journalctl -u jibri.service


#24

root@jibri:/var/log/jitsi/jibri# journalctl -u jibri.service
– Logs begin at Thu 2019-02-07 12:29:09 UTC, end at Tue 2019-02-12 13:38:00 UTC. –
Feb 07 13:29:32 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[10994]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[10994]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[10994]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[11032]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[11032]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[11032]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[11052]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[11052]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[11052]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Stopping Jibri Process…
Feb 07 13:29:33 jibri graceful_shutdown.sh[11070]: % Total % Received % Xferd Average Speed Time
Feb 07 13:29:33 jibri graceful_shutdown.sh[11070]: Dload Upload Total
Feb 07 13:29:33 jibri graceful_shutdown.sh[11070]: [158B blob data]
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Control process exited, code=exited status=7
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 07 13:29:33 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 07 13:29:33 jibri systemd[1]: Stopped Jibri Process.
Feb 07 13:29:33 jibri systemd[1]: Started Jibri Process.
lines 1-37


#25

yep, I realised it is the same. I’m out of ideas … not sure how to get the whole stack trace that you can see the end when doing service jibri status


#26

Feb 12 12:48:23 jibri systemd[1]: Stopping Jibri Process…
Feb 12 12:48:23 jibri graceful_shutdown.sh[4288]: % Total % Received % Xferd Average Speed Time
Feb 12 12:48:23 jibri graceful_shutdown.sh[4288]: Dload Upload Total
Feb 12 12:48:25 jibri launch.sh[3722]: 2019-02-12 12:48:25.229 INFORMATION: [15] org.jitsi.jibri.api.http.
Feb 12 12:48:25 jibri graceful_shutdown.sh[4288]: [237B blob data]
Feb 12 12:48:25 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 12 12:48:25 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 12 12:48:25 jibri systemd[1]: Stopped Jibri Process.
Feb 12 12:48:25 jibri systemd[1]: Started Jibri Process.
Feb 12 12:48:26 jibri launch.sh[4338]: Can’t load log handler “java.util.logging.FileHandler”
Feb 12 12:48:26 jibri launch.sh[4338]: java.nio.file.AccessDeniedException: /var/log/jitsi/jibri/log.0.txt
Feb 12 12:48:26 jibri launch.sh[4338]: java.nio.file.AccessDeniedException: /var/log/jitsi/jibri/log.0.txt
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.nio.fs.UnixException.translateToIOException(UnixExce
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.nio.fs.UnixException.rethrowAsIOException(UnixExcept
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.nio.fs.UnixException.rethrowAsIOException(UnixExcept
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFil
Feb 12 12:48:26 jibri launch.sh[4338]: at java.nio.channels.FileChannel.open(FileChannel.java:287)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.nio.channels.FileChannel.open(FileChannel.java:335)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.FileHandler.openFiles(FileHandler.java
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.FileHandler.(FileHandler.java:28
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(N
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.reflect.NativeConstructorAccessorImpl.newInstance(Na
Feb 12 12:48:26 jibri launch.sh[4338]: at sun.reflect.DelegatingConstructorAccessorImpl.newInstanc
Feb 12 12:48:26 jibri launch.sh[4338]: at java.lang.reflect.Constructor.newInstance(Constructor.ja
Feb 12 12:48:26 jibri launch.sh[4338]: at java.lang.Class.newInstance(Class.java:442)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.LogManager$5.run(LogManager.java:966)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.security.AccessController.doPrivileged(Native Metho
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.LogManager.loadLoggerHandlers(LogManag
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.LogManager.initializeGlobalHandlers(Lo
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.LogManager.access$1500(LogManager.java
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.LogManager$RootLogger.accessCheckedHan
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.Logger.getHandlers(Logger.java:1777)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.Logger.log(Logger.java:735)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.Logger.doLog(Logger.java:765)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.Logger.log(Logger.java:788)
Feb 12 12:48:26 jibri launch.sh[4338]: at java.util.logging.Logger.info(Logger.java:1490)
Feb 12 12:48:26 jibri launch.sh[4338]: at org.jitsi.jibri.MainKt.main(Main.kt:87)
Feb 12 12:48:26 jibri launch.sh[4338]: 2019-02-12 12:48:26.749 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:26 jibri launch.sh[4338]: 2019-02-12 12:48:26.757 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:26 jibri launch.sh[4338]: 2019-02-12 12:48:26.757 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:26 jibri launch.sh[4338]: 2019-02-12 12:48:26.757 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:27 jibri launch.sh[4338]: 2019-02-12 12:48:27.839 INFORMATION: [1] org.jitsi.jibri.Main.loadC
Feb 12 12:48:27 jibri launch.sh[4338]: JibriConfig(recordingDirectory=/srv/recordings, enabledStatsD=true,
Feb 12 12:48:28 jibri launch.sh[4338]: 2019-02-12 12:48:28.054:INFO::main: Logging initialized @2296ms to
Feb 12 12:48:28 jibri launch.sh[4338]: 2019-02-12 12:48:28.177:WARN:oejsh.ContextHandler:main: o.e.j.s.Ser
Feb 12 12:48:28 jibri launch.sh[4338]: 2019-02-12 12:48:28.178:WARN:oejsh.ContextHandler:main: Empty conte
Feb 12 12:48:28 jibri launch.sh[4338]: 2019-02-12 12:48:28.187:INFO:oejs.Server:main: jetty-9.4.z-SNAPSHOT
Feb 12 12:48:29 jibri launch.sh[4338]: 2019-02-12 12:48:29.056 WARNUNG: [1] org.glassfish.jersey.internal.
Feb 12 12:48:29 jibri launch.sh[4338]: 2019-02-12 12:48:29.351:INFO:oejsh.ContextHandler:main: Started o.e
Feb 12 12:48:29 jibri launch.sh[4338]: 2019-02-12 12:48:29.371:INFO:oejs.AbstractConnector:main: Started S
Feb 12 12:48:29 jibri launch.sh[4338]: 2019-02-12 12:48:29.372:INFO:oejs.Server:main: Started @3614ms
Feb 12 12:48:29 jibri launch.sh[4338]: 2019-02-12 12:48:29.694 INFORMATION: [1] org.jitsi.jibri.api.xmpp.X
Feb 12 12:48:29 jibri launch.sh[4338]: 2019-02-12 12:48:29.712 INFORMATION: [1] org.jitsi.jibri.api.xmpp.X
Feb 12 12:48:30 jibri launch.sh[4338]: 2019-02-12 12:48:30.691 INFORMATION: [1] class org.jitsi.xmpp.muccl
Feb 12 12:48:30 jibri launch.sh[4338]: 2019-02-12 12:48:30.896 INFORMATION: [1] class org.jitsi.xmpp.muccl
Feb 12 12:48:30 jibri launch.sh[4338]: 2019-02-12 12:48:30.968:WARN:oejsh.ContextHandler:main: o.e.j.s.Ser
Feb 12 12:48:30 jibri launch.sh[4338]: 2019-02-12 12:48:30.968:WARN:oejsh.ContextHandler:main: Empty conte
Feb 12 12:48:30 jibri launch.sh[4338]: 2019-02-12 12:48:30.970:INFO:oejs.Server:main: jetty-9.4.z-SNAPSHOT
Feb 12 12:48:31 jibri launch.sh[4338]: 2019-02-12 12:48:31.147 WARNUNG: [1] org.glassfish.jersey.internal.
Feb 12 12:48:31 jibri launch.sh[4338]: 2019-02-12 12:48:31.250:INFO:oejsh.ContextHandler:main: Started o.e
Feb 12 12:48:31 jibri launch.sh[4338]: 2019-02-12 12:48:31.254:INFO:oejs.AbstractConnector:main: Started S
Feb 12 12:48:31 jibri launch.sh[4338]: 2019-02-12 12:48:31.256:INFO:oejs.Server:main: Started @5498ms
Feb 12 12:48:34 jibri systemd[1]: Stopping Jibri Process…
Feb 12 12:48:34 jibri graceful_shutdown.sh[4397]: % Total % Received % Xferd Average Speed Time
Feb 12 12:48:34 jibri graceful_shutdown.sh[4397]: Dload Upload Total
Feb 12 12:48:35 jibri launch.sh[4338]: 2019-02-12 12:48:35.384 INFORMATION: [15] org.jitsi.jibri.api.http.
Feb 12 12:48:35 jibri graceful_shutdown.sh[4397]: [237B blob data]
Feb 12 12:48:35 jibri systemd[1]: jibri.service: Main process exited, code=exited, status=143/n/a
Feb 12 12:48:35 jibri systemd[1]: jibri.service: Failed with result ‘exit-code’.
Feb 12 12:48:35 jibri systemd[1]: Stopped Jibri Process.
Feb 12 12:48:35 jibri systemd[1]: Started Jibri Process.
Feb 12 12:48:36 jibri launch.sh[4458]: Can’t load log handler “java.util.logging.FileHandler”
Feb 12 12:48:36 jibri launch.sh[4458]: java.nio.file.AccessDeniedException: /var/log/jitsi/jibri/log.0.txt
Feb 12 12:48:36 jibri launch.sh[4458]: java.nio.file.AccessDeniedException: /var/log/jitsi/jibri/log.0.txt
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.nio.fs.UnixException.translateToIOException(UnixExce
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.nio.fs.UnixException.rethrowAsIOException(UnixExcept
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.nio.fs.UnixException.rethrowAsIOException(UnixExcept
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFil
Feb 12 12:48:36 jibri launch.sh[4458]: at java.nio.channels.FileChannel.open(FileChannel.java:287)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.nio.channels.FileChannel.open(FileChannel.java:335)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.FileHandler.openFiles(FileHandler.java
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.FileHandler.(FileHandler.java:28
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(N
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.reflect.NativeConstructorAccessorImpl.newInstance(Na
Feb 12 12:48:36 jibri launch.sh[4458]: at sun.reflect.DelegatingConstructorAccessorImpl.newInstanc
Feb 12 12:48:36 jibri launch.sh[4458]: at java.lang.reflect.Constructor.newInstance(Constructor.ja
Feb 12 12:48:36 jibri launch.sh[4458]: at java.lang.Class.newInstance(Class.java:442)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.lang.Class.newInstance(Class.java:442)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.LogManager$5.run(LogManager.java:966)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.security.AccessController.doPrivileged(Native Metho
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.LogManager.loadLoggerHandlers(LogManag
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.LogManager.initializeGlobalHandlers(Lo
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.LogManager.access$1500(LogManager.java
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.LogManager$RootLogger.accessCheckedHan
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.Logger.getHandlers(Logger.java:1777)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.Logger.log(Logger.java:735)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.Logger.doLog(Logger.java:765)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.Logger.log(Logger.java:788)
Feb 12 12:48:36 jibri launch.sh[4458]: at java.util.logging.Logger.info(Logger.java:1490)
Feb 12 12:48:36 jibri launch.sh[4458]: at org.jitsi.jibri.MainKt.main(Main.kt:87)
Feb 12 12:48:36 jibri launch.sh[4458]: 2019-02-12 12:48:36.597 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:36 jibri launch.sh[4458]: 2019-02-12 12:48:36.605 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:36 jibri launch.sh[4458]: 2019-02-12 12:48:36.606 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:36 jibri launch.sh[4458]: 2019-02-12 12:48:36.606 INFORMATION: [1] org.jitsi.jibri.Main.main(
Feb 12 12:48:37 jibri launch.sh[4458]: 2019-02-12 12:48:37.690 INFORMATION: [1] org.jitsi.jibri.Main.loadC
Feb 12 12:48:37 jibri launch.sh[4458]: JibriConfig(recordingDirectory=/srv/recordings, enabledStatsD=true,
Feb 12 12:48:37 jibri launch.sh[4458]: 2019-02-12 12:48:37.863:INFO::main: Logging initialized @2062ms to
Feb 12 12:48:37 jibri launch.sh[4458]: 2019-02-12 12:48:37.975:WARN:oejsh.ContextHandler:main: o.e.j.s.Ser
Feb 12 12:48:37 jibri launch.sh[4458]: 2019-02-12 12:48:37.975:WARN:oejsh.ContextHandler:main: Empty conte
Feb 12 12:48:37 jibri launch.sh[4458]: 2019-02-12 12:48:37.993:INFO:oejs.Server:main: jetty-9.4.z-SNAPSHOT
Feb 12 12:48:38 jibri launch.sh[4458]: 2019-02-12 12:48:38.923 WARNUNG: [1] org.glassfish.jersey.internal.
Feb 12 12:48:39 jibri launch.sh[4458]: 2019-02-12 12:48:39.232:INFO:oejsh.ContextHandler:main: Started o.e
Feb 12 12:48:39 jibri launch.sh[4458]: 2019-02-12 12:48:39.251:INFO:oejs.AbstractConnector:main: Started S
Feb 12 12:48:39 jibri launch.sh[4458]: 2019-02-12 12:48:39.252:INFO:oejs.Server:main: Started @3451ms
Feb 12 12:48:39 jibri launch.sh[4458]: 2019-02-12 12:48:39.617 INFORMATION: [1] org.jitsi.jibri.api.xmpp.X
Feb 12 12:48:39 jibri launch.sh[4458]: 2019-02-12 12:48:39.642 INFORMATION: [1] org.jitsi.jibri.api.xmpp.X
Feb 12 12:48:40 jibri launch.sh[4458]: 2019-02-12 12:48:40.621 INFORMATION: [1] class org.jitsi.xmpp.muccl
Feb 12 12:48:40 jibri launch.sh[4458]: 2019-02-12 12:48:40.761 INFORMATION: [1] class org.jitsi.xmpp.muccl
Feb 12 12:48:40 jibri launch.sh[4458]: 2019-02-12 12:48:40.818:WARN:oejsh.ContextHandler:main: o.e.j.s.Ser
Feb 12 12:48:40 jibri launch.sh[4458]: 2019-02-12 12:48:40.820:WARN:oejsh.ContextHandler:main: Empty conte
Feb 12 12:48:40 jibri launch.sh[4458]: 2019-02-12 12:48:40.820:INFO:oejs.Server:main: jetty-9.4.z-SNAPSHOT
Feb 12 12:48:40 jibri launch.sh[4458]: 2019-02-12 12:48:40.958 WARNUNG: [1] org.glassfish.jersey.internal.
Feb 12 12:48:41 jibri launch.sh[4458]: 2019-02-12 12:48:41.060:INFO:oejsh.ContextHandler:main: Started o.e
Feb 12 12:48:41 jibri launch.sh[4458]: 2019-02-12 12:48:41.067:INFO:oejs.AbstractConnector:main: Started S
Feb 12 12:48:41 jibri launch.sh[4458]: 2019-02-12 12:48:41.068:INFO:oejs.Server:main: Started @5268ms
lines 26536-26572/26572 (END)

thats the end. Does this help you?


#27

Can you fix that, for some reason the folder permissions are wrong.
They are normally fixed while installing jibri https://github.com/jitsi/jibri/blob/master/debian/postinst#L27
Something had change those in the meantime.


#29

Ok… I have following logs now:

log.1.txt (3.5 KB)
log.0.txt (70.6 KB)
ffmpeg.0.txt (9.8 KB)
browser.0.txt (1.8 MB)


#30

Have you looked at the log files? Have you tried fixing this error:
2019-02-13 08:40:31.010 SCHWERWIEGEND: [90] org.jitsi.jibri.service.impl.FileRecordingJibriService.finalize() Failed to run finalize script: java.io.IOException: Cannot run program “/path/to/finalize_recording.sh”: error=2, Datei oder Verzeichnis nicht gefunden with stack:

This is the script that will handle the recording. Or you can enable dropbox integration where the recording will be uploaded to your Dropbox account, you will need to install jitsi-upload-integrations package.


#31

yes, i checked the logs and saw this error… but I dont know where i can edit the script. Or other question… Is it necessary at all regarding to my lifesizeproblem?


#32

This is for recording … Are you calling the room and this one triggers, this is strange?


#33

nope. when I try calling the room with my lifesize nothing happens. But I mean… Do I need to configure my jibri for recording regarding to my lifesizeproblem. I don’t necessarily have to record my conferences. I just want that I can call a jitsi room with my lifesize


#34

It is strange to me that it hits the finalize recording script, or maybe there is a bug…

I just saw that before that there are some other errors:

2019-02-13 08:40:24.852 INFORMATION: [86] org.jitsi.jibri.util.JibriSubprocess.ffmpeg.launch() Starting ffmpeg with command ffmpeg -y -v info -f x11grab -draw_mouse 0 -r 30 -s 1280x720 -thread_queue_size 4096 -i :0.0+0,0 -f alsa -thread_queue_size 4096 -i hw:0,1,0 -acodec aac -strict -2 -ar 44100 -c:v libx264 -preset veryfast -profile:v main -level 3.1 -pix_fmt yuv420p -r 30 -crf 25 -g 60 -tune zerolatency -f mp4 /srv/recordings/lxkveonnokerdswf/123_2019-02-13-08-40-20.mp4 ([ffmpeg, -y, -v, info, -f, x11grab, -draw_mouse, 0, -r, 30, -s, 1280x720, -thread_queue_size, 4096, -i, :0.0+0,0, -f, alsa, -thread_queue_size, 4096, -i, hw:0,1,0, -acodec, aac, -strict, -2, -ar, 44100, -c:v, libx264, -preset, veryfast, -profile:v, main, -level, 3.1, -pix_fmt, yuv420p, -r, 30, -crf, 25, -g, 60, -tune, zerolatency, -f, mp4, /srv/recordings/lxkveonnokerdswf/123_2019-02-13-08-40-20.mp4])
2019-02-13 08:40:29.867 FEIN: [54] org.jitsi.jibri.util.ProcessStatePublisher.ffmpeg.invoke() Process ffmpeg hasn't written in 2 seconds, publishing periodic update
2019-02-13 08:40:29.871 INFORMATION: [90] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegProcessUpdate() Ffmpeg quit abruptly.  Last output line: :0.0+0,0: Invalid argument
2019-02-13 08:40:29.873 INFORMATION: [90] org.jitsi.jibri.capture.ffmpeg.FfmpegCapturer.onFfmpegStateMachineStateChange() Ffmpeg capturer transitioning from state Starting up to Error: SESSION Ffmpeg failed to start

ffmpeg is installed? Have you hit the recording button?


#35

yes. ffmpeg is installed (7:3.4.4-0ubuntu0.18.04.1)

yes I hit the recording button.

Now it says sometimes “All recorders are currently busy - we’re working on freeing recording resources. Please try again in a few minutes.”

Or is it possible that my mistake isnt in jibri- but in jitsi-server?

log.9.txt (36.3 KB)
log.8.txt (455 Bytes)
log.7.txt (3.5 KB)
log.6.txt (3.5 KB)
log.5.txt (3.5 KB)
log.4.txt (3.5 KB)
log.3.txt (3.5 KB)
log.2.txt (3.5 KB)
log.1.txt (3.5 KB)
log.0.txt (34.9 KB)
ffmpeg.8.txt (12.3 KB)
ffmpeg.7.txt (2.5 KB)
ffmpeg.6.txt (7.4 KB)
ffmpeg.5.txt (7.4 KB)
ffmpeg.4.txt (2.5 KB)
ffmpeg.3.txt (19.7 KB)
ffmpeg.2.txt (2.5 KB)
ffmpeg.1.txt (4.9 KB)
ffmpeg.0.txt (4.9 KB)
browser.8.txt (2.2 MB)
browser.7.txt (446.4 KB)
browser.6.txt (1.4 MB)
browser.5.txt (1.4 MB)
browser.4.txt (445.8 KB)
browser.3.txt (3.8 MB)
browser.2.txt (491.2 KB)
browser.1.txt (1.0 MB)
browser.0.txt (987.9 KB)


#36

I don’t know.
Restart jibri, see at the same time whether it sees the jibri connecting and does it detect it you will see “Added brewery instance …”.
Do you have the setting org.jitsi.jicofo.jibri.SIP_BREWERY=... in jicofo’s sip-communicator.properties file?


#37

jicofo’s sip-communicator.properties file:

org.jitsi.jicofo.jibri.BREWERY=JibriBrewery@internal.auth.jitsi-konferenz.uk-augsburg.de
org.jitsi.jicofo.jibri.PENDING_TIMEOUT=90


maybe this information helps you:
when I press “start recording” on the jitsi-meet interface, I can see that my jibri server starts google chrome, then it joins the conference.After 5 seconds it closes chrome.
Meanwhile you dont realize in the jitsi-meet interface, that there is somebody connected.


#38

This is only for recorder/streames jibris. Change it to org.jitsi.jicofo.jibri.SIP_BREWERY restart jicofo and then jibri and retry inviting your room.


#39

what do you mean with “retry inviting your room”?

btw maybe this information helps you:
when I press “start recording” on the jitsi-meet interface, I can see that my jibri server starts google chrome, then it joins the conference.After 5 seconds it closes chrome.
Meanwhile you dont realize in the jitsi-meet interface, that there is somebody connected.


#40

You are trying to invite a lifesize, room equipment to the conference.
It is not done through recording. In one of the documents I posted above it is briefly described how to configure this, so when you open the ‘+’(invite people, numbers, rooms) in the interface and you can search which room to invite and when you click it, it will be invited which triggers a different path than the one for recording. It uses pjsua sip client, which you should already had installed to call the lifesize equipment using sip video call.


#41

I just tried to configure jibri until now. I thought that I need a working jibri first before I go to the next step.

Should I ignore the jibri errors and just continue with configurating the sip gtw?
Or what do you suggest?


#42

I would say sip gw, but if you want to first make jibri work, then put an empty post-process bash file or something that will not throw errors. I suspect it has some problems with ffmpeg which anyway needs fixing for sip gw … Before every attempt you can clear jibri logs and restart it so you don’t upload a thousand files. We have a real job to do and not many people will spend time of downloading 10 files and open each one to check for errors, try fixing the errors you see by yourself before coming back for help. Help us, to help you, thank you.