Unable to install BBB 2.5 on ubuntu 20.04

[intense razer]

Hi,

I'm having problems installing BBB 2.5 on a clean ubuntu 20.04 server. The same server ran BBB 2.4, nothing changed so far.

But I'm getting a lot of errors during installing with the skript:

Sending build context to Docker daemon   2.56kB
Step 1/5 : FROM openjdk:11-jre-bullseye
 ---> eb33bf3b5fe3
Step 2/5 : ENV DEBIAN_FRONTEND noninteractive
 ---> Using cache
 ---> 3acee6812b54
Step 3/5 : RUN echo "deb http://deb.debian.org/debian bullseye-backports main" >                                                                                                             > /etc/apt/sources.list
 ---> Using cache
 ---> 881761719b04
Step 4/5 : RUN apt update && apt -y install locales-all fontconfig libxt6 libxre                                                                                                             nder1
 ---> Running in 978842e6eaed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Err:1 http://deb.debian.org/debian bullseye InRelease
  Temporary failure resolving 'deb.debian.org'
Err:2 http://security.debian.org/debian-security bullseye-security InRelease
  Temporary failure resolving 'security.debian.org'
Err:3 http://deb.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'deb.debian.org'
Err:4 http://deb.debian.org/debian bullseye-backports InRelease
  Temporary failure resolving 'deb.debian.org'
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Tempor                                                                                                             ary failure resolving 'deb.debian.org'
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-sec                                                                                                             urity/InRelease  Temporary failure resolving 'security.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease                                                                                                               Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-backports/InRelea                                                                                                             se  Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used                                                                                                              instead.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Reading package lists...
Building dependency tree...
Reading state information...
Package locales-all is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

No idea what is happening there, could it be that docker can not get a connection to internet?

Please help, if you can :)

Regards, Norbert

[Wolfgang Pein]

Hi,

yesterday I successfully installed BBB V2.5.2 on a fresh MS Azure Ubuntu 20.04 Virtual machine.

Maybe the following comments help:

- I used the "special" install script bbb-install-2.5.sh (see also:  https://github.com/bigbluebutton/bigbluebutton/releases   )   

- use the correct BBB version (in my case focal-250-2.5.2)

- check the firewall (in my case I initially forgot to open the MS Azure VM firewall for RTP (UDP), HTTP (TCP) and HTTPS (TCP))

Good luck!

Wolfgang

[intense razer]

Thanks for your help. Sadly nothing changed. I disabled every firewall, using the script as advised.

I am using a bare metal server, no vm.

Any other suggestions?

Thanks in advance,

Norbert 

--
You received this message because you are subscribed to a topic in the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bigbluebutton-setup/KdCj0eCTSaI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/4e785c6e-a690-46eb-aa76-4631e20ea654n%40googlegroups.com.

[Fred Dixon]

Hi,

Two questions: where is your server located? On your server are you able to reach deb.debian.org?  

Trying a ping, here's the output we see on one of our servers

$ ping deb.debian.org
PING debian.map.fastlydns.net (199.232.162.132): 56 data bytes
64 bytes from 199.232.162.132: icmp_seq=0 ttl=49 time=36.781 ms

Regards,... Fred

You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/CACse3txtmVe7%2BWG1zusubh3%2BSNvXB6-md-aqofe%2BTGPty1ivjw%40mail.gmail.com.

--

BigBlueButton Developer

http://bigbluebutton.org/

Like BigBlueButton?  Tweet us at @bigbluebutton

[Wolfgang Pein]

Hi,

I can agree on what Fred said with a small difference: 

when I ping deb.debian.org on my Azure server then this resolves to IP-adress 199.232.138.132

In addition I would suggest the following (I assume that your system is a test system):

- upgrade your Ubuntu 20.04 with/to the latest available Ubuntu 20.04 packages (if not already done)

- install BBB without Greenlight (I assume that only Greenlight does use docker) but instead use the demo option (-a)

So to install BBB V2.5.2 run the following command (as sudo or start sudo bash and then run this command):

wget -qO- https://ubuntu.bigbluebutton.org/bbb-install-2.5.sh | bash -s -- -v focal-250-2.5.2 -s <your domain name> -e <your mail-adress> -w -a

You need to add the -c option if you want to use a turn-server

Hope this helps!

Regards

Wolfgang

[intense razer]

Thanks for your help!

@ Fred: The server is located in Germany

ping to debian.org:

PING debian.map.fastlydns.net (199.232.150.132) 56(84) bytes of data.

64 bytes from 199.232.150.132 (199.232.150.132): icmp_seq=1 ttl=58 time=12.8 ms

It is not reachable during installation of bbb 2.5 - the same server (with ubuntu 18.04) ran bbb 2.4 - witout any problems during installation.

@wop...

Because of that error "debian.org not reachable" I updateed my sources.lst. The Server updated to the latest ubuntu 20.04.4 during installation of bbb (I did it also before installation). Same errors - and if i tried to install bbb after the update, the script said i have to run it under ubuntu 20.04. Curios...

I hope that information is helpful helping me :)

Regards,

Norbert

Fred Dixon schrieb am Samstag, 9. Juli 2022 um 12:26:02 UTC+2:

[intense razer]

I tried installing without greenlight as well - same behaviour:

# Building bbb-libreoffice docker image
#

Sending build context to Docker daemon   2.56kB
Step 1/5 : FROM openjdk:11-jre-bullseye
 ---> eb33bf3b5fe3
Step 2/5 : ENV DEBIAN_FRONTEND noninteractive
 ---> Using cache
 ---> 3acee6812b54
Step 3/5 : RUN echo "deb http://deb.debian.org/debian bullseye-backports main" >> /etc/apt/sources.list
 ---> Using cache
 ---> 881761719b04
Step 4/5 : RUN apt update && apt -y install locales-all fontconfig libxt6 libxrender1

 ---> Running in 569a95dc1651

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Err:1 http://deb.debian.org/debian bullseye InRelease
  Temporary failure resolving 'deb.debian.org'
Err:2 http://security.debian.org/debian-security bullseye-security InRelease
  Temporary failure resolving 'security.debian.org'

So i think the problem must have to do when the script tries to build the docker image for bbb-libreoffice. But i don't know why than there is no internet.

I even tried to check/change the docker ip on the system by creating /etc/docker/daemon.json and things like that. But without any luck.

[Wolfgang Pein]

Hi,

this is strange! I never came across similar messages when installing BBB.

Maybe this problem does arise from the combination: hardware, Ubuntu version and BBB V2.5.2 script? 

If you have a chance you may install BBB in a different environment. I never used dedicated hardware but only virtual machines either in MS Azure or Linux KVM (Proxmox).

You probably can also use virtual box or VMWare workstation.

Do you have a public IPv4 adress for your server? Are you using your server behind a firewall/router e.g. a FritzBox?

Networking could be a nightmare! I support 1 installation which runs on a Proxmox VM behind a FritzBox. "Our" solution was to use the feature "exposed host" on the FritzBox to exclusively use the MyFritz IPv4 adress for BBB.

Especially LetsEncrypt needs a publicly reachable IPv4-adress.

One more comment: do you have native IPv4 or IPv4 over IPv6 (DSL Lite)? The german provider 1&1 obviously changed their networking during these days. I had a working VPN tunnel between 2 FritzBoxes and this no longer works

with DSL Lite as before.

I checked the putty output of my recent BBB install - I do attach an extract to this message.

There is one obvious difference: in your logfile it is stated:  ---> using cache !!!

I do not see such a message in my log - why is cache used in your install???

Hope this helps!

Wolfgang

--------

Extract log my BBB install:

dc649b0835b3: Extracting   40.3MB/47.2MB
[1B [1A [2K
dc649b0835b3: Extracting  45.71MB/47.2MB
[1B [1A [2K
dc649b0835b3: Extracting   47.2MB/47.2MB
[1B [1A [2K
dc649b0835b3: Pull complete
[1BDigest: sha256:02ca7dec8b1166e5e3380925870189153cd9e51eacc75f66f303feb916e3d3ff

Status: Downloaded newer image for openjdk:11-jre-bullseye

 ---> eb33bf3b5fe3

Step 2/5 : ENV DEBIAN_FRONTEND noninteractive

 ---> Running in 0fc9d8493496

Removing intermediate container 0fc9d8493496

 ---> 8d342358459a

Step 3/5 : RUN echo "deb http://deb.debian.org/debian bullseye-backports main" >> /etc/apt/sources.list

 ---> Running in 2def7b5e2cd0

Removing intermediate container 2def7b5e2cd0

 ---> 42612a24f398

Step 4/5 : RUN apt update && apt -y install locales-all fontconfig libxt6 libxrender1

 ---> Running in c587ef7ab876

[91m

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

[0m [91m

[0mGet:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]

Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB]

Get:3 http://deb.debian.org/debian bullseye-updates InRelease [39.4 kB]

Get:4 http://deb.debian.org/debian bullseye-backports InRelease [44.2 kB]

Get:5 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [164 kB]

Get:6 http://deb.debian.org/debian bullseye/main amd64 Packages [8182 kB]

Get:7 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2592 B]

Get:8 http://deb.debian.org/debian bullseye-backports/main amd64 Packages [312 kB]

Fetched 8904 kB in 1s (6683 kB/s)

Reading package lists...

Building dependency tree...

Reading state information...

13 packages can be upgraded. Run 'apt list --upgradable' to see them.

[91m

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

[0mReading package lists...

Building dependency tree...

Reading state information...

fontconfig is already the newest version (2.13.1-4.2).

The following additional packages will be installed:

  libbsd0 libc-l10n libice6 libmd0 libsm6 libx11-6 libx11-data libxau6 libxcb1

  libxdmcp6 x11-common

The following NEW packages will be installed:

  libbsd0 libc-l10n libice6 libmd0 libsm6 libx11-6 libx11-data libxau6 libxcb1

  libxdmcp6 libxrender1 libxt6 locales-all x11-common

0 upgraded, 14 newly installed, 0 to remove and 13 not upgraded.

Need to get 13.8 MB of archives.

After this operation, 237 MB of additional disk space will be used.

Get:1 http://deb.debian.org/debian bullseye/main amd64 libc-l10n all 2.31-13+deb11u3 [863 kB]

Get:2 http://deb.debian.org/debian bullseye/main amd64 libmd0 amd64 1.0.3-3 [28.0 kB]

Get:3 http://deb.debian.org/debian bullseye/main amd64 libbsd0 amd64 0.11.3-1 [108 kB]

Get:4 http://deb.debian.org/debian bullseye/main amd64 x11-common all 1:7.7+22 [252 kB]

Get:5 http://deb.debian.org/debian bullseye/main amd64 libice6 amd64 2:1.0.10-1 [58.5 kB]

Get:6 http://deb.debian.org/debian bullseye/main amd64 libsm6 amd64 2:1.2.3-1 [35.1 kB]

Get:7 http://deb.debian.org/debian bullseye/main amd64 libxau6 amd64 1:1.0.9-1 [19.7 kB]

Get:8 http://deb.debian.org/debian bullseye/main amd64 libxdmcp6 amd64 1:1.1.2-3 [26.3 kB]

Get:9 http://deb.debian.org/debian bullseye/main amd64 libxcb1 amd64 1.14-3 [140 kB]

Get:10 http://deb.debian.org/debian bullseye/main amd64 libx11-data all 2:1.7.2-1 [311 kB]

Get:11 http://deb.debian.org/debian bullseye/main amd64 libx11-6 amd64 2:1.7.2-1 [772 kB]

Get:12 http://deb.debian.org/debian bullseye/main amd64 libxrender1 amd64 1:0.9.10-1 [33.0 kB]

Get:13 http://deb.debian.org/debian bullseye/main amd64 libxt6 amd64 1:1.2.0-1 [189 kB]

Get:14 http://deb.debian.org/debian bullseye/main amd64 locales-all amd64 2.31-13+deb11u3 [10.9 MB]

[91mdebconf: delaying package configuration, since apt-utils is not installed

[0mFetched 13.8 MB in 0s (110 MB/s)

Selecting previously unselected package libc-l10n.

[intense razer]

Thanks for all suggestions.

The server is hosted by Strato, it has a valid IPv4 and IPv6, no firewall installed.

Thanks for the hint with the cache, any idea how to prevent using it during installation?

Regards,

Norbert

[Wolfgang Pein]

Hi,

unfortunately I have no clue how to prevent caching. Is your Ubuntu a fresh installation made by yourself? Or do you use a predefined image from Strato (this is the case with MS Azure - you have to use their Ubuntu images and cannot install the Operation system by yourself)? Or maybe you upgraded your BBB System from Ubuntu 18.04 to 20.04? 

There are many articles on docker and caching and how to prevent  caching by using an Option but obviously this would mean to change the install script.

Why is my install working without caching? At least this message on caching does not appear!

So let's ignore different Hardware, if you use the same  install Script for BBB V2.5 then the problem can only be with Ubuntu and it's packages!

 

So the only idea I have is to really verify which Ubuntu 20.04 image is used resp. install Ubuntu 20.04 again on a fresh disc followed by BBB install

:-) Wolfgang

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/25d48b26-346e-4e95-b1b4-4dc97495b071n%40googlegroups.com.

[intense razer]

Hi,

you just named the problem: Strato.

I have to use there Images, i even can not Go back to 18.04.

And yes, it is a clean Installation.

Seems to be bad luck ;)

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/CAHp6-%3Dqi9YSga_mXc%2B63NvJpaDVsHJc0dV015wwDHjGnOa3OVA%40mail.gmail.com.

[Wolfgang Pein]

Maybe this link helps to delete docker cache. If no cache then it cannot be used?

https://nodogmablog.bryanhogan.net/2021/11/doing-a-bit-of-docker-cleanup/

[intense razer]

Thanks for that hint. Sadly the same: nothing changed, same error.

Maybe I have to switch to another provider and change the whole server. For whatever reason ;)

[Jean Pluzo]

Hi,

I've also had similar problems. This was caused by me being behind a proxy. Once I configured the proxy I could install BBB 2.4/2.5 without problems.

I'm not sure about Strato, but perhaps double check proxy settings (in Ubuntu you have to set proxies independently for apt, environment and sometimes docker).

Also I would check any DNS issues, since netplan (I think) seems to need a DNS server explicitly activated (in the yaml config).

All in all, this does not seem to be a BBB issue, but an Ubuntu issue.

Regards,

J.

[Wolfgang Pein]

Maybe one last idea:

obviously the problem is in the area of docker.
Would it be possible to uninstall Docker on the fresh Strato Ubuntu 20.04 server (probably docker is part of the provided image by Strato), restart the server and then install BBB?
I think that the BBB install script will install docker if not available - maybe this makes the difference?

Or ask Strato for a solution (use of another server)!!

:-) Wolfgang

[Martin Thomas Schrott]

Hi,

the same problem was discussed in the zki bbb-tech list.

Wolfgang Huber  had this issue with strato last week.

It has nothing to do with docker, we already tried uninstalling and a lot of other configurations.

The solution seems to be:

in /etc/sysctl.conf set:
net.ipv4.ip_forward = 1
sysctl -p /etc/sysctl.conf

cheers

Martin

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/58bb0231-b5cf-41f5-9b02-cd9bf7d5e255n%40googlegroups.com.

[intense razer]

Thanks for that suggestion.

I uncommented net.ipv4.ip_forward = 1in /etc/sysctl.conf but sadly nothing changed.

Could you please provide more informsation about that discussion in zki tech?

Thanks!

[Martin Thomas Schrott]

Hi,

oh, that's bad - so the solution seems to be much more complex.

I'll attach some information from the original discussion in german. Maybe you should join the thread at

bbb-...@zki.de

or contact Wolfgang (see below)

please keep us up to date on both lists.

cheers

Martin

----

Von: huber <hu...@ash-berlin.eu>Hallo,
bis jetzt darf Docker einmal ins Internet, dann brauchts einen Restart
Ich hab nochmal Nameserver durchprobiert:
mit 81.169.148.34 und 208.67.222.222 bekomme ich die Antworten als ipv4,
mit 85.214.7.22 und 81.169.163.106 ipv6 zurück
das *** Can't find debian.org: No answer würde ich dem jeweils fehlende ipv Format zurechnen.
Wenn ich nslookup debian.org ohne Docker mache, bekomme ich bei OpenDNS und den Strato Servern ipv4 und ipv6
Die Ausgaben hängen unten dran.
Wenn docker den DNS über die daemon.json bekommt, ist die Antwort immer in ipv4
Ist es denn normal, daß ich jedesmal einen Restart machen muß, bevor Docker wieder ins Internet darf? und
macht das irgendwie Sinn, daß es nur entweder ipv4 oder ipv6 zurück gibt?
Ohne
service docker restart
gibts:
root@bbb18:~# docker run busybox nslookup debian.org
;; connection timed out; no servers could be reached


Viele Grüße,
Wolfgang

Draufgemacht hatte ich es mit:
apt install docker docker-compose docker.io

Bevor Docker ins Internet darf, muß ich noch:
service docker stop &&
iptables -t nat -F &&
ifconfig docker0 down &&
brctl delbr docker0 &&
service docker start -d
machen


In der daemon.json hab ich jetzt:
{
    "dns": ["208.67.222.222", "1.1.1.1"]
}
drin, versucht hatte ich aber auch
{
  "data-root": "/etc/docker/",
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  }
}
und anderen DNS Servern



root@bbb18:~# nslookup debian.org
Server:        85.214.7.22
Address:    85.214.7.22#53

Non-authoritative answer:
Name:    debian.org
Address: 128.31.0.62
Name:    debian.org
Address: 149.20.4.15
Name:    debian.org
Address: 130.89.148.77
Name:    debian.org
Address: 2001:4f8:1:c::15
Name:    debian.org
Address: 2001:67c:2564:a119::77
Name:    debian.org
Address: 2603:400a:ffff:bb8::801f:3e


root@bbb18:~# service docker restart
root@bbb18:~# docker run --dns 85.214.7.22 busybox nslookup debian.org
Server:        85.214.7.22
Address:    85.214.7.22:53

Non-authoritative answer:
Name:    debian.org
Address: 2001:4f8:1:c::15
Name:    debian.org
Address: 2603:400a:ffff:bb8::801f:3e
Name:    debian.org
Address: 2001:67c:2564:a119::77

*** Can't find debian.org: No answer

root@bbb18:~# service docker restart
root@bbb18:~# docker run --dns 81.169.163.106 busybox nslookup debian.org
Server:        81.169.163.106
Address:    81.169.163.106:53

Non-authoritative answer:
Name:    debian.org
Address: 2001:67c:2564:a119::77
Name:    debian.org
Address: 2603:400a:ffff:bb8::801f:3e
Name:    debian.org
Address: 2001:4f8:1:c::15

*** Can't find debian.org: No answer

root@bbb18:~# docker run --dns 81.169.163.106 busybox nslookup debian.org
;; connection timed out; no servers could be reached

root@bbb18:~# service docker restart
root@bbb18:~# docker run --dns 81.169.148.34 busybox nslookup debian.org
Server:        81.169.148.34
Address:    81.169.148.34:53

Non-authoritative answer:
Name:    debian.org
Address: 130.89.148.77
Name:    debian.org
Address: 128.31.0.62
Name:    debian.org
Address: 149.20.4.15

*** Can't find debian.org: No answer



Am Mittwoch, dem 06.07.2022 um 13:51 +0200 schrieb Michael Wuttke:
Hallo Wolfgan,

wenn Du host und whois auf die DNS Servers: 85.214.7.22 81.169.163.106
81.169.148.34 machst, siest Du, dass das Stratos DNS-Server sind. Nimm
doch die bitte mal und nicht den von google.

Danke & Gruß,
Michael

Am 06.07.22 um 13:35 schrieb huber via BBB-Tech:
Hallo,
Bin weiter am Scheitern.t
Ich kann Docker über apt installieren, das funktioniert problemlos. So hat ein Ticket bei Strato wohl
keine
Aussicht auf Erfolg. Gestern hatte ich mir den Tag um die Ohren gehauen, um Eure Tips durchzugehen,
nachzuvollziehen und nochmal zu probieren. Ich bin da ja ein bischen langsam.
Unter https://docs.bigbluebutton.org/2.5/install.html Troubleshooting steht passend dazu ein Problem beim
Nameserver. Diese Fehlermeldung bekomme ich.
Ubuntu 20.04 uses systemd-resolved, which presents a local caching resolver and registers this at
/etc/resolv.conf. If you get they above error and have a local name server, such as 10.11.12.13, then try
adding it with the hosts resolv.conf.
echo "nameserver 10.11.12.13" > /etc/resolv.conf
Wir hatten am Montag ja auch
nameserver 127.0.0.53V
options edns0 trust-ad
search localdomain

Der Server, bei dem ich 2.5 installieren konnte, gibt
systemd-resolve --status | grep 'DNS Servers' -A2 ausgibt:
        DNS Servers: 8.8.8.8
Link 2 (enp2s0)
    DNS Servers: 85.214.7.22 81.169.163.106 81.169.148.34
Link 3 (enp3s0)
aus. Das tut er, obwohl ich
rm /etc/resolv.conf
echo "nameserver 8.8.8.8" > /etc/resolv.conf
gemacht habe. Das war am Montag auf dem Rechner ja nicht so. Da gabs dann nur mehr die 8.8.8.8
Wenn der Rechner Ubuntu neu drauf hat, geht es.
Das hab ich Gestern vor dem Heimgehen nochmal angeworfen, hat aber auch nicht geklappt. Wo die
Unterschiede zu
dem Einen, der geht sind, weiß ich nicht.
Vermutlich werde ich dann auch zu Hetzner gehen, Strato liegt halt Werbewirksam einen Netzwerkknoten von
unsrer HS entfernt.
Aber vielleicht hat ja jemand noch eine schöne Idee

Nochmal vielen, vielen Dank für Eure Hilfe,
Wolfgang

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/ca463e70-4626-447a-93af-d3fb5f0a5072n%40googlegroups.com.

[Wolfgang Pein]

Maybe it would help to deactivate IPv6?

Maybe Docker is "confused" with IPv4  a n d  IPv6?

:-) Wolfgang P.

To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/ca463e70-4626-447a-93af-d3fb5f0a5072n%40googlegroups.com.