All recorders are currently busy issue faced when we click start recording


#21

Hi @damencho, @Aaron_van_Meerten, @Tanvir, @bbaldino,

I installed jitsi-meet, jicofo unstable versions.

$ apt-cache policy jitsi-meet
jitsi-meet:
Installed: 1.0.3389-1
Candidate: 1.0.3389-1
Version table:
*** 1.0.3389-1 500
500 https://download.jitsi.org unstable/ Packages
100 /var/lib/dpkg/status
1.0.3388-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3387-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3386-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3385-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3384-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3383-1 500
500 https://download.jitsi.org stable/ Packages
500 https://download.jitsi.org unstable/ Packages
1.0.3382-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3381-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3380-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3379-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3378-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3377-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3376-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3375-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3374-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3373-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3372-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3371-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3370-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3369-1 500
500 https://download.jitsi.org unstable/ Packages
1.0.3344-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3229-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3135-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2988-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2794-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2635-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2467-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2098-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1622-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1595-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1465-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1338-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1294-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1217-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1108-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1072-1 500
500 https://download.jitsi.org stable/ Packages

$ apt-cache policy jicofo
jicofo:
Installed: 1.0-443-1
Candidate: 1.0-443-1
Version table:
*** 1.0-443-1 500
500 https://download.jitsi.org unstable/ Packages
100 /var/lib/dpkg/status
1.0-442-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-440-1 500
500 https://download.jitsi.org stable/ Packages
500 https://download.jitsi.org unstable/ Packages
1.0-439-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-438-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-437-1 500
500 https://download.jitsi.org stable/ Packages
500 https://download.jitsi.org unstable/ Packages
1.0-436-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-435-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-434-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-433-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-432-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-431-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-430-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-429-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-428-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-427-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-426-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-425-1 500
500 https://download.jitsi.org stable/ Packages
500 https://download.jitsi.org unstable/ Packages
1.0-424-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-423-1 500
500 https://download.jitsi.org unstable/ Packages
1.0-417-1 500
500 https://download.jitsi.org stable/ Packages
1.0-405-1 500
500 https://download.jitsi.org stable/ Packages
1.0-394-1 500
500 https://download.jitsi.org stable/ Packages
1.0-388-1 500
500 https://download.jitsi.org stable/ Packages
1.0-371-1 500
500 https://download.jitsi.org stable/ Packages
1.0-357-1 500
500 https://download.jitsi.org stable/ Packages
1.0-320-1 500
500 https://download.jitsi.org stable/ Packages
1.0-319-1 500
500 https://download.jitsi.org stable/ Packages
1.0-304-1 500
500 https://download.jitsi.org stable/ Packages
1.0-298-1 500
500 https://download.jitsi.org stable/ Packages
1.0-295-1 500
500 https://download.jitsi.org stable/ Packages
1.0-292-1 500
500 https://download.jitsi.org stable/ Packages
1.0-273-1 500
500 https://download.jitsi.org stable/ Packages
1.0-267-1 500
500 https://download.jitsi.org stable/ Packages

jicofo Logs:

jicofo.log (177.4 KB)

Again i faced same issue i.e All recorders are currently busy issue faced when we click start recording.

Please provide solution for above issue.

Thanks,
Keerthi.


#22

Hi @damencho, @Aaron_van_Meerten, @Tanvir, @bbaldino,

Can you please provide a solution for this issue.

Thanks,
Keerthi.


#23

@keerthireddyb use this jibri works well with jicofo stable…atleast works for me…use that…!!


#24

@keerthireddyb your most recent jicofo logs show Jibri having an error. Please attach the Jibri logs as well.


#25

Hi @bbaldino,

jibri logs:

log.0.txt (10.8 KB)


#26

Hi @keerthireddyb,

Please use the version 5.1.58-1 as mentioned by Tanvir above, as it is highly stable.
Also, as per your logs, it seems chrome failed to start and is related to jibri-xorg.
Every time you restart jibri service, make sure you check whether jibri-xorg is running or not.

Thanks.


#27

Hi @bhattdhruvin, @Tanvir,

I installed jibri 5.1.58-1. and jicofo stable versions. but i faced below issue.

jibri logs:

log.0.txt (8.4 KB)

jicofo logs:

jicofo.log (92.4 KB)

jibri status:

jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2018-11-26 16:37:59 IST; 13min ago
Process: 393 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=7)
Main PID: 398 (java)
CGroup: /system.slice/jibri.service
├─ 398 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/jibri/jibri.jar --config /etc/jitsi
├─ 501 /usr/local/bin/chromedriver --port=25588 --log-path=/tmp/chromedriver.log
├─ 4496 /usr/local/bin/chromedriver --port=12635 --log-path=/tmp/chromedriver.log
└─31762 /usr/local/bin/chromedriver --port=7123 --log-path=/tmp/chromedriver.log

Nov 26 16:38:50 abacusatc launch.sh[398]: org.jitsi.jibri.JibriManager.startFileRecording(JibriManager.kt:121)
Nov 26 16:38:50 abacusatc launch.sh[398]: org.jitsi.jibri.api.xmpp.XmppApi.handleStartService(XmppApi.kt:285)
Nov 26 16:38:50 abacusatc launch.sh[398]: org.jitsi.jibri.api.xmpp.XmppApi.access$handleStartService(XmppApi.kt:68)
Nov 26 16:38:50 abacusatc launch.sh[398]: org.jitsi.jibri.api.xmpp.XmppApi$handleStartJibriIq$1.run(XmppApi.kt:200)
Nov 26 16:38:50 abacusatc launch.sh[398]: java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Nov 26 16:38:50 abacusatc launch.sh[398]: java.util.concurrent.FutureTask.run(FutureTask.java:266)
Nov 26 16:38:50 abacusatc launch.sh[398]: java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
Nov 26 16:38:50 abacusatc launch.sh[398]: java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
Nov 26 16:38:50 abacusatc launch.sh[398]: java.lang.Thread.run(Thread.java:748)
Nov 26 16:38:50 abacusatc launch.sh[398]: 2018-11-26 16:38:50.863 INFO: [39] org.jitsi.jibri.api.xmpp.XmppApi.run() Sending start service respo

jibri-xorg status:

jibri-xorg.service - Jibri Xorg Process
Loaded: loaded (/etc/systemd/system/jibri-xorg.service; disabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2018-11-26 16:37:59 IST; 14min ago
Process: 362 ExecStart=/usr/bin/Xorg -nocursor -noreset +extension RANDR +extension RENDER -logfile /tmp/xorg.log -config /etc/jitsi/jibri/xo
Main PID: 362 (code=exited, status=1/FAILURE)

Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Unit entered failed state.
Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Failed with result ‘exit-code’.
Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Service hold-off time over, scheduling restart.
Nov 26 16:37:59 abacusatc systemd[1]: Stopped Jibri Xorg Process.
Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Start request repeated too quickly.
Nov 26 16:37:59 abacusatc systemd[1]: Failed to start Jibri Xorg Process.
Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Unit entered failed state.
Nov 26 16:37:59 abacusatc systemd[1]: jibri-xorg.service: Failed with result ‘start-limit-hit’.
lines 1-15/15 (END)

Versions:

$apt-cache policy jitsi-meet
jitsi-meet:
Installed: 1.0.3383-1
Candidate: 1.0.3383-1
Version table:
*** 1.0.3383-1 500
500 https://download.jitsi.org stable/ Packages
100 /var/lib/dpkg/status
1.0.3344-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3229-1 500
500 https://download.jitsi.org stable/ Packages
1.0.3135-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2988-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2794-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2635-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2467-1 500
500 https://download.jitsi.org stable/ Packages
1.0.2098-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1622-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1595-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1465-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1338-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1294-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1217-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1108-1 500
500 https://download.jitsi.org stable/ Packages
1.0.1072-1 500
500 https://download.jitsi.org stable/ Packages

$ apt-cache policy jicofo
jicofo:
Installed: 1.0-440-1
Candidate: 1.0-440-1
Version table:
*** 1.0-440-1 500
500 https://download.jitsi.org stable/ Packages
100 /var/lib/dpkg/status
1.0-437-1 500
500 https://download.jitsi.org stable/ Packages
1.0-425-1 500
500 https://download.jitsi.org stable/ Packages
1.0-417-1 500
500 https://download.jitsi.org stable/ Packages
1.0-405-1 500
500 https://download.jitsi.org stable/ Packages
1.0-394-1 500
500 https://download.jitsi.org stable/ Packages
1.0-388-1 500
500 https://download.jitsi.org stable/ Packages
1.0-371-1 500
500 https://download.jitsi.org stable/ Packages
1.0-357-1 500
500 https://download.jitsi.org stable/ Packages
1.0-320-1 500
500 https://download.jitsi.org stable/ Packages
1.0-319-1 500
500 https://download.jitsi.org stable/ Packages
1.0-304-1 500
500 https://download.jitsi.org stable/ Packages
1.0-298-1 500
500 https://download.jitsi.org stable/ Packages
1.0-295-1 500
500 https://download.jitsi.org stable/ Packages
1.0-292-1 500
500 https://download.jitsi.org stable/ Packages
1.0-273-1 500
500 https://download.jitsi.org stable/ Packages
1.0-267-1 500
500 https://download.jitsi.org stable/ Packages

$ apt-cache policy jibri
jibri:
Installed: 5.1.58-1
Candidate: 6.0.59-1
Version table:
6.0.59-1 500
500 https://download.jitsi.org unstable/ Packages
*** 5.1.58-1 500
500 https://download.jitsi.org unstable/ Packages
100 /var/lib/dpkg/status
5.0.57-1 500
500 https://download.jitsi.org unstable/ Packages
4.2.56-1 500
500 https://download.jitsi.org unstable/ Packages
4.1.54-1 500
500 https://download.jitsi.org unstable/ Packages
4.0.53-1 500
500 https://download.jitsi.org unstable/ Packages
3.0.52-1 500
500 https://download.jitsi.org unstable/ Packages
2.0.51-1 500
500 https://download.jitsi.org unstable/ Packages
1.4.50-1 500
500 https://download.jitsi.org unstable/ Packages
1.3.49-1 500
500 https://download.jitsi.org unstable/ Packages
1.2.48-1 500
500 https://download.jitsi.org unstable/ Packages

Please provide a solution.

Thanks,
Keerthi.


#28

jibri-xorg failed…try to investigate why…without this running properly it won’t work


#29

@keerthireddyb
Please refer Recording failed to start and Chrome failed to start: exited abnormally for jibri-xorg.

Thanks and Regards,
Dhruvin


#30

Hi @bhattdhruvin, @Tanvir,

I started xorg after stopped GUI with use of lightdm but again xorg failed. please help how to solve the above issue.

Thanks,
Keerthi.


#31

Hi All, @damencho, @bhattdhruvin, @Tanvir, @bbaldino,

I really frustrated to solve this issue, Can you please provide a solution for the above issue.

Thanks You,
Keerthi.


#32

Hi @keerthireddyb,
Please follow these steps to see if it works.
Let us take Computer A as one with Jitsi-meet installed and Computer B as one with Jibri installed.
The computer with Jibri i.e. B should be ubuntu 16.04, as I am facing issues in Ubuntu 18.04 Desktop version.
Install and configure jitsi-meet and jibri as per given docs.
Now take remote control of B using ssh in A and login as sudo user.
First thing, turn off lightdm service:

systemctl stop lightdm

Now check if any other services using xorg:

ps -aux | grep xorg

kill any process you see except the last one. In short there has to be only one xorg line in the above output.

Now start jibri-xorg:

service jibri-xorg start

Now check whether the service started:

service jibri-xorg status

If it is running with no issues, then start jibri:

service jibri start

If the service doesn’t start, please write here with your journalctl logs.
Please note that you are only using the computer with jitsi-meet installed (i.e. A) and you are not touching the jibri computer (i.e. B) after installation. Everything is to be done using terminal in A.

Regards,
Dhruvin


#33

Hi @bhattdhruvin,

Thank you for your response, I fallowed your steps but still i am unable to start jibri xorg.

$ systemctl stop lightdm

$ ps -aux | grep xorg
root 11795 0.0 0.0 21292 1020 pts/51 S+ 11:21 0:00 grep --color=auto xorg

$ service jibri-xorg start

$ ps -aux | grep xorg
root 11931 0.0 0.0 21292 956 pts/51 S+ 11:21 0:00 grep --color=auto xorg

$ service jibri-xorg status
● jibri-xorg.service - Jibri Xorg Process
Loaded: loaded (/etc/systemd/system/jibri-xorg.service; disabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2018-12-10 11:21:23 IST; 23s ago
Process: 11866 ExecStart=/usr/bin/Xorg -nocursor -noreset +extension RANDR +extension RENDER -logfile /tmp/xorg.log -config /etc/jitsi/jibri/
Main PID: 11866 (code=exited, status=1/FAILURE)

Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Main process exited, code=exited, status=1/FAILURE
Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Unit entered failed state.
Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Failed with result ‘exit-code’.
Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Service hold-off time over, scheduling restart.
Dec 10 11:21:23 abacusatc systemd[1]: Stopped Jibri Xorg Process.
Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Start request repeated too quickly.
Dec 10 11:21:23 abacusatc systemd[1]: Failed to start Jibri Xorg Process.
Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Unit entered failed state.
Dec 10 11:21:23 abacusatc systemd[1]: jibri-xorg.service: Failed with result ‘start-limit-hit’.

$ service jibri start

$ service jibri status
● jibri.service - Jibri Process
Loaded: loaded (/etc/systemd/system/jibri.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2018-12-10 11:22:01 IST; 6s ago
Process: 12040 ExecStop=/opt/jitsi/jibri/graceful_shutdown.sh (code=exited, status=7)
Main PID: 12046 (java)
CGroup: /system.slice/jibri.service
└─12046 java -Djava.util.logging.config.file=/etc/jitsi/jibri/logging.properties -jar /opt/jitsi/jibri/jibri.jar --config /etc/jitsi

Dec 10 11:22:02 abacusatc launch.sh[12046]: 2018-12-10 11:22:02.737 INFO: [1] org.jitsi.jibri.api.xmpp.XmppApi.start() The trustAllXmppCerts co
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.225 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.connected() [prod enviro
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.286 INFO: [1] class org.jitsi.xmpp.mucclient.MucClient.authenticated() [prod en
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.300:WARN:oejsh.ContextHandler:main: o.e.j.s.ServletContextHandler@26a529dc{/,nu
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.301:WARN:oejsh.ContextHandler:main: Empty contextPath
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.301:INFO:oejs.Server:main: jetty-9.2.z-SNAPSHOT
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.327 WARNING: [1] org.glassfish.jersey.internal.inject.Providers.checkProviderRu
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.357:INFO:oejsh.ContextHandler:main: Started o.e.j.s.ServletContextHandler@26a52
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.357:INFO:oejs.ServerConnector:main: Started ServerConnector@69c6161d{HTTP/1.1}{
Dec 10 11:22:03 abacusatc launch.sh[12046]: 2018-12-10 11:22:03.358:INFO:oejs.Server:main: Started @1881ms

journalctl Logs:

– Logs begin at Sat 2018-12-08 21:16:08 IST, end at Mon 2018-12-10 11:18:41 IST
Dec 08 21:16:08 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:16:42 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:17:01 abacusatc CRON[27951]: pam_unix(cron:session): session opened fo
Dec 08 21:17:01 abacusatc CRON[27952]: (root) CMD ( cd / && run-parts --report
Dec 08 21:17:01 abacusatc CRON[27951]: pam_unix(cron:session): session closed fo
Dec 08 21:17:08 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:17:27 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:18:33 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:18:47 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:19:39 abacusatc sshd[27965]: Invalid user thkim from 51.38.68.193
Dec 08 21:19:39 abacusatc sshd[27965]: input_userauth_request: invalid user thki
Dec 08 21:19:39 abacusatc sshd[27965]: pam_unix(sshd:auth): check pass; user unk
Dec 08 21:19:39 abacusatc sshd[27965]: pam_unix(sshd:auth): authentication failu
Dec 08 21:19:41 abacusatc sshd[27965]: Failed password for invalid user thkim fr
Dec 08 21:19:42 abacusatc sshd[27965]: Received disconnect from 51.38.68.193 por
Dec 08 21:19:42 abacusatc sshd[27965]: Disconnected from 51.38.68.193 port 51776
Dec 08 21:19:45 abacusatc sshd[27967]: Connection closed by 36.67.106.109 port 3
Dec 08 21:20:16 abacusatc sshd[27969]: Invalid user teste from 201.21.115.162
Dec 08 21:20:16 abacusatc sshd[27969]: input_userauth_request: invalid user test
Dec 08 21:20:16 abacusatc sshd[27969]: pam_unix(sshd:auth): check pass; user unk
Dec 08 21:20:16 abacusatc sshd[27969]: pam_unix(sshd:auth): authentication failu
Dec 08 21:20:19 abacusatc sshd[27969]: Failed password for invalid user teste fr
lines 1-23…skipping…
– Logs begin at Sat 2018-12-08 21:16:08 IST, end at Mon 2018-12-10 11:18:41 IST
Dec 08 21:16:08 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:16:42 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:17:01 abacusatc CRON[27951]: pam_unix(cron:session): session opened fo
Dec 08 21:17:01 abacusatc CRON[27952]: (root) CMD ( cd / && run-parts --report
Dec 08 21:17:01 abacusatc CRON[27951]: pam_unix(cron:session): session closed fo
Dec 08 21:17:08 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:17:27 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:18:33 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:18:47 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:
Dec 08 21:19:39 abacusatc sshd[27965]: Invalid user thkim from 51.38.68.193
Dec 08 21:19:39 abacusatc sshd[27965]: input_userauth_request: invalid user thki
Dec 08 21:19:39 abacusatc sshd[27965]: pam_unix(sshd:auth): check pass; user unk
Dec 08 21:19:39 abacusatc sshd[27965]: pam_unix(sshd:auth): authentication failu
Dec 08 21:19:41 abacusatc sshd[27965]: Failed password for invalid user thkim fr
Dec 08 21:19:42 abacusatc sshd[27965]: Received disconnect from 51.38.68.193 por
Dec 08 21:19:42 abacusatc sshd[27965]: Disconnected from 51.38.68.193 port 51776
Dec 08 21:19:45 abacusatc sshd[27967]: Connection closed by 36.67.106.109 port 3
Dec 08 21:20:16 abacusatc sshd[27969]: Invalid user teste from 201.21.115.162
Dec 08 21:20:16 abacusatc sshd[27969]: input_userauth_request: invalid user test
Dec 08 21:20:16 abacusatc sshd[27969]: pam_unix(sshd:auth): check pass; user unk
Dec 08 21:20:16 abacusatc sshd[27969]: pam_unix(sshd:auth): authentication failu
Dec 08 21:20:19 abacusatc sshd[27969]: Failed password for invalid user teste fr
Dec 08 21:20:19 abacusatc sshd[27969]: Received disconnect from 201.21.115.162 p
lines 1-24…skipping…
– Logs begin at Sat 2018-12-08 21:16:08 IST, end at Mon 2018-12-10 11:18:41 IST. –
Dec 08 21:16:08 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=37.139.19.252 DST=220.225.233.83
Dec 08 21:16:42 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=212.92.100.178 DST=220.225.233.8
Dec 08 21:17:01 abacusatc CRON[27951]: pam_unix(cron:session): session opened for user root by (uid=0)
Dec 08 21:17:01 abacusatc CRON[27952]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 08 21:17:01 abacusatc CRON[27951]: pam_unix(cron:session): session closed for user root
Dec 08 21:17:08 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=185.176.26.57 DST=220.225.233.83
Dec 08 21:17:27 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=5.188.86.35 DST=220.225.233.83 L
Dec 08 21:18:33 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=5.188.86.35 DST=220.225.233.83 L
Dec 08 21:18:47 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=37.139.22.24 DST=220.225.233.83
Dec 08 21:19:39 abacusatc sshd[27965]: Invalid user thkim from 51.38.68.193
Dec 08 21:19:39 abacusatc sshd[27965]: input_userauth_request: invalid user thkim [preauth]
Dec 08 21:19:39 abacusatc sshd[27965]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 21:19:39 abacusatc sshd[27965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.68.193
Dec 08 21:19:41 abacusatc sshd[27965]: Failed password for invalid user thkim from 51.38.68.193 port 51776 ssh2
Dec 08 21:19:42 abacusatc sshd[27965]: Received disconnect from 51.38.68.193 port 51776:11: Bye Bye [preauth]
Dec 08 21:19:42 abacusatc sshd[27965]: Disconnected from 51.38.68.193 port 51776 [preauth]
Dec 08 21:19:45 abacusatc sshd[27967]: Connection closed by 36.67.106.109 port 34460 [preauth]
Dec 08 21:20:16 abacusatc sshd[27969]: Invalid user teste from 201.21.115.162
Dec 08 21:20:16 abacusatc sshd[27969]: input_userauth_request: invalid user teste [preauth]
Dec 08 21:20:16 abacusatc sshd[27969]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 21:20:16 abacusatc sshd[27969]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.21.115.162
Dec 08 21:20:19 abacusatc sshd[27969]: Failed password for invalid user teste from 201.21.115.162 port 40095 ssh2
Dec 08 21:20:19 abacusatc sshd[27969]: Received disconnect from 201.21.115.162 port 40095:11: Bye Bye [preauth]
Dec 08 21:20:19 abacusatc sshd[27969]: Disconnected from 201.21.115.162 port 40095 [preauth]
Dec 08 21:20:49 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=91.134.185.93 DST=220.225.233.83
Dec 08 21:21:40 abacusatc sshd[27977]: Invalid user solaris from 123.207.160.217
Dec 08 21:21:40 abacusatc sshd[27977]: input_userauth_request: invalid user solaris [preauth]
Dec 08 21:21:40 abacusatc sshd[27977]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 21:21:40 abacusatc sshd[27977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.207.160.217
Dec 08 21:21:42 abacusatc sshd[27977]: Failed password for invalid user solaris from 123.207.160.217 port 43732 ssh2
Dec 08 21:21:42 abacusatc sshd[27977]: Received disconnect from 123.207.160.217 port 43732:11: Bye Bye [preauth]
Dec 08 21:21:42 abacusatc sshd[27977]: Disconnected from 123.207.160.217 port 43732 [preauth]
Dec 08 21:21:52 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=31.184.195.108 DST=220.225.233.8
Dec 08 21:22:07 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=37.139.30.5 DST=220.225.233.83 L
Dec 08 21:22:18 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=109.248.9.12 DST=220.225.233.83
Dec 08 21:22:57 abacusatc kernel: [UFW BLOCK] IN=enp1s0 OUT= MAC=ec:8e:b5:d6:46:87:00:13:19:93:ad:40:08:00 SRC=5.188.86.35 DST=220.225.233.83 L
Dec 08 21:23:26 abacusatc sshd[27981]: Invalid user user0 from 113.197.54.213
Dec 08 21:23:26 abacusatc sshd[27981]: input_userauth_request: invalid user user0 [preauth]
Dec 08 21:23:26 abacusatc sshd[27981]: pam_unix(sshd:auth): check pass; user unknown
Dec 08 21:23:26 abacusatc sshd[27981]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.197.54.213
Dec 08 21:23:28 abacusatc sshd[27981]: Failed password for invalid user user0 from 113.197.54.213 port 43196 ssh2

Thanks,
Keerthi.


#34

@keerthireddyb
Looking at your logs, it seems that jibri-xorg has been given start command while it was already started, and hence this happened.

I recommend you to fresh install jibri by purging the current installed version.
Give your system a fresh start by cleaning all non-required packages and a clean restart.
Then install and configure jibri as per given manual.

Then follow the steps in my above post, and see if it works.

Also, the journalctl logs I requested are for jibri services. Use command journalctl -xe and scroll up to jibri and jibri-xorg process start-stop logs and get the logs if the process fails to start again. I need to see the reason for jibri and jibri-xorg to be unable to start.

Regards,
Dhruvin