Jitsi recording is getting closed in 10 sec

Hi Team,

Thanks in Advance,

I was able to Setup my own jitsi / jibri server. on AWS Ubuntu 18 version
But when i try to start recording a meeting or streaming live on you tube it is getting closed in 10 sec.
I don’t know if i am missing some thing from side while setup.
Please help me on fixing up this.

My jitsi server URL: https://meet.srit.online/
Youtube Video Live : https://youtu.be/PTKRVzGAp24

2 Likes

Maybe jicofo error. Check /var/log/jitsi/jicofo.log, if file don’t have that you create:

cat > /var/log/jitsi/jicofo.log
chmod 777 /var/log/jitsi/
chown jicofo:jitsi /var/log/jitsi/jicofo.log

Hi,
I have tried that but could not get it worked.
Below are the JVB logs which can be helpful if any.
2020-05-15 13:28:54.540 INFO: [19] Videobridge.createConference#320: create_conf, id=18cf3b94326d2a83 gid=null logging=false
2020-05-15 13:28:54.551 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.01119S. Sticky failure: false
2020-05-15 13:29:04.539 INFO: [19] Videobridge.createConference#320: create_conf, id=678bf7bcde686929 gid=null logging=false
2020-05-15 13:29:04.549 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.009944S. Sticky failure: false
2020-05-15 13:29:14.249 INFO: [17] VideobridgeExpireThread.expire#144: Running expire()
2020-05-15 13:29:14.540 INFO: [19] Videobridge.createConference#320: create_conf, id=24271e8009d6af66 gid=null logging=false
2020-05-15 13:29:14.591 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.051399S. Sticky failure: false
2020-05-15 13:29:24.540 INFO: [19] Videobridge.createConference#320: create_conf, id=9dd61b0c7cc43aa6 gid=null logging=false
2020-05-15 13:29:24.549 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.009281S. Sticky failure: false
2020-05-15 13:29:34.539 INFO: [19] Videobridge.createConference#320: create_conf, id=763d754a6db50c4a gid=null logging=false
2020-05-15 13:29:34.554 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.014616S. Sticky failure: false
2020-05-15 13:29:44.539 INFO: [19] Videobridge.createConference#320: create_conf, id=5975fd1c5b676d9d gid=null logging=false
2020-05-15 13:29:44.553 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.013989S. Sticky failure: false
2020-05-15 13:29:54.539 INFO: [19] Videobridge.createConference#320: create_conf, id=2d22e5e8cba63f03 gid=null logging=false
2020-05-15 13:29:54.706 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.16623S. Sticky failure: false
2020-05-15 13:30:04.540 INFO: [19] Videobridge.createConference#320: create_conf, id=7bcf9658cb948670 gid=null logging=false
2020-05-15 13:30:04.546 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.00667S. Sticky failure: false
2020-05-15 13:30:14.248 INFO: [17] VideobridgeExpireThread.expire#144: Running expire()
2020-05-15 13:30:14.540 INFO: [19] Videobridge.createConference#320: create_conf, id=37f4305ce67ef117 gid=null logging=false
2020-05-15 13:30:14.545 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.00603S. Sticky failure: false
2020-05-15 13:30:24.540 INFO: [19] Videobridge.createConference#320: create_conf, id=9a6c15713fd73c6b gid=null logging=false
2020-05-15 13:30:24.551 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.011834S. Sticky failure: false
2020-05-15 13:30:34.539 INFO: [19] Videobridge.createConference#320: create_conf, id=3b19eb250ec8ba40 gid=null logging=false
2020-05-15 13:30:34.549 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.010197S. Sticky failure: false
2020-05-15 13:30:44.540 INFO: [19] Videobridge.createConference#320: create_conf, id=b428e3d8d5146453 gid=null logging=false
2020-05-15 13:30:44.578 INFO: [19] AbstractHealthCheckService.run#171: Performed a successful health check in PT0.038548S. Sticky failure: false