[jitsi-dev] Redirection when connecting from a mobile phone


#21

Hi, Saúl.

Perfect. So in the case of compiling the source code for jitsi-meet, if
I understood correctly, I should install jitsi-meet and
jitsi-meet-prosody (in addition to jicofo and jitsi-videobridge). It is
right?

Just jitsi-meet should be ok, the rest you should already have them.

Ah, then I think this would coincide with the procedure suggested by
Buddhika, right?

I haven’t seen his replies, sorry.

No problem. I was referring to this reply:

http://lists.jitsi.org/pipermail/dev/2017-June/033692.html

From what I see, the other packages would be installed as dependencies:

------------------------------------------------------------------------
root@conference:~# aptitude show jitsi-meet
[...]
Depends: jitsi-videobridge (= 961-1), jicofo (= 1.0-357-1),
jitsi-meet-web (= 1.0.2025-1), jitsi-meet-web-config (= 1.0.2025-1),
jitsi-meet-prosody (= 1.0.2025-1)
------------------------------------------------------------------------

I think in this case we would have redundant code installed, because we
have the jitsi-meet version of the package and the version we compiled
with the code of https://github.com/jitsi/jitsi-meet, right?

If you build a Debian package, it will replace the installed one, if you
just build the code you have 2 choices:

- copy your changes over the existing files
- install it elsewhere and have nguni look there

I think that's why Buddhika said that he changed on Nginx the web
directory for the one used by the compiled application.

This would work for the second option, yes.

I do understand. Could you please tell me how to build the Debian
package? I've made some attempts but I could not get it.

Thanks for your reply.

Kind regards,
Daniel

···

On 14/06/17 16:45, Saúl Ibarra Corretgé wrote:


#22

Hi,

To create a debian package this should work:
$ cd jitsi-meet
$ npm install
$ make
$ dpkg-buildpackage -A -rfakeroot -us -uc

Regards
damencho

···

On Wed, Jun 21, 2017 at 1:52 PM, Daniel <daniel-listas@gmx.net> wrote:

Hi, Saúl.

On 14/06/17 16:45, Saúl Ibarra Corretgé wrote:

Perfect. So in the case of compiling the source code for jitsi-meet, if
I understood correctly, I should install jitsi-meet and
jitsi-meet-prosody (in addition to jicofo and jitsi-videobridge). It is
right?

Just jitsi-meet should be ok, the rest you should already have them.

Ah, then I think this would coincide with the procedure suggested by
Buddhika, right?

I haven’t seen his replies, sorry.

No problem. I was referring to this reply:

http://lists.jitsi.org/pipermail/dev/2017-June/033692.html

From what I see, the other packages would be installed as dependencies:

------------------------------------------------------------------------
root@conference:~# aptitude show jitsi-meet
[...]
Depends: jitsi-videobridge (= 961-1), jicofo (= 1.0-357-1),
jitsi-meet-web (= 1.0.2025-1), jitsi-meet-web-config (= 1.0.2025-1),
jitsi-meet-prosody (= 1.0.2025-1)
------------------------------------------------------------------------

I think in this case we would have redundant code installed, because we
have the jitsi-meet version of the package and the version we compiled
with the code of https://github.com/jitsi/jitsi-meet, right?

If you build a Debian package, it will replace the installed one, if you
just build the code you have 2 choices:

- copy your changes over the existing files
- install it elsewhere and have nguni look there

I think that's why Buddhika said that he changed on Nginx the web
directory for the one used by the compiled application.

This would work for the second option, yes.

I do understand. Could you please tell me how to build the Debian
package? I've made some attempts but I could not get it.

Thanks for your reply.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#23

Hi,

Hi, Damian.

Thanks for your reply.

To create a debian package this should work:
$ cd jitsi-meet
$ npm install
$ make
$ dpkg-buildpackage -A -rfakeroot -us -uc

I think it's failing the 'npn' step. Is it possible? Below the output I
am getting:

···

On 21/06/17 16:47, Damian Minkov wrote:

-----------------------------------------------------------------------
root@testing:/usr/src/jitsi-meet# npm install
npm WARN deprecated strophe@1.2.4: This package is no longer maintained;
use 'strophe.js' instead.
npm ERR! 404 Not Found
npm ERR! 404
npm ERR! 404 'atlaskit/button' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404 It was specified as a dependency of 'jitsi-meet'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Linux 3.16.0-4-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /usr/src/jitsi-meet
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code E404
npm WARN deprecated jssha@1.5.0: jsSHA versions < v2.0.0 will no longer
receive features
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/src/jitsi-meet/npm-debug.log
npm ERR! not ok code 0
-----------------------------------------------------------------------

Previously I installed these dependencies as suggested in
https://github.com/jitsi/jitsi-meet/blob/master/README.md:

root@testing:~# aptitude install npm nodejs-legacy

Kind regards,
Daniel


#24

Hi,

···

On Wed, Jun 21, 2017 at 3:12 PM, Daniel <daniel-listas@gmx.net> wrote:

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.
I think the LTS versions are: node v6.11.0 + npm v3.10.10

Regards
damencho


#25

Hi again, Damian.

npm-debug.log (242 KB)

···

On 21/06/17 17:12, Daniel wrote:

To create a debian package this should work:
$ cd jitsi-meet
$ npm install
$ make
$ dpkg-buildpackage -A -rfakeroot -us -uc

I think it's failing the 'npn' step. Is it possible? Below the output I
am getting:

-----------------------------------------------------------------------
root@testing:/usr/src/jitsi-meet# npm install
npm WARN deprecated strophe@1.2.4: This package is no longer maintained;
use 'strophe.js' instead.
(...)
npm ERR! Additional logging details can be found in:
npm ERR! /usr/src/jitsi-meet/npm-debug.log
npm ERR! not ok code 0
-----------------------------------------------------------------------

I also attached the log generated by npm
(/usr/src/jitsi-meet/npm-debug.log) in the case that this provides
additional information.

Thanks in advance.

Kind regards,
Daniel


#26

Hi,

Hi, Damian.

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

Thanks for your reply.

Kind regards,
Daniel

[1]
https://packages.debian.org/search?keywords=npm&searchon=names&suite=all&section=all
[2]
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

···

On 21/06/17 18:07, Damian Minkov wrote:

On Wed, Jun 21, 2017 at 3:12 PM, Daniel <daniel-listas@gmx.net> wrote:


#27

Hi,

No idea about the 4x version, you can try. When building jitsi-meet
packages we are using the node coming from nodejs.org, the repos you
already spotted.

Cheers
damencho

···

On Wed, Jun 21, 2017 at 5:34 PM, Daniel <daniel-listas@gmx.net> wrote:

On 21/06/17 18:07, Damian Minkov wrote:

Hi,

Hi, Damian.

On Wed, Jun 21, 2017 at 3:12 PM, Daniel <daniel-listas@gmx.net> wrote:

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

Thanks for your reply.

Kind regards,
Daniel

[1]
https://packages.debian.org/search?keywords=npm&searchon=names&suite=all&section=all
[2]
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#28

Hi,

Hi, Damian.

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

I suggest you use that repo. Nodejs move much faster than the Debian release cycle, so you’re better off using it.

Cheers,

···

On Jun 21, 2017, at 17:34, Daniel <daniel-listas@gmx.net> wrote:
On 21/06/17 18:07, Damian Minkov wrote:

On Wed, Jun 21, 2017 at 3:12 PM, Daniel <daniel-listas@gmx.net> wrote:

Thanks for your reply.

Kind regards,
Daniel

[1]
https://packages.debian.org/search?keywords=npm&searchon=names&suite=all&section=all
[2]
https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
Saúl


#29

Hi Saúl/Damian.

···

On 22/06/17 10:13, Saúl Ibarra Corretgé wrote:

On Wed, Jun 21, 2017 at 3:12 PM, Daniel <daniel-listas@gmx.net> wrote:

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

I suggest you use that repo. Nodejs move much faster than the Debian
release cycle, so you’re better off using it.

Thank you both for responding. I used the packages of node.org and it
seems that the generation of the packages in Jessie has been successful,
although I have some doubts that I would like to ask you.

The generated packages were:

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

---------------------------------------------------------------------
Jicofo 2017-06-22 11:28:13.692 GRAVE: [6416]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:13.694 GRAVE: [6420]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:13.694 GRAVE: [6415]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.write(BufferedWriter.java:221)
        at java.io.Writer.write(Writer.java:157)
        at
org.jivesoftware.smack.PacketWriter.openStream(PacketWriter.java:261)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:190)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:14.549 GRAVE: [6398]
util.UtilActivator.uncaughtException().119 An uncaught exception
occurred in thread=Thread[Smack Reconnection Manager,5,main] and message
was: null
java.lang.IllegalThreadStateException
        at java.lang.Thread.start(Thread.java:708)
        at
org.jivesoftware.smack.PacketReader.startup(PacketReader.java:106)
        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.jivesoftware.smack.ReconnectionManager$2.run(ReconnectionManager.java:133)
Jicofo 2017-06-22 11:28:14.698 GRAVE: [6435]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:14.708 GRAVE: [6437]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:14.712 GRAVE: [6429]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:15.533 GRAVE: [6504]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.net.SocketException: Tubería rota (Write failed)
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
        at java.io.BufferedWriter.flush(BufferedWriter.java:254)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:15.550 GRAVE: [6508]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:15.593 GRAVE: [29]
org.jitsi.meet.ComponentMain.call().278 host-unknown, host:localhost,
port:5347
org.xmpp.component.ComponentException: host-unknown
        at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
        at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
        at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
        at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
        at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
        at
org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
Jicofo 2017-06-22 11:28:15.684 GRAVE: [6505]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:15.699 GRAVE: [6509]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:16.553 GRAVE: [6512]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:16.559 GRAVE: [6510]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:16.688 GRAVE: [6513]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:16.693 GRAVE: [6517]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:16.696 GRAVE: [6516]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.write(BufferedWriter.java:221)
        at java.io.Writer.write(Writer.java:157)
        at
org.jivesoftware.smack.PacketWriter.openStream(PacketWriter.java:261)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:190)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:17.551 GRAVE: [6522]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:17.553 GRAVE: [6524]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:17.696 GRAVE: [6523]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.EOFException: no more data available - expected end tag
</stream:stream> to close start tag <stream:stream> from line 1, parser
stopped on START_TAG seen ...://etherx.jabber.org/streams\'
version=\'1.0\' xmlns=\'jabber:client\'>... @1:126
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3035)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:18.557 GRAVE: [6532]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.net.SocketException: Tubería rota (Write failed)
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
        at java.io.BufferedWriter.flush(BufferedWriter.java:254)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:18.568 GRAVE: [6530]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:18.568 GRAVE: [6528]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:18.688 GRAVE: [6527]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:18.707 GRAVE: [6533]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:19.552 GRAVE: [6534]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:19.698 GRAVE: [6537]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.EOFException: no more data available - expected end tag
</stream:stream> to close start tag <stream:stream> from line 1, parser
stopped on START_TAG seen ...://etherx.jabber.org/streams\'
version=\'1.0\' xmlns=\'jabber:client\'>... @1:126
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3035)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:19.710 GRAVE: [6541]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
(...)
---------------------------------------------------------------------

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

---------------------------------------------------------------------
Jun 22 11:36:56 jcp5558f1b13870 info component disconnected: nil (false)
Jun 22 11:37:01 jcp5558f1f41980 info Incoming Jabber component connection
Jun 22 11:37:01 mod_component info Disconnecting component,
<stream:error> is: <stream:error><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>focus.ok does not match any
configured external components</text></stream:error>
Jun 22 11:37:01 jcp5558f1f41980 info component disconnected: nil (false)
Jun 22 11:37:06 jcp5558f2062a00 info Incoming Jabber component connection
Jun 22 11:37:06 mod_component info Disconnecting component,
<stream:error> is: <stream:error><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>focus.ok does not match any
configured external components</text></stream:error>
Jun 22 11:37:06 jcp5558f2062a00 info component disconnected: nil (false)
Jun 22 11:37:11 jcp5558f23f7060 info Incoming Jabber component connection
Jun 22 11:37:11 mod_component info Disconnecting component,
<stream:error> is: <stream:error><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>focus.ok does not match any
configured external components</text></stream:error>
Jun 22 11:37:11 jcp5558f23f7060 info component disconnected: nil (false)
---------------------------------------------------------------------

Any help would be appreciated.

Kind regards,
Daniel


#30

Hi,

Hi Saúl/Damian.

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

I suggest you use that repo. Nodejs move much faster than the Debian
release cycle, so you’re better off using it.

Thank you both for responding. I used the packages of node.org and it
seems that the generation of the packages in Jessie has been successful,
although I have some doubts that I would like to ask you.

The generated packages were:

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

The version is in changelog
(https://github.com/jitsi/jitsi-meet/blob/master/debian/changelog) as
every debian package.
The version is not committed to the repo, there are just tags with
snapshots for different versions. The actual version is kept in our ci
and is changed in the changelog on every build.

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

---------------------------------------------------------------------
Jicofo 2017-06-22 11:28:13.692 GRAVE: [6416]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:13.694 GRAVE: [6420]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:13.694 GRAVE: [6415]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.write(BufferedWriter.java:221)
        at java.io.Writer.write(Writer.java:157)
        at
org.jivesoftware.smack.PacketWriter.openStream(PacketWriter.java:261)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:190)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:14.549 GRAVE: [6398]
util.UtilActivator.uncaughtException().119 An uncaught exception
occurred in thread=Thread[Smack Reconnection Manager,5,main] and message
was: null
java.lang.IllegalThreadStateException
        at java.lang.Thread.start(Thread.java:708)
        at
org.jivesoftware.smack.PacketReader.startup(PacketReader.java:106)
        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.jivesoftware.smack.ReconnectionManager$2.run(ReconnectionManager.java:133)
Jicofo 2017-06-22 11:28:14.698 GRAVE: [6435]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:14.708 GRAVE: [6437]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:14.712 GRAVE: [6429]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:15.533 GRAVE: [6504]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.net.SocketException: Tubería rota (Write failed)
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
        at java.io.BufferedWriter.flush(BufferedWriter.java:254)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:15.550 GRAVE: [6508]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:15.593 GRAVE: [29]
org.jitsi.meet.ComponentMain.call().278 host-unknown, host:localhost,
port:5347
org.xmpp.component.ComponentException: host-unknown
        at
org.jivesoftware.whack.ExternalComponent.connect(ExternalComponent.java:219)
        at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:221)
        at
org.jivesoftware.whack.ExternalComponentManager.addComponent(ExternalComponentManager.java:201)
        at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:270)
        at org.jitsi.meet.ComponentMain$3.call(ComponentMain.java:255)
        at
org.jitsi.retry.RetryStrategy$TaskRunner.run(RetryStrategy.java:193)
        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:748)
Jicofo 2017-06-22 11:28:15.684 GRAVE: [6505]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:15.699 GRAVE: [6509]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:16.553 GRAVE: [6512]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:16.559 GRAVE: [6510]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:16.688 GRAVE: [6513]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:16.693 GRAVE: [6517]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:16.696 GRAVE: [6516]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.write(BufferedWriter.java:221)
        at java.io.Writer.write(Writer.java:157)
        at
org.jivesoftware.smack.PacketWriter.openStream(PacketWriter.java:261)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:190)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:17.551 GRAVE: [6522]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:17.553 GRAVE: [6524]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:17.696 GRAVE: [6523]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.EOFException: no more data available - expected end tag
</stream:stream> to close start tag <stream:stream> from line 1, parser
stopped on START_TAG seen ...://etherx.jabber.org/streams\'
version=\'1.0\' xmlns=\'jabber:client\'>... @1:126
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3035)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:18.557 GRAVE: [6532]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.net.SocketException: Tubería rota (Write failed)
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:155)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295)
        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141)
        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229)
        at java.io.BufferedWriter.flush(BufferedWriter.java:254)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:18.568 GRAVE: [6530]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:18.568 GRAVE: [6528]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:18.688 GRAVE: [6527]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:18.707 GRAVE: [6533]
org.jivesoftware.smack.PacketReader.notifyConnectionError() 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)
Jicofo 2017-06-22 11:28:19.552 GRAVE: [6534]
org.jivesoftware.smack.PacketWriter.writePackets() Error writing packet
java.io.IOException: Stream closed
        at java.io.BufferedWriter.ensureOpen(BufferedWriter.java:116)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:126)
        at java.io.BufferedWriter.flush(BufferedWriter.java:253)
        at
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:212)
        at
org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:42)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:80)
Jicofo 2017-06-22 11:28:19.698 GRAVE: [6537]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.io.EOFException: no more data available - expected end tag
</stream:stream> to close start tag <stream:stream> from line 1, parser
stopped on START_TAG seen ...://etherx.jabber.org/streams\'
version=\'1.0\' xmlns=\'jabber:client\'>... @1:126
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3035)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
Jicofo 2017-06-22 11:28:19.710 GRAVE: [6541]
org.jivesoftware.smack.PacketReader.notifyConnectionError() Closes the
connection temporary
java.net.SocketException: Socket closed
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
        at java.net.SocketInputStream.read(SocketInputStream.java:171)
        at java.net.SocketInputStream.read(SocketInputStream.java:141)
        at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
        at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
        at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
        at java.io.InputStreamReader.read(InputStreamReader.java:184)
        at java.io.BufferedReader.read1(BufferedReader.java:210)
        at java.io.BufferedReader.read(BufferedReader.java:286)
        at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2992)
        at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
        at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
        at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395)
        at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
        at
org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:329)
        at
org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:45)
        at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:74)
(...)
---------------------------------------------------------------------

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

---------------------------------------------------------------------
Jun 22 11:36:56 jcp5558f1b13870 info component disconnected: nil (false)
Jun 22 11:37:01 jcp5558f1f41980 info Incoming Jabber component connection
Jun 22 11:37:01 mod_component info Disconnecting component,
<stream:error> is: <stream:error><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>focus.ok does not match any
configured external components</text></stream:error>
Jun 22 11:37:01 jcp5558f1f41980 info component disconnected: nil (false)
Jun 22 11:37:06 jcp5558f2062a00 info Incoming Jabber component connection
Jun 22 11:37:06 mod_component info Disconnecting component,
<stream:error> is: <stream:error><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>focus.ok does not match any
configured external components</text></stream:error>
Jun 22 11:37:06 jcp5558f2062a00 info component disconnected: nil (false)
Jun 22 11:37:11 jcp5558f23f7060 info Incoming Jabber component connection
Jun 22 11:37:11 mod_component info Disconnecting component,
<stream:error> is: <stream:error><host-unknown
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>focus.ok does not match any
configured external components</text></stream:error>
Jun 22 11:37:11 jcp5558f23f7060 info component disconnected: nil (false)
---------------------------------------------------------------------

Jicofo cannot connect to prosody. host-unknown error means jicofo
tries to connect as a component to your prosody but prosody responds
as this component is not configured.
I would suggest make a jitsi-meet normal deployment on clean, make
sure it works then you can replace the components you want by your
custom versions.

Regards
damencho

···

On Thu, Jun 22, 2017 at 9:39 AM, Daniel <daniel-listas@gmx.net> wrote:

On 22/06/17 10:13, Saúl Ibarra Corretgé wrote:

On Wed, Jun 21, 2017 at 3:12 PM, Daniel <daniel-listas@gmx.net> wrote:

Any help would be appreciated.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#31

Hi,

Hi, Damian.

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

I suggest you use that repo. Nodejs move much faster than the Debian
release cycle, so you’re better off using it.

Thank you both for responding. I used the packages of node.org and it
seems that the generation of the packages in Jessie has been successful,
although I have some doubts that I would like to ask you.

The generated packages were:

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

The version is in changelog
(https://github.com/jitsi/jitsi-meet/blob/master/debian/changelog) as
every debian package.
The version is not committed to the repo, there are just tags with
snapshots for different versions. The actual version is kept in our ci
and is changed in the changelog on every build.

Let me see if I understood. Then this "changelog" file does not change
in its contents? The question is oriented to maintain a growing
numbering if in the future I generate a newer version of packages with
changes that you can introduce in the Git repo.

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

(...)

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

(...)

Jicofo cannot connect to prosody. host-unknown error means jicofo
tries to connect as a component to your prosody but prosody responds
as this component is not configured.
I would suggest make a jitsi-meet normal deployment on clean, make
sure it works then you can replace the components you want by your
custom versions.

Thank you. I was able to solve it. Apparently, the jicofo config file
was not created using the correct name for JICOFO_HOSTNAME and
JICOFO_AUTH_DOMAIN:

···

On 22/06/17 12:13, Damian Minkov wrote:

---------------------------------------------------------------------
root@defiant:/etc/jitsi/jicofo# diff config config.orig
6c6
< JICOFO_HOSTNAME=testmeet.freesoftware
---

JICOFO_HOSTNAME=ok

15c15
< JICOFO_AUTH_DOMAIN=auth.testmeet.freesoftware
---

JICOFO_AUTH_DOMAIN=auth.ok

---------------------------------------------------------------------

Can this be related to the order of installation of the packages?

1) # aptitude install jicofo jitsi-videobridge
2) # dpkg -i jitsi-meet-web_1.0.1-1_all.deb
3) # dpkg -i jitsi-meet-web-config_1.0.1-1_all.deb
4) # aptitude install prosody
5) # dpkg -i jitsi-meet-prosody_1.0.1-1_all.deb

Thanks for your time.

Kind regards,
Daniel


#32

Hi,

Hi,

Hi, Damian.

npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21

You are using very old versions of npm and node. Please update them
and try again.

I think the LTS versions are: node v6.11.0 + npm v3.10.10

Those are the versions available in Jessie when installing from
repositories as suggested by Github's Readme.md. Maybe it may be
advisable to update the Readme.md indicating which are the minimum
required versions.

In Debian Backports there seems to be a newer version of the "nodejs"
package: 4.8.2. This is the same version available in the current stable
branch (Debian Stretch). There does not seem to be any newer versions
for the npm package [1].

Do you think it could work with nodejs 4.8.2 or would it be better to
use this [2] repo?

I suggest you use that repo. Nodejs move much faster than the Debian
release cycle, so you’re better off using it.

Thank you both for responding. I used the packages of node.org and it
seems that the generation of the packages in Jessie has been successful,
although I have some doubts that I would like to ask you.

The generated packages were:

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

The version is in changelog
(https://github.com/jitsi/jitsi-meet/blob/master/debian/changelog) as
every debian package.
The version is not committed to the repo, there are just tags with
snapshots for different versions. The actual version is kept in our ci
and is changed in the changelog on every build.

Let me see if I understood. Then this "changelog" file does not change
in its contents? The question is oriented to maintain a growing
numbering if in the future I generate a newer version of packages with
changes that you can introduce in the Git repo.

Its content changes only when building in order the deb dev tools to
take into account when creating a package. There is a tool to change
it:
dch -v "$VERSION-1" "Build from git. "

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

(...)

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

(...)

Jicofo cannot connect to prosody. host-unknown error means jicofo
tries to connect as a component to your prosody but prosody responds
as this component is not configured.
I would suggest make a jitsi-meet normal deployment on clean, make
sure it works then you can replace the components you want by your
custom versions.

Thank you. I was able to solve it. Apparently, the jicofo config file
was not created using the correct name for JICOFO_HOSTNAME and
JICOFO_AUTH_DOMAIN:

JICOFO_AUTH_DOMAIN is generated using the value for JICOFO_HOSTNAME by
appending auth. in front of it. JICOFO_HOSTNAME is filled with the
value used for hostname when installing jvb and if its missing it asks
the user. So apparently it was filled as 'ok'.

Maybe the order is wrong you need to install first jvb and then
jicofo. While installing first jicofo you entered 'ok' as hostname.

We have a meta package which is taking care of those when installing
everything on a single machine
https://github.com/jitsi/jitsi-meet-debian-meta

https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/control-tmpl
Will install in that order that I mentioned.

Regards
damencho

···

On Thu, Jun 22, 2017 at 11:19 AM, Daniel <daniel-listas@gmx.net> wrote:

On 22/06/17 12:13, Damian Minkov wrote:

---------------------------------------------------------------------
root@defiant:/etc/jitsi/jicofo# diff config config.orig
6c6
< JICOFO_HOSTNAME=testmeet.freesoftware
---

JICOFO_HOSTNAME=ok

15c15
< JICOFO_AUTH_DOMAIN=auth.testmeet.freesoftware
---

JICOFO_AUTH_DOMAIN=auth.ok

---------------------------------------------------------------------

Can this be related to the order of installation of the packages?

1) # aptitude install jicofo jitsi-videobridge
2) # dpkg -i jitsi-meet-web_1.0.1-1_all.deb
3) # dpkg -i jitsi-meet-web-config_1.0.1-1_all.deb
4) # aptitude install prosody
5) # dpkg -i jitsi-meet-prosody_1.0.1-1_all.deb

Thanks for your time.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#33

Hi,

Hi, Damian.

The generated packages were:

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

The version is in changelog
(https://github.com/jitsi/jitsi-meet/blob/master/debian/changelog) as
every debian package.
The version is not committed to the repo, there are just tags with
snapshots for different versions. The actual version is kept in our ci
and is changed in the changelog on every build.

Let me see if I understood. Then this "changelog" file does not change
in its contents? The question is oriented to maintain a growing
numbering if in the future I generate a newer version of packages with
changes that you can introduce in the Git repo.

Its content changes only when building in order the deb dev tools to
take into account when creating a package. There is a tool to change
it:
dch -v "$VERSION-1" "Build from git. "

Thanks for the clarification. $VERSION is an environment variable that
is taken from somewhere?

Another thing I noticed is that if I wanted to update all the packages
of the operating system, this could lead to the packages that I
installed manually are replaced by the packages of the repository
because they have a greater version number:

···

On 22/06/17 13:53, Damian Minkov wrote:

--------------------------------------------------------------------------
root@testing:~# aptitude upgrade -V
The following packages will be upgraded:
  jitsi-meet-prosody [1.0.1-1 -> 1.0.2046-1] jitsi-meet-web [1.0.1-1 ->
1.0.2046-1] jitsi-meet-web-config [1.0.1-1 -> 1.0.2046-1]
  libgraphite2-3 [1.3.6-1~deb8u1 -> 1.3.10-1~deb8u1]
4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,305 kB of archives. After unpacking 12.0 MB will be used.
Do you want to continue? [Y/n/?]
--------------------------------------------------------------------------

Any suggestions to avoid this?

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

(...)

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

(...)

Jicofo cannot connect to prosody. host-unknown error means jicofo
tries to connect as a component to your prosody but prosody responds
as this component is not configured.
I would suggest make a jitsi-meet normal deployment on clean, make
sure it works then you can replace the components you want by your
custom versions.

Thank you. I was able to solve it. Apparently, the jicofo config file
was not created using the correct name for JICOFO_HOSTNAME and
JICOFO_AUTH_DOMAIN:

JICOFO_AUTH_DOMAIN is generated using the value for JICOFO_HOSTNAME by
appending auth. in front of it. JICOFO_HOSTNAME is filled with the
value used for hostname when installing jvb and if its missing it asks
the user. So apparently it was filled as 'ok'.

Maybe the order is wrong you need to install first jvb and then
jicofo. While installing first jicofo you entered 'ok' as hostname.

Perfect! Doing a manual installation in that order, everything worked
without problems. Thank you very much!

We have a meta package which is taking care of those when installing
everything on a single machine
https://github.com/jitsi/jitsi-meet-debian-meta

https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/control-tmpl
Will install in that order that I mentioned.

Interesting. Thank you for sharing this. The question I have about this
is: how should I instruct the meta package to install
jitsi-meet-prosody, jitsi-meet-web and jitsi-meet-web-config using my
packages and not the repository packages?

Thanks for your time.

Kind regards,
Daniel


#34

Hi,

Hi,

Hi, Damian.

The generated packages were:

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

The version is in changelog
(https://github.com/jitsi/jitsi-meet/blob/master/debian/changelog) as
every debian package.
The version is not committed to the repo, there are just tags with
snapshots for different versions. The actual version is kept in our ci
and is changed in the changelog on every build.

Let me see if I understood. Then this "changelog" file does not change
in its contents? The question is oriented to maintain a growing
numbering if in the future I generate a newer version of packages with
changes that you can introduce in the Git repo.

Its content changes only when building in order the deb dev tools to
take into account when creating a package. There is a tool to change
it:
dch -v "$VERSION-1" "Build from git. "

Thanks for the clarification. $VERSION is an environment variable that
is taken from somewhere?

Yes I just pasted a code from our ci.

Another thing I noticed is that if I wanted to update all the packages
of the operating system, this could lead to the packages that I
installed manually are replaced by the packages of the repository
because they have a greater version number:

--------------------------------------------------------------------------
root@testing:~# aptitude upgrade -V
The following packages will be upgraded:
  jitsi-meet-prosody [1.0.1-1 -> 1.0.2046-1] jitsi-meet-web [1.0.1-1 ->
1.0.2046-1] jitsi-meet-web-config [1.0.1-1 -> 1.0.2046-1]
  libgraphite2-3 [1.3.6-1~deb8u1 -> 1.3.10-1~deb8u1]
4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,305 kB of archives. After unpacking 12.0 MB will be used.
Do you want to continue? [Y/n/?]
--------------------------------------------------------------------------

Any suggestions to avoid this?

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

(...)

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

(...)

Jicofo cannot connect to prosody. host-unknown error means jicofo
tries to connect as a component to your prosody but prosody responds
as this component is not configured.
I would suggest make a jitsi-meet normal deployment on clean, make
sure it works then you can replace the components you want by your
custom versions.

Thank you. I was able to solve it. Apparently, the jicofo config file
was not created using the correct name for JICOFO_HOSTNAME and
JICOFO_AUTH_DOMAIN:

JICOFO_AUTH_DOMAIN is generated using the value for JICOFO_HOSTNAME by
appending auth. in front of it. JICOFO_HOSTNAME is filled with the
value used for hostname when installing jvb and if its missing it asks
the user. So apparently it was filled as 'ok'.

Maybe the order is wrong you need to install first jvb and then
jicofo. While installing first jicofo you entered 'ok' as hostname.

Perfect! Doing a manual installation in that order, everything worked
without problems. Thank you very much!

We have a meta package which is taking care of those when installing
everything on a single machine
https://github.com/jitsi/jitsi-meet-debian-meta

https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/control-tmpl
Will install in that order that I mentioned.

Interesting. Thank you for sharing this. The question I have about this
is: how should I instruct the meta package to install
jitsi-meet-prosody, jitsi-meet-web and jitsi-meet-web-config using my
packages and not the repository packages?

About this and upgrades you can come up with making your own meta
package and depend on your versions. Basically, if you want to make
fork of packages and reuse some packages you need to make changes to
package names and handle them.

Not sure what is your usecase and why you need your own packages, but
we advise to not fork packages and use the existing as it is with
adding hooks to put your stuff in there. If some hooks are missing it
is ok to discuss different approaches and you can come up with PRs and
integrate them in the upstream so other people from the community to
benefit from them.

Regards
damencho

···

On Thu, Jun 22, 2017 at 2:48 PM, Daniel <daniel-listas@gmx.net> wrote:

On 22/06/17 13:53, Damian Minkov wrote:

Thanks for your time.

Kind regards,
Daniel

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#35

Hi,

Hi, Damian.

---------------------------------------------------------------------
-rw-r--r-- 1 root root 5978 Jun 21 23:16
jitsi-meet-prosody_1.0.1-1_all.deb
-rw-r--r-- 1 root root 11662 Jun 21 23:16
jitsi-meet-tokens_1.0.1-1_all.deb
-rw-r--r-- 1 root root 1832 Jun 21 23:16
jitsi-meet-web_1.0.1-1_all.changes
-rw-r--r-- 1 root root 4266444 Jun 21 23:16 jitsi-meet-web_1.0.1-1_all.deb
-rw-r--r-- 1 root root 10154 Jun 21 23:16
jitsi-meet-web-config_1.0.1-1_all.deb
---------------------------------------------------------------------

I see that each file is generated with the version number 1.0.1-1, which
is different from the version numbers that appear in the Jitsi
repositories for the same packages. I guess it should be just the number
that is fixed somewhere because it looks like a newer version than the
one on "testing" repo considering that, for example, the thumbnail image
is smaller than the one we can see for Jitsi Meet on the Testing branch.
To avoid confusion, is there a way to keep a "correct" version number
for the generated version of each package?

The version is in changelog
(https://github.com/jitsi/jitsi-meet/blob/master/debian/changelog) as
every debian package.
The version is not committed to the repo, there are just tags with
snapshots for different versions. The actual version is kept in our ci
and is changed in the changelog on every build.

Let me see if I understood. Then this "changelog" file does not change
in its contents? The question is oriented to maintain a growing
numbering if in the future I generate a newer version of packages with
changes that you can introduce in the Git repo.

Its content changes only when building in order the deb dev tools to
take into account when creating a package. There is a tool to change
it:
dch -v "$VERSION-1" "Build from git. "

Thanks for the clarification. $VERSION is an environment variable that
is taken from somewhere?

Yes I just pasted a code from our ci.

Another thing I noticed is that if I wanted to update all the packages
of the operating system, this could lead to the packages that I
installed manually are replaced by the packages of the repository
because they have a greater version number:

--------------------------------------------------------------------------
root@testing:~# aptitude upgrade -V
The following packages will be upgraded:
  jitsi-meet-prosody [1.0.1-1 -> 1.0.2046-1] jitsi-meet-web [1.0.1-1 ->
1.0.2046-1] jitsi-meet-web-config [1.0.1-1 -> 1.0.2046-1]
  libgraphite2-3 [1.3.6-1~deb8u1 -> 1.3.10-1~deb8u1]
4 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,305 kB of archives. After unpacking 12.0 MB will be used.
Do you want to continue? [Y/n/?]
--------------------------------------------------------------------------

Any suggestions to avoid this?

On the other hand, I tried to test the packages in an environment with
Debian Strech (remember they were generated in Jessie) and there I'm
having several issues after installation. Should they run smoothly?

I am observing these errors in Jicofo:

(...)

There are several errors of type "SEVERE" (the log says "GRAVE").

At the same time I see errors in Prosody:

(...)

Jicofo cannot connect to prosody. host-unknown error means jicofo
tries to connect as a component to your prosody but prosody responds
as this component is not configured.
I would suggest make a jitsi-meet normal deployment on clean, make
sure it works then you can replace the components you want by your
custom versions.

Thank you. I was able to solve it. Apparently, the jicofo config file
was not created using the correct name for JICOFO_HOSTNAME and
JICOFO_AUTH_DOMAIN:

JICOFO_AUTH_DOMAIN is generated using the value for JICOFO_HOSTNAME by
appending auth. in front of it. JICOFO_HOSTNAME is filled with the
value used for hostname when installing jvb and if its missing it asks
the user. So apparently it was filled as 'ok'.

Maybe the order is wrong you need to install first jvb and then
jicofo. While installing first jicofo you entered 'ok' as hostname.

Perfect! Doing a manual installation in that order, everything worked
without problems. Thank you very much!

We have a meta package which is taking care of those when installing
everything on a single machine
https://github.com/jitsi/jitsi-meet-debian-meta

https://github.com/jitsi/jitsi-meet-debian-meta/blob/master/control-tmpl
Will install in that order that I mentioned.

Interesting. Thank you for sharing this. The question I have about this
is: how should I instruct the meta package to install
jitsi-meet-prosody, jitsi-meet-web and jitsi-meet-web-config using my
packages and not the repository packages?

About this and upgrades you can come up with making your own meta
package and depend on your versions. Basically, if you want to make
fork of packages and reuse some packages you need to make changes to
package names and handle them.

Not sure what is your usecase and why you need your own packages, but
we advise to not fork packages and use the existing as it is with
adding hooks to put your stuff in there. If some hooks are missing it
is ok to discuss different approaches and you can come up with PRs and
integrate them in the upstream so other people from the community to
benefit from them.

Thank you. This additional complexity of creating new packages comes
from the need to integrate Jitsi Meet with an LMS (learning management
system), Chamilo. The idea is that any device can directly access Jitsi
Meet but, for the mails exchanged with Saúl and tests that I did on my
side, I noticed that access from Android is now intercepted (after
setting MOBILE_APP_PROMO to false). It can be accessed using a Chrome
checkbox to display the desktop version, but the idea is for users to
naturally access Jitsi from their phones without having to use any
special settings or mobile application.

So my idea was to change this check [1], changing "android" to something
like "NOTandroid", as Saúl suggested, and recompile, since there is no
other way to avoid this. Yes, I know it's a lot of work for a trivial
change...

If you have any other approach that allows to change this behavior and
at the same time facilitate the maintenance, I would love to hear it.

Thanks in advance.

Kind regards,
Daniel

[1]
https://github.com/jitsi/jitsi-meet/blob/master/react/features/app/functions.web.js#L42

···

On 22/06/17 16:59, Damian Minkov wrote: