How to know jicofo is working?

Hi, I try to start jicofo by this command line:

./jicofo.sh --domain=jitsi.exmaple.com --secret=focus_secret --user_domain=auth.jitsi.example.com --user_name=focus --user_password=focuspassword

there is no error logs after started but I don’t know how to sure it works or not. I configured jitsi-meet to connect to focus.jitsi.example.com (the prosody module works as well) but it said that CONFERENCE FAILED: conference.focusDisconnected focus.jitsi.example.com. Can someone tell me what’s error and how to check is jicofo working or not?

Thanks

What’s in the jicofo logs?

Thanks a lot @saghul

Here is log

mod_bosh                                  debug	BOSH body open (sid: b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e)
mod_bosh                                  debug	BOSH stanza received: <iq id='93cfcc36-ed6b-4e18-bb2b-2f10293aead9:sendIQ' type='get' to='jitsi.example.com'>

boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	Received[c2s]: <iq id='93cfcc36-ed6b-4e18-bb2b-2f10293aead9:sendIQ' type='get' to='jitsi.example.com'>
stanzarouter                              debug	Unhandled c2s stanza: iq; xmlns=urn:xmpp:extdisco:2
mod_bosh                                  debug	BOSH stanza received: <iq id='5e604192-3e5a-4d01-8db8-a943042e566a:sendIQ' type='get' to='jitsi.example.com' from='88128040-4f0c-4722-a4ff-15b51dc484fe@jitsi.example.com/1677e3d3-df61-47d2-857b-e6d66a4c3b05'>

boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	Received[c2s]: <iq id='5e604192-3e5a-4d01-8db8-a943042e566a:sendIQ' type='get' to='jitsi.example.com' from='88128040-4f0c-4722-a4ff-15b51dc484fe@jitsi.example.com/1677e3d3-df61-47d2-857b-e6d66a4c3b05'>
mod_bosh                                  debug	BOSH stanza received: <iq id='104a7b41-a508-4045-ae7d-e049b7a9ac17:sendIQ' type='set' to='focus.jitsi.example.com'>

boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	Received[c2s]: <iq id='104a7b41-a508-4045-ae7d-e049b7a9ac17:sendIQ' type='set' to='focus.jitsi.example.com'>
focus.jitsi.example.com:component         warn	Component not connected, bouncing error for: <iq id='104a7b41-a508-4045-ae7d-e049b7a9ac17:sendIQ' type='set' to='focus.jitsi.example.com' from='88128040-4f0c-4722-a4ff-15b51dc484fe@jitsi.example.com/1677e3d3-df61-47d2-857b-e6d66a4c3b05'>
mod_bosh                                  debug	We have an open request, so sending on that
mod_bosh                                  debug	Request destroyed: table: 0x7fdc824689e0
boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	BOSH session marked as inactive (for 60s)
socket                                    debug	server.lua: closed client handler and removed socket from list
mod_bosh                                  debug	Session b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e has 0 out of 1 requests open
mod_bosh                                  debug	and there are 0 things in the send_buffer:
socket                                    debug	server.lua: accepted new client connection from 127.0.0.1:49628 to 5280
http.server                               debug	Firing event: POST jitsi.example.com/http-bind
mod_bosh                                  debug	Handling new request table: 0x7fdc82474310: <body rid="3963708889" sid="b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e" xmlns="http://jabber.org/protocol/httpbind"><iq id="beefbd8c-382c-4f2f-9f8f-f1a46404e974:sendIQ" to="jitsi.example.com" type="get" xmlns="jabber:client"><services xmlns="urn:xmpp:extdisco:1"/></iq></body>
----------
mod_bosh                                  debug	BOSH body open (sid: b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e)
mod_bosh                                  debug	BOSH stanza received: <iq id='beefbd8c-382c-4f2f-9f8f-f1a46404e974:sendIQ' type='get' to='jitsi.example.com'>

boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	Received[c2s]: <iq id='beefbd8c-382c-4f2f-9f8f-f1a46404e974:sendIQ' type='get' to='jitsi.example.com'>
stanzarouter                              debug	Unhandled c2s stanza: iq; xmlns=urn:xmpp:extdisco:1
mod_bosh                                  debug	We have an open request, so sending on that
mod_bosh                                  debug	Request destroyed: table: 0x7fdc824748a0
boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	BOSH session marked as inactive (for 60s)
socket                                    debug	server.lua: closed client handler and removed socket from list
mod_bosh                                  debug	Session b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e has 0 out of 1 requests open
mod_bosh                                  debug	and there are 0 things in the send_buffer:
socket                                    debug	server.lua: accepted new client connection from ::1:49629 to 5280
http.server                               debug	Firing event: POST jitsi.example.com/http-bind
mod_bosh                                  debug	Handling new request table: 0x7fdc820ea0d0: <body rid="3963708890" sid="b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e" xmlns="http://jabber.org/protocol/httpbind"/>
----------
mod_bosh                                  debug	BOSH body open (sid: b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e)
mod_bosh                                  debug	Session b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e has 1 out of 1 requests open
mod_bosh                                  debug	and there are 0 things in the send_buffer:
mod_bosh                                  debug	Have nothing to say, so leaving request unanswered for now
socket                                    debug	server.lua: accepted new client connection from 127.0.0.1:49631 to 5280
http.server                               debug	Firing event: POST jitsi.example.com/http-bind
mod_bosh                                  debug	Handling new request table: 0x7fdc7feb6ca0: <body rid="3963708891" sid="b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e" xmlns="http://jabber.org/protocol/httpbind"><iq id="426fc964-8ec7-452b-82ef-2913f4c54d52:sendIQ" to="focus.jitsi.example.com" type="set" xmlns="jabber:client"><conference machine-uid="4321508c61dfd6dba0253705f9e98470" room="megazone@conference.jitsi.example.com" xmlns="http://jitsi.org/protocol/focus"><property name="disableRtx" value="false"/></conference></iq></body>
----------
mod_bosh                                  debug	BOSH body open (sid: b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e)
mod_bosh                                  debug	BOSH stanza received: <iq id='426fc964-8ec7-452b-82ef-2913f4c54d52:sendIQ' type='set' to='focus.jitsi.example.com'>

boshb5f27b7a-fbe3-4b50-9697-23f83e6b9a6e  debug	Received[c2s]: <iq id='426fc964-8ec7-452b-82ef-2913f4c54d52:sendIQ' type='set' to='focus.jitsi.example.com'>
focus.jitsi.example.com:component         warn	Component not connected, bouncing error for: <iq id='426fc964-8ec7-452b-82ef-2913f4c54d52:sendIQ' type='set' to='focus.jitsi.example.com' from='88128040-4f0c-4722-a4ff-15b51dc484fe@jitsi.example.com/1677e3d3-df61-47d2-857b-e6d66a4c3b05'>
mod_bosh                                  debug	We have an open request, so sending on that
mod_bosh                                  debug	Request destroyed: table: 0x7fdc820ea5c0
socket                                    debug	server.lua: closed client handler and removed socket from list
mod_bosh                                  debug	Session b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e has 1 out of 1 requests open
mod_bosh                                  debug	and there are 0 things in the send_buffer:
mod_bosh                                  debug	Have nothing to say, so leaving request unanswered for now
socket                                    debug	server.lua: accepted new client connection from ::1:49632 to 5280
http.server                               debug	Firing event: POST jitsi.example.com/http-bind
mod_bosh                                  debug	Handling new request table: 0x7fdc82511f50: <body rid="3963708892" sid="b5f27b7a-fbe3-4b50-9697-23f83e6b9a6e" type="terminate" xmlns="http://jabber.org/protocol/httpbind"><presence type="unavailable" xmlns="jabber:client"/></body>

I guess the problem is here but I don’t know how to fix it. I followed manual installation (here: Self-Hosting Guide - Manual installation · Jitsi Meet Handbook)

That manual is pretty outdated … for example, jicofo no longer supports to be component. Use the quick install guide to avoid the headaches. Make sure it works then you can reuse existing config and run from source if this is your goal.

@damencho do you mean this documentation Self-Hosting Guide - Debian/Ubuntu server · Jitsi Meet Handbook, right? In fact, I want to install it on my development environment. Is there any developer guide that I can use to install jitsi-meet and debug it?

Use as an example. Copy-paste will not work

If you want to just debug the code you can just do make dev locally and do that, that will use alpha jitsi net as a backend loading configs and some resources from there, but the code going in appbundle will be coming from the local source code and you can debug it …

Thanks @emrah. However, can you explain further more?

Hi @damencho, so I should remove component configuration in the prosody and only run make dev in jicofo and jitsi-meet. That’s all, right?

One more thing, the list of arguments of running command line still the same, right?

The thing I wrote, you don’t need a deployment and VM and you will be debugging jitsi-meet.

It is just make dev in jitsi-meet repo, of course you need npm install before that.

Thanks a lot @damencho but it seems like make dev in jitsi-meet repo is only debug for jitsi-meet, not include jicofo.

Is there any way that I can debug for jitsi-meet and jicofo and jvb together (all modules in debug mode)?

nope, you can checkout locally jicofo and jvb and stop jicofo on your dev environment and start the one locally making it connect to your deployment …

Sorry @damencho, can you explain further more above suggestion?

One more thing is which branch of codes should I use? I am using master branch of all those repos (jicofo, jitsi-meet, jitsi-videobridge)

First make sure you have a working deployment on a vm.