Failed to start Jibri Process

I installed jitsi-meet,implemented secure domain and integrated etherpad.
Then I tried to install jibri on same(with jitsi meet server) machine (ubuntu 18.04)
I followed the jibri original tutorial and git documentation but ended up with pathetic failure :slight_smile:


I dont even know what is wrong or which part of the installation causes this. In jibri log :

2019-12-07 12:03:05.742 INFO: [1] org.jitsi.jibri.Main.main() Jibri run with args [--config, /etc/jitsi/jibri/config.json]
2019-12-07 12:03:05.756 INFO: [1] org.jitsi.jibri.Main.main() Using config file /etc/jitsi/jibri/config.json
2019-12-07 12:03:05.756 INFO: [1] org.jitsi.jibri.Main.main() Using port 3333 for internal HTTP API
2019-12-07 12:03:05.756 INFO: [1] org.jitsi.jibri.Main.main() Using port 2222 for the HTTP API

Jibri config file :

{
    // 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": [
                "192.168.0.149"
            ],
            // The xmpp domain we'll connect to on the XMPP server
            "xmpp_domain": "192.168.0.149",
            // Jibri will login to the xmpp server as a privileged user 
            "control_login": {
                // The domain to use for logging in
                "domain": "auth.192.168.0.149",
                // 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.192.168.0.149",
                "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.192.168.0.149",
                "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"
        }
    ]
}

is there can be anything wrong with “chrome version”? or with “same/separate machine” or “stable/unstable” ? if so plz tell me how to get rid of this .
I am also getting this error during “apt-get update”


my current openjdk version is 11.
@damencho @saghul
please help me to find out the problem and thanx in advance :heart:

I think you need to be using openjdk version 8 for jibri to work properly.

I updated while trying… before that it was 8… still wasn’t working

Now having status=203 and not even any info in jibri log about it


@damencho plz help anyone understanding the problem
I followed the youtube tutorial and also checked git instructions.
Thanx in advance :heart:

So your jibri logs are empty?
What does “journalctl -xe” says?

Thanx for the reply.
I am not familiar with that command but it shows :

ডিসেম্বর 09 18:16:41 Fuji org.gnome.Shell.desktop[1636]: [1985:863:1209/181641.165777:ERROR:webrtc_event_log_manager_rem
ডিসেম্বর 09 18:16:48 Fuji polkitd(authority=local)[949]: Operator of unix-session:2 successfully authenticated as unix-u
ডিসেম্বর 09 18:16:50 Fuji gedit[1173]: The specified location is not mounted
ডিসেম্বর 09 18:16:53 Fuji polkitd(authority=local)[949]: Operator of unix-session:2 successfully authenticated as unix-u
ডিসেম্বর 09 18:16:55 Fuji slack.desktop[3682]: [12/09/19, 18:16:55:201] info: [DND] (TK00RGSSZ) Checking for changes in 
ডিসেম্বর 09 18:16:55 Fuji slack.desktop[3682]: [12/09/19, 18:16:55:201] info: [DND] (TK00RGSSZ) Will check for changes i
ডিসেম্বর 09 18:17:01 Fuji CRON[1271]: pam_unix(cron:session): session opened for user root by (uid=0)
ডিসেম্বর 09 18:17:01 Fuji CRON[1275]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
ডিসেম্বর 09 18:17:01 Fuji CRON[1271]: pam_unix(cron:session): session closed for user root
ডিসেম্বর 09 18:17:36 Fuji gedit[1519]: The specified location is not mounted
ডিসেম্বর 09 18:17:36 Fuji org.gnome.Shell.desktop[1636]: [1985:31825:1209/181736.408368:ERROR:webrtc_event_log_manager_r
ডিসেম্বর 09 18:17:36 Fuji org.gnome.Shell.desktop[1636]: [1985:31825:1209/181736.449363:ERROR:webrtc_event_log_manager_r
ডিসেম্বর 09 18:17:39 Fuji polkitd(authority=local)[949]: Operator of unix-session:2 successfully authenticated as unix-u
ডিসেম্বর 09 18:17:41 Fuji org.gnome.Shell.desktop[1636]: [OpenH264] this = 0x0x373f933812d0, Warning:Change QP Range fro
ডিসেম্বর 09 18:17:41 Fuji org.gnome.Shell.desktop[1636]: [OpenH264] this = 0x0x373f933812d0, Warning:Change QP Range fro
ডিসেম্বর 09 18:17:41 Fuji org.gnome.Shell.desktop[1636]: [OpenH264] this = 0x0x373f933812d0, Warning:Change QP Range fro
ডিসেম্বর 09 18:17:41 Fuji org.gnome.Shell.desktop[1636]: [1985:31825:1209/181741.869146:ERROR:webrtc_event_log_manager_r
ডিসেম্বর 09 18:17:43 Fuji slack.desktop[3682]: [12/09/19, 18:17:43:639] info: [CHECK-FOR-OLD-IMS] (TK00RGSSZ) Within lim
ডিসেম্বর 09 18:17:43 Fuji org.gnome.Shell.desktop[1636]: [OpenH264] this = 0x0x373f933812d0, Warning:Actual input framer
ডিসেম্বর 09 18:17:45 Fuji org.gnome.Shell.desktop[1636]: [1985:31825:1209/181745.326282:ERROR:webrtc_event_log_manager_r
ডিসেম্বর 09 18:17:45 Fuji org.gnome.Shell.desktop[1636]: [1985:31825:1209/181745.725059:ERROR:webrtc_event_log_manager_r
ডিসেম্বর 09 18:17:55 Fuji org.gnome.Shell.desktop[1636]: [1985:31825:1209/181755.459530:ERROR:webrtc_event_log_manager_r
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.151418:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.314756:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.318866:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.319692:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.319807:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.319871:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.325711:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:18 Fuji org.gnome.Shell.desktop[1636]: [2023:2039:1209/181818.346303:ERROR:ssl_client_socket_impl.cc(9
ডিসেম্বর 09 18:18:28 Fuji org.gnome.Shell.desktop[1636]: [2019:2019:1209/181828.128479:ERROR:shared_image_manager.cc(191
ডিসেম্বর 09 18:18:28 Fuji org.gnome.Shell.desktop[1636]: [2019:2019:1209/181828.128699:ERROR:shared_image_manager.cc(191

Restart jibri and then execute it.

here :

-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Automatic restarting of the unit jibri-icewm.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: Stopped Jibri Window Manager.
-- Subject: Unit jibri-icewm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-icewm.service has finished shutting down.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: Stopped Jibri Xorg Process.
-- Subject: Unit jibri-xorg.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-xorg.service has finished shutting down.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: jibri-xorg.service: Start request repeated too quickly.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: jibri-xorg.service: Failed with result 'exit-code'.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: Failed to start Jibri Xorg Process.
-- Subject: Unit jibri-xorg.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-xorg.service has failed.
-- 
-- The result is RESULT.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: Dependency failed for Jibri Window Manager.
-- Subject: Unit jibri-icewm.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-icewm.service has failed.
-- 
-- The result is RESULT.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: jibri-icewm.service: Job jibri-icewm.service/start failed with result 'dependency'.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: Stopped Jibri Process.
-- Subject: Unit jibri.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri.service has finished shutting down.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: jibri.service: Start request repeated too quickly.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: jibri.service: Failed with result 'exit-code'.
ডিসেম্বর 09 19:02:48 Fuji systemd[1]: Failed to start Jibri Process.
-- Subject: Unit jibri.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri.service has failed.
-- 
-- The result is RESULT.
ডিসেম্বর 09 19:02:59 Fuji org.gnome.Shell.desktop[1636]: [1985:9038:1209/190259.523040:ERROR:webrtc_event_log_manager_remote.cc(408)] Session ID already set.
lines 1795-1848/1848 (END)

:slight_smile:

Here is your error. Now check /tmp/xorg.log or /var/log/jitsi/xorg.log, not sure about the name and location. And see why it fails and try to fix it.

Are you running this on a machine with already running xorg server?

Actually I am not sure about that… I installed jitsi meet in my PC, integrated secure domain and etherpad
:sleepy: can this be a issue? and where can I find the actual description of exit codes?

dpkg --list shows this but I m not sure what these are :

ii  xserver-xorg   1:7.7+19ubun amd64        X.Org X server
ii  xserver-xorg-c 2:1.19.6-1ub amd64        Xorg X server - core server
ii  xserver-xorg-i 1:7.7+19ubun amd64        X.Org X server -- input driver me
ii  xserver-xorg-i 0.27.1-1     amd64        X.Org X server -- libinput input 
ii  xserver-xorg-i 1:1.4.1-1bui amd64        X.Org X server -- void input driv
ii  xserver-xorg-i 1:0.36.1-0ub amd64        X.Org X server -- Wacom input dri
ii  xserver-xorg-l 2:1.19.6-1ub amd64        setuid root Xorg server wrapper
ii  xserver-xorg-v 1:7.7+19ubun amd64        X.Org X server -- output driver m
ii  xserver-xorg-v 18.0.1-1     amd64        X.Org X server -- AMDGPU display 
ii  xserver-xorg-v 1:18.0.1-1   amd64        X.Org X server -- AMD/ATI display
ii  xserver-xorg-v 1:0.3.8-1bui amd64        X.Org X server -- dummy display d
ii  xserver-xorg-v 1:0.4.4-1bui amd64        X.Org X server -- fbdev display d
ii  xserver-xorg-v 2:2.99.917+g amd64        X.Org X server -- Intel i8xx, i9x
ii  xserver-xorg-v 1:1.0.15-2   amd64        X.Org X server -- Nouveau display
ii  xserver-xorg-v 0.1.5-2build amd64        X.Org X server -- QXL display dri
ii  xserver-xorg-v 1:18.0.1-1   amd64        X.Org X server -- AMD/ATI Radeon 
ii  xserver-xorg-v 1:2.3.4-1bui amd64        X.Org X server -- VESA display dr
ii  xserver-xorg-v 1:13.2.1-1bu amd64        X.Org X server -- VMware display 

may be when I tried multiple times this happened.
@damencho can u plz tell me how I should proceed for jibri now? :worried:

I just ran this command as it was said in git instruction for jibri, now I see ‘xorg server’ here.

sudo apt-get install default-jre-headless ffmpeg curl alsa-utils icewm xdotool xserver-xorg-input-void xserver-xorg-video-dummy

plz help
@damencho @saghul

What instructions are you following and in what step did you get stuck?

I followed the git instruction but my jibri process isnt even running :worried:

What is the output of you start it manually?

after following the instructions I have this… after checking

later found out that jibri xorg process isnt starting but i m not familiar solving this issue

Check the output of the service with journalctl -xe

@saghul

-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has begun starting up.
ডিসেম্বর 14 09:01:01 Fuji dbus-daemon[1510]: [session uid=1000 pid=1510] Successf
ডিসেম্বর 14 09:01:01 Fuji systemd[1484]: Started GNOME Terminal Server.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local s
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local s
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local s
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local s
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: Failed to load snap icon: local s
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: Failed to load snap icon: local s
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_path_get_basename: assertion 'f
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_regex_match_full: assertion 'st
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_path_get_basename: assertion 'f
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_regex_match_full: assertion 'st
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: Failed to load snap icon: local s
lines 1759-1781/1781 (END)
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has begun starting up.
ডিসেম্বর 14 09:01:01 Fuji dbus-daemon[1510]: [session uid=1000 pid=1510] Successfully activated service 'org.gnome.Terminal'
ডিসেম্বর 14 09:01:01 Fuji systemd[1484]: Started GNOME Terminal Server.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
ডিসেম্বর 14 09:01:05 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_path_get_basename: assertion 'file_name != NULL' failed
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_regex_match_full: assertion 'string != NULL' failed
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_path_get_basename: assertion 'file_name != NULL' failed
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: g_regex_match_full: assertion 'string != NULL' failed
ডিসেম্বর 14 09:01:06 Fuji gnome-software[2937]: Failed to load snap icon: local snap has no icon
~

anything wrong? :woozy_face:
after restarting jibri and then after that command :

ডিসেম্বর 14 09:39:23 Fuji systemd[1]: jibri-icewm.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Automatic restarting of the unit jibri-icewm.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: Stopped Jibri Window Manager.
-- Subject: Unit jibri-icewm.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-icewm.service has finished shutting down.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: Stopped Jibri Process.
-- Subject: Unit jibri.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri.service has finished shutting down.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: jibri.service: Start request repeated too quickly.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: jibri.service: Failed with result 'exit-code'.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: Failed to start Jibri Process.
-- Subject: Unit jibri.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri.service has failed.
-- 
-- The result is RESULT.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: Stopped Jibri Xorg Process.
-- Subject: Unit jibri-xorg.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-xorg.service has finished shutting down.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: jibri-xorg.service: Start request repeated too quickly.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: jibri-xorg.service: Failed with result 'exit-code'.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: Failed to start Jibri Xorg Process.
-- Subject: Unit jibri-xorg.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-xorg.service has failed.
-- 
-- The result is RESULT.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: Dependency failed for Jibri Window Manager.
-- Subject: Unit jibri-icewm.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit jibri-icewm.service has failed.
-- 
-- The result is RESULT.
ডিসেম্বর 14 09:39:23 Fuji systemd[1]: jibri-icewm.service: Job jibri-icewm.service/start failed with result 'dependency'.

Wait, is this server a full Ubuntu desktop installation?