[jitsi-users] Jirecon connection error

Carlo_Dimaggio · 2015-09-10 13:08:25 UTC

Hi guys,

I'm trying to use jirecon (as XMPP external component) but I'm in stuck
with the configuration. Unfortunately I don't find any useful
documentation about the installation.
Here my current configuration:

*Prosody:*
    [...]
    Component "jirecon.192.168.0.207"
        componentsecret = "jirecon123"

*Jitsi meet*
    [...]
    hosts: {
        [...]
        jirecon: 'jirecon.192.168.0.207',

*Jirecon*
/ jirecon.properties/
        org.jitsi.jirecon.XMPP_HOST=192.168.0.207
        org.jitsi.jirecon.XMPP_PORT=5347
        org.jitsi.jirecon.XMPP_USER=jirecon
        org.jitsi.jirecon.XMPP_PASS=jirecon123

I execute this command: component.sh --conf=jirecon.properties
--port=5347 --secret=jirecon123 --domain=192.168.0.207 --name=jirecon
--host=192.168.0.207

(Evenif the default configuration uses port 5222, I changed it to 5347
as the prosody external components should connect to this port

The*log*shows*:**

···

*

    set 10, 2015 3:01:05 PM org.jivesoftware.smack.PacketReader
    notifyConnectionError
    SEVERE: Closes the connection temporary
    stream:error (text)
            at
    org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:264)
            at
    org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
            at
    org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)

    set 10, 2015 3:01:20 PM org.jitsi.util.Logger info
    INFO: Failed to initialize Jirecon: Connection failed. No response
    from server.:
    set 10, 2015 3:01:20 PM org.jitsi.util.Logger info
    INFO: Un-initialize
    set 10, 2015 3:01:20 PM org.jitsi.util.Logger warn
    WARNING: Not initialized:
    java.lang.Throwable
            at org.jitsi.jirecon.TaskManager.uninit(TaskManager.java:166)
            at org.jitsi.jirecon.TaskManager.init(TaskManager.java:144)
            at
    org.jitsi.jirecon.xmppcomponent.XMPPComponent.preComponentStart(XMPPComponent.java:235)
            at
    org.xmpp.component.AbstractComponent.start(AbstractComponent.java:959)
            at
    org.jivesoftware.whack.ExternalComponent.start(ExternalComponent.java:372)
            at
    org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:234)
            at
    org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
            at
    org.jitsi.jirecon.xmppcomponent.ComponentLauncher.main(ComponentLauncher.java:141)

    Connection failed. No response from server.:
            at
    org.jivesoftware.smack.PacketReader.startup(PacketReader.java:123)
            at
    org.jivesoftware.smack.XMPPConnection.initConnection(XMPPConnection.java:573)
            at
    org.jivesoftware.smack.XMPPConnection.connectUsingConfiguration(XMPPConnection.java:532)
            at
    org.jivesoftware.smack.XMPPConnection.connect(XMPPConnection.java:968)
            at org.jitsi.jirecon.TaskManager.connect(TaskManager.java:269)
            at org.jitsi.jirecon.TaskManager.init(TaskManager.java:139)
            at
    org.jitsi.jirecon.xmppcomponent.XMPPComponent.preComponentStart(XMPPComponent.java:235)
            at
    org.xmpp.component.AbstractComponent.start(AbstractComponent.java:959)
            at
    org.jivesoftware.whack.ExternalComponent.start(ExternalComponent.java:372)
            at
    org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:234)
            at
    org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
            at
    org.jitsi.jirecon.xmppcomponent.ComponentLauncher.main(ComponentLauncher.java:141)
    set 10, 2015 3:01:20 PM org.jitsi.util.Logger info
    INFO: Jirecon component has been started successfully.**

(NOTE: jicofo uses port the same socket and it works. Indeed prosody
listen to 0.0.0.0:5347)

Someone can help me?

Regards,
Carlo

Boris_Grozev · 2015-09-10 14:03:57 UTC

Should be XMPP_PORT=5222, --port=5347 (the first is for client connections, the second for the component connection). I don't know if that's what causes the problem, though.

Boris

···

On 10/09/15 08:08, Carlo Dimaggio wrote:

Hi guys,

I'm trying to use jirecon (as XMPP external component) but I'm in stuck
with the configuration. Unfortunately I don't find any useful
documentation about the installation.
Here my current configuration:

*Prosody:*
     [...]
     Component "jirecon.192.168.0.207"
         componentsecret = "jirecon123"

*Jitsi meet*
     [...]
     hosts: {
         [...]
         jirecon: 'jirecon.192.168.0.207',

*Jirecon*
/jirecon.properties/
org.jitsi.jirecon.XMPP_HOST=192.168.0.207
org.jitsi.jirecon.XMPP_PORT=5347
org.jitsi.jirecon.XMPP_USER=jirecon
     org.jitsi.jirecon.XMPP_PASS=jirecon123

I execute this command: component.sh --conf=jirecon.properties
--port=5347 --secret=jirecon123 --domain=192.168.0.207 --name=jirecon
--host=192.168.0.207

(Evenif the default configuration uses port 5222, I changed it to 5347
as the prosody external components should connect to this port

Carlo_Dimaggio · 2015-09-10 16:45:15 UTC

Should be XMPP_PORT=5222, --port=5347 (the first is for client
connections, the second for the component connection). I don't know if
that's what causes the problem, though.

Boris

Hi Boris,
I have changed the XMPP_PORT to 5222 and created an account with
prosodyctl adduser jirecon@192.168.0.207.

Jirecon authenticates but now I have a strange error:

==> /var/log/prosody/prosody.log <==
Sep 10 18:24:46 c2s1d640c0 info Client connected
Sep 10 18:24:46 stanzarouter warn Unhandled c2s_unauthed stream
element or stanza: handshake; xmlns=jabber:component:accept: <handshake
xmlns='jabber:component:accept'>52750870bd78a9a04641806cc533dd0389ca35d3</handshake>
Sep 10 18:24:46 c2s1d640c0 info c2s stream for <127.0.0.1>
closed: unsupported-stanza-type
Sep 10 18:24:46 c2s1d640c0 info Client disconnected: connection
closed
Sep 10 18:24:47 c2s204a3d0 info Client connected
Sep 10 18:24:48 sasl warn Client is violating RFC 3920 (section
6.1, point 7).
Sep 10 18:24:48 c2s204a3d0 info Authenticated as
jirecon@192.168.0.207
*Sep 10 18:24:53 jirecon.192.168.0.207:component warn Component
not connected, bouncing error for: <iq id='1LKqF-3201' type='get'
to='jirecon.192.168.0.207'
from='focus@auth.192.168.0.207/focus22421293267'>**
**Sep 10 18:25:23 jirecon.192.168.0.207:component warn Component
not connected, bouncing error for: <iq id='1LKqF-3201' type='get'
to='jirecon.192.168.0.207'
from='focus@auth.192.168.0.207/focus22421293267'>**
**Sep 10 18:25:53 jirecon.192.168.0.207:component warn Component
not connected, bouncing error for: <iq id='1LKqF-3223' type='get'
to='jirecon.192.168.0.207'
from='focus@auth.192.168.0.207/focus22421293267'>*
Sep 10 18:26:01 c2s204a3d0 info c2s stream for
jirecon@192.168.0.207/Smack closed: session closed
Sep 10 18:26:01 c2s204a3d0 info Client disconnected: connection
closed
Sep 10 18:26:01 c2s1fb9ec0 info Client connected
Sep 10 18:26:01 stanzarouter warn Unhandled c2s_unauthed stream
element or stanza: handshake; xmlns=jabber:component:accept: <handshake
xmlns='jabber:component:accept'>581e96278ee725ead512d58f5a96f7f88b01139e</handshake>
Sep 10 18:26:01 c2s1fb9ec0 info c2s stream for <127.0.0.1>
closed: unsupported-stanza-type
Sep 10 18:26:01 c2s1fb9ec0 info Client disconnected: connection
closed

while the jirecon console shows:

[...]
INFO: failed to find jitsi-defaults.properties with class loader, will
continue without it.
set 10, 2015 6:24:47 PM org.jitsi.util.Logger info
INFO: Normal classloader
set 10, 2015 6:24:47 PM org.jitsi.util.Logger info
INFO: failed to find jitsi-default-overrides.properties with class
loader, will continue without it.
set 10, 2015 6:24:48 PM org.jitsi.util.Logger info
INFO: Logging in as XMPP client using: host=192.168.0.207; port=5222;
user=jirecon
set 10, 2015 6:24:48 PM org.jitsi.util.Logger info
INFO: Jirecon component has been started successfully.
set 10, 2015 6:26:01 PM org.jitsi.util.Logger info
INFO: Shutdown Jirecon component
set 10, 2015 6:26:01 PM org.jitsi.util.Logger info
INFO: Un-initialize
set 10, 2015 6:26:01 PM org.jitsi.util.Logger info
INFO: Closing the XMPP connection.

I don't know if it could be a bug or a misconfiguration (what is the
meaning of "...bouncing error for...".

C.

Boris_Grozev · 2015-09-10 18:35:03 UTC

This means that jirecon is not connected as a component.

Boris

···

On 10/09/15 11:45, Carlo Dimaggio wrote:

Should be XMPP_PORT=5222, --port=5347 (the first is for client
connections, the second for the component connection). I don't know if
that's what causes the problem, though.

Boris

Hi Boris,
I have changed the XMPP_PORT to 5222 and created an account with
prosodyctl adduser jirecon@192.168.0.207.

Jirecon authenticates but now I have a strange error:

==> /var/log/prosody/prosody.log <==
Sep 10 18:24:46 c2s1d640c0 info Client connected
Sep 10 18:24:46 stanzarouter warn Unhandled c2s_unauthed stream
element or stanza: handshake; xmlns=jabber:component:accept: <handshake
xmlns='jabber:component:accept'>52750870bd78a9a04641806cc533dd0389ca35d3</handshake>
Sep 10 18:24:46 c2s1d640c0 info c2s stream for <127.0.0.1>
closed: unsupported-stanza-type
Sep 10 18:24:46 c2s1d640c0 info Client disconnected: connection
closed
Sep 10 18:24:47 c2s204a3d0 info Client connected
Sep 10 18:24:48 sasl warn Client is violating RFC 3920 (section
6.1, point 7).
Sep 10 18:24:48 c2s204a3d0 info Authenticated as
jirecon@192.168.0.207
*Sep 10 18:24:53 jirecon.192.168.0.207:component warn Component not
connected, bouncing error for: <iq id='1LKqF-3201' type='get'
to='jirecon.192.168.0.207'
from='focus@auth.192.168.0.207/focus22421293267'>**
**Sep 10 18:25:23 jirecon.192.168.0.207:component warn Component not
connected, bouncing error for: <iq id='1LKqF-3201' type='get'
to='jirecon.192.168.0.207'
from='focus@auth.192.168.0.207/focus22421293267'>**
**Sep 10 18:25:53 jirecon.192.168.0.207:component warn Component not
connected, bouncing error for: <iq id='1LKqF-3223' type='get'
to='jirecon.192.168.0.207'
from='focus@auth.192.168.0.207/focus22421293267'>*
Sep 10 18:26:01 c2s204a3d0 info c2s stream for
jirecon@192.168.0.207/Smack closed: session closed
Sep 10 18:26:01 c2s204a3d0 info Client disconnected: connection
closed
Sep 10 18:26:01 c2s1fb9ec0 info Client connected
Sep 10 18:26:01 stanzarouter warn Unhandled c2s_unauthed stream
element or stanza: handshake; xmlns=jabber:component:accept: <handshake
xmlns='jabber:component:accept'>581e96278ee725ead512d58f5a96f7f88b01139e</handshake>
Sep 10 18:26:01 c2s1fb9ec0 info c2s stream for <127.0.0.1>
closed: unsupported-stanza-type
Sep 10 18:26:01 c2s1fb9ec0 info Client disconnected: connection
closed

Carlo_Dimaggio · 2015-09-11 13:11:18 UTC

Hi Boris,

true. I had a misconfiguration in the jirecon.properties file.
Thank you.

Regards,
Carlo

···

Il 10/09/15 20:35, Boris Grozev ha scritto:

This means that jirecon is not connected as a component.

Boris