[jitsi-dev] Jitsi Videobridge version 85 & 86


#1

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including version 84 seem to work fine for me, however I can't get version 85 & 86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address /fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address /fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works fine.

Thanks!
Debber


#2

Hey Debber,

This could be my fault.

Could you please send your complete logs?

Emil

···

On 24.02.2014, at 11:31, Debber <debber@pref.nl> wrote:

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including version 84 seem to work fine for me, however I can't get version 85 & 86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address /fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address /fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works fine.

Thanks!
Debber

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

--
https://jitsi.org


#3

Hi Emil,

Thanks for the reply. Attached is the jvb log (jvb version 86).
Also added the Prosody log (prosody-trunk)
OS is Ubuntu 12.04 64bit.

Debber

Emil Ivov schreef op 24-02-14 17:34:

jvb.log (23.4 KB)

prosody.log (43.9 KB)

···

Hey Debber,

This could be my fault.

Could you please send your complete logs?

Emil

On 24.02.2014, at 11:31, Debber <debber@pref.nl> wrote:

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including version 84 seem to work fine for me, however I can't get version 85 & 86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address /fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address /fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works fine.

Thanks!
Debber

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


#4

This issue seems to persist with version 87.

Furthermore I noticed this process has been invoked running as user jitsi (user exclusively for the Jitsi Videobridge):

jitsi@prez:~$ ps -ef|grep jitsi
jitsi 31077 1 0 07:03 pts/0 00:00:00 /usr/bin/python /usr/bin/ec2metadata
...

Seems weird as the host isn't an EC2 instance. In this case the host is a kvm-instance running within an Openstack environment.

Thanks,
Debber

···

Thanks for the reply. Attached is the jvb log (jvb version 86).
Also added the Prosody log (prosody-trunk)
OS is Ubuntu 12.04 64bit.

Debber

Emil Ivov schreef op 24-02-14 17:34:

Hey Debber,

This could be my fault.

Could you please send your complete logs?

Emil

On 24.02.2014, at 11:31, Debber <debber@pref.nl> wrote:

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including
version 84 seem to work fine for me, however I can't get version 85 &
86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign
requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign
requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works
fine.

Thanks!
Debber

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

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


#5

Hey Debber,

This issue seems to persist with version 87.

Furthermore I noticed this process has been invoked running as user jitsi (user exclusively for the Jitsi Videobridge):

jitsi@prez:~$ ps -ef|grep jitsi
jitsi 31077 1 0 07:03 pts/0 00:00:00 /usr/bin/python /usr/bin/ec2metadata
...

Seems weird as the host isn't an EC2 instance. In this case the host is a kvm-instance running within an Openstack environment.

That's actually the command that we run in order to determine whether this is (or not) an EC2 instance. Are you saying that it just hangs there? That's interesting and it would definitely explain the issue. What does that command do on your system?

Emil

···

On 27.02.2014, at 06:57, Debber <debber@pref.nl> wrote:

Thanks,
Debber

Thanks for the reply. Attached is the jvb log (jvb version 86).
Also added the Prosody log (prosody-trunk)
OS is Ubuntu 12.04 64bit.

Debber

Emil Ivov schreef op 24-02-14 17:34:

Hey Debber,

This could be my fault.

Could you please send your complete logs?

Emil

On 24.02.2014, at 11:31, Debber <debber@pref.nl> wrote:

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including
version 84 seem to work fine for me, however I can't get version 85 &
86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign
requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign
requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works
fine.

Thanks!
Debber

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

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

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

--
https://jitsi.org


#6

Hey Debber,

Could you please check with the latest build? Just changed ec2
detection to not rely on actually calling the command and just verify
its existence.

Please let me know how this works for you,
Emil

···

On Sat, Mar 1, 2014 at 3:01 PM, Emil Ivov <emcho@jitsi.org> wrote:

Hey Debber,

On 27.02.2014, at 06:57, Debber <debber@pref.nl> wrote:

This issue seems to persist with version 87.

Furthermore I noticed this process has been invoked running as user jitsi (user exclusively for the Jitsi Videobridge):

jitsi@prez:~$ ps -ef|grep jitsi
jitsi 31077 1 0 07:03 pts/0 00:00:00 /usr/bin/python /usr/bin/ec2metadata
...

Seems weird as the host isn't an EC2 instance. In this case the host is a kvm-instance running within an Openstack environment.

That's actually the command that we run in order to determine whether this is (or not) an EC2 instance. Are you saying that it just hangs there? That's interesting and it would definitely explain the issue. What does that command do on your system?

Emil

Thanks,
Debber

Thanks for the reply. Attached is the jvb log (jvb version 86).
Also added the Prosody log (prosody-trunk)
OS is Ubuntu 12.04 64bit.

Debber

Emil Ivov schreef op 24-02-14 17:34:

Hey Debber,

This could be my fault.

Could you please send your complete logs?

Emil

On 24.02.2014, at 11:31, Debber <debber@pref.nl> wrote:

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including
version 84 seem to work fine for me, however I can't get version 85 &
86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign
requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign
requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works
fine.

Thanks!
Debber

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

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

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

--
https://jitsi.org

--
https://jitsi.org


#7

Thanks Emil, I'd be glad to! Did you already push the code?
At this moment (Sun 06:54am CET) the latest available version seems still to be 87...

Regarding /usr/bin/ec2metadata....the file is in the Ubuntu package
cloud-utils

root@prez:~# dpkg -S /usr/bin/ec2metadata
cloud-utils: /usr/bin/ec2metadata

If I remove it, this would also remove some other packages, so i'm not sure that this would be a wise move....afaik the packages root from the base-image of the vps-hoster.

root@prez:~# apt-get remove --purge cloud-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
   unattended-upgrades python-pycurl python-cheetah python-software-properties python-configobj
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
   cloud-init* cloud-initramfs-growroot* cloud-utils*
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 726 kB disk space will be freed.
Do you want to continue [Y/n]? n
Abort.

Debber

PS Sorry Emil, at first I replied to you instead of the list...probably due to a serious lack of coffee :wink:

Emil Ivov schreef op 02-03-14 03:46:

···

Hey Debber,

Could you please check with the latest build? Just changed ec2
detection to not rely on actually calling the command and just verify
its existence.

Please let me know how this works for you,
Emil

On Sat, Mar 1, 2014 at 3:01 PM, Emil Ivov <emcho@jitsi.org> wrote:

Hey Debber,

On 27.02.2014, at 06:57, Debber <debber@pref.nl> wrote:

This issue seems to persist with version 87.

Furthermore I noticed this process has been invoked running as user jitsi (user exclusively for the Jitsi Videobridge):

jitsi@prez:~$ ps -ef|grep jitsi
jitsi 31077 1 0 07:03 pts/0 00:00:00 /usr/bin/python /usr/bin/ec2metadata
...

Seems weird as the host isn't an EC2 instance. In this case the host is a kvm-instance running within an Openstack environment.

That's actually the command that we run in order to determine whether this is (or not) an EC2 instance. Are you saying that it just hangs there? That's interesting and it would definitely explain the issue. What does that command do on your system?

Emil

Thanks,
Debber

Thanks for the reply. Attached is the jvb log (jvb version 86).
Also added the Prosody log (prosody-trunk)
OS is Ubuntu 12.04 64bit.

Debber

Emil Ivov schreef op 24-02-14 17:34:

Hey Debber,

This could be my fault.

Could you please send your complete logs?

Emil

On 24.02.2014, at 11:31, Debber <debber@pref.nl> wrote:

Hi all,

While deploying Jitmeet the Jitsi Videobridge up to and including
version 84 seem to work fine for me, however I can't get version 85 &
86 to work.

Maybe I'm missing something config-wise?

The logs from the Jitsi Videobridge (85 and 86) show:

...
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fea5:6b80%3 and port 10049 (Cannot assign
requested address)
Feb 24, 2014 8:43:26 AM org.ice4j.ice.harvest.HostCandidateHarvester
harvest
WARNING: Failed to create a socket for:
addr:/fe80:0:0:0:f816:3eff:fea5:6b80%3
preferredPort:10000
minPort:10000
maxPort:10100
protocol:udp
Continuing with next address
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
INFO: Retrying a bind because of a failure to bind to address
/fe80:0:0:0:f816:3eff:fe32:b627%2 and port 10000 (Cannot assign
requested address)
Feb 24, 2014 8:43:27 AM org.ice4j.ice.harvest.HostCandidateHarvester
createDatagramSocket
...

For now I downgraded the Jitsi Videobridge to version 84 which works
fine.

Thanks!
Debber

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

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

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

--
https://jitsi.org


#8

Hello,

Hey Debber,

Could you please check with the latest build? Just changed ec2
detection to not rely on actually calling the command and just verify
its existence.

I don't think that just checking the binary is reliable. How about checking
http://169.254.169.254 directly, with a very short timeout, and saving
the result?

An example patch is attached (which I haven't actually tested). I don't
know which is more appropriate -- doing the check on the first call to
smellsLikeAnEC2(), or in a static block (or maybe in a new thread
started in a static block). I did the first.

Regards,
Boris

ice4j-ec2.patch (2.85 KB)

···

On 02/03/14 03:46, Emil Ivov wrote:


#9

Hello,

Hey Debber,

Could you please check with the latest build? Just changed ec2
detection to not rely on actually calling the command and just verify
its existence.

I don't think that just checking the binary is reliable.

It's not. The change was meant to prevent the process from hanging.
But you are right, it would probably still hang in this same case.

How about checking
http://169.254.169.254 directly, with a very short timeout, and saving
the result?

An example patch is attached (which I haven't actually tested). I don't
know which is more appropriate -- doing the check on the first call to
smellsLikeAnEC2(), or in a static block (or maybe in a new thread
started in a static block). I did the first.

Looks good to me!

Emil

···

On Mon, Mar 3, 2014 at 10:25 PM, Boris Grozev <boris@jitsi.org> wrote:

On 02/03/14 03:46, Emil Ivov wrote:

Regards,
Boris

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

--
https://jitsi.org


#10

Emil Ivov schreef op 04-03-14 12:41:

Hello,

Hey Debber,

Could you please check with the latest build? Just changed ec2
detection to not rely on actually calling the command and just verify
its existence.

I don't think that just checking the binary is reliable.

It's not. The change was meant to prevent the process from hanging.
But you are right, it would probably still hang in this same case.

Agreed, thanks Emil and Boris! 'mv /usr/bin/ec2metadata /usr/bin/ec2metadata.bak' allowed for an upgrade to jvb version 89 in my case.

How about checking
http://169.254.169.254 directly, with a very short timeout, and saving
the result?

An example patch is attached (which I haven't actually tested). I don't
know which is more appropriate -- doing the check on the first call to
smellsLikeAnEC2(), or in a static block (or maybe in a new thread
started in a static block). I did the first.

Looks good to me!

Guess you guys are right, opting for a practical approach as long as there aren't any identifying facts within the vps itself....

Thanks again,
Debber

···

On Mon, Mar 3, 2014 at 10:25 PM, Boris Grozev <boris@jitsi.org> wrote:

On 02/03/14 03:46, Emil Ivov wrote: