Update to 2.3.0 from former Dev

320 views
Skip to first unread message

Matthias Grähn

unread,
Apr 30, 2021, 4:42:54 AM4/30/21
to BigBlueButton-Setup
Hi,

great to see that the 2.3 is finally released and this a couple of hours after upgrading to 2.3-rc2 :-) Appreciate your work to bring all this components working together.

What ist the recommended way to upgrade to 2.3. just use the package-manager of ubuntu or do I have to change repositories as well?

Thanks and best regards
Matthias


Martin Thomas Schrott

unread,
Apr 30, 2021, 7:53:49 AM4/30/21
to bigbluebu...@googlegroups.com, Matthias Grähn

as usual just execute the bbb-install shell script as you installed the rc2 with. (hopefully)

it always is better to install using the shell script.


cheers

Martin

EDU-Werkstatt GmbH    |   Am Friedrichshain 22   |   10407 Berlin                                           
Geschäftsführer: David Hauptmann, Andreas Grähn
Registergericht: Amtsgericht Berlin (Charlottenburg)   |   HRB 146423                                        
Telefon: +4930 - 224 1199 - 0   |   E-Mail: in...@edu-werkstatt.de
--
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/ead3dc9c-82b7-4528-9754-5aaedd5ac7b2n%40googlegroups.com.

Fred Dixon

unread,
Apr 30, 2021, 8:13:46 AM4/30/21
to BigBlueButton-.
Hi Martin,

We recommend using the `bbb-install.sh` script to install/upgrade with 2.3.

Regards,... Fred



--
BigBlueButton Developer

Like BigBlueButton?  Tweet us at @bigbluebutton

Martin Thomas Schrott

unread,
Apr 30, 2021, 8:15:36 AM4/30/21
to bigbluebu...@googlegroups.com, Fred Dixon

Am 30.04.2021 um 14:13 schrieb Fred Dixon:
> Hi Martin,
>
> We recommend using the `bbb-install.sh` script to install/upgrade with
> 2.3.
>

isn't that what I said ? ;-)

cheers


Fred Dixon

unread,
Apr 30, 2021, 8:16:31 AM4/30/21
to Martin Thomas Schrott, BigBlueButton-.
Exactly! :-)

Cheers,... Fred

Matthias Grähn

unread,
Apr 30, 2021, 9:53:52 AM4/30/21
to bigbluebu...@googlegroups.com
yes I used the script, ok then I will use it yust with the bionic-230. Ok I see I already used this before so the dev disappeared after the release candidates were available.

Thanks


--
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/42-oZYcywLA/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/CAOeuy5N8-KP%2BmySk22FqVuq-NccyEkXR%3DCi5J6Qr%2B2PjCkutYQ%40mail.gmail.com.

Marco Cassisa

unread,
Apr 30, 2021, 10:03:32 AM4/30/21
to BigBlueButton-Setup
I did 
apt upgrade  on ubuntu 18.04 where 2.3-dev was installed
the process stumbled upon an error (see below):  does it depends on using apt upgrade? So, should I have used bbb-install.sh? How to fix the process?
Thanks
Marco

46 info run bbb-web...@2.5.0-beta.2 postinstall  cd node_modules/sip.js/src/Grammar && mkdir -p dist && pegjs --extra-options-file peg.json src/Grammar.pegjs dist/Grammar.js
47 info run bbb-web...@2.5.0-beta.2 postinstall { code: 1, signal: null }
48 timing command:rebuild Completed in 211ms
49 verbose stack Error: command failed
49 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
49 verbose stack     at ChildProcess.emit (node:events:365:28)
49 verbose stack     at maybeClose (node:internal/child_process:1067:16)
49 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
50 verbose pkgid bbb-web...@2.5.0-beta.2
51 verbose cwd /usr/local/bigbluebutton/bbb-webrtc-sfu
52 verbose Linux 4.15.0-142-generic
53 verbose argv "/usr/bin/node" "/usr/bin/npm" "rebuild"
54 verbose node v16.0.0
55 verbose npm  v7.10.0
56 error code 1
57 error path /usr/local/bigbluebutton/bbb-webrtc-sfu
58 error command failed
59 error command sh -c cd node_modules/sip.js/src/Grammar && mkdir -p dist && pegjs --extra-options-file peg.json src/Grammar.pegjs dist/Grammar.js
60 error /usr/local/bigbluebutton/bbb-webrtc-sfu/node_modules/pegjs/bin/pegjs:54
60 error   util.error(message);
60 error        ^
60 error
60 error TypeError: util.error is not a function
60 error     at abort (/usr/local/bigbluebutton/bbb-webrtc-sfu/node_modules/pegjs/bin/pegjs:54:8)
60 error     at WriteStream.<anonymous> (/usr/local/bigbluebutton/bbb-webrtc-sfu/node_modules/pegjs/bin/pegjs:235:7)
60 error     at WriteStream.emit (node:events:365:28)
60 error     at emitErrorNT (node:internal/streams/destroy:193:8)
60 error     at emitErrorCloseNT (node:internal/streams/destroy:158:3)
60 error     at processTicksAndRejections (node:internal/process/task_queues:83:21)


Lorenz Schori

unread,
Apr 30, 2021, 10:15:15 AM4/30/21
to Marco Cassisa, bigbluebu...@googlegroups.com
Hi Marco,

On Fri, 30 Apr 2021 07:03:32 -0700 (PDT)
Marco Cassisa <marco....@gmail.com> wrote:

> 54 verbose node v16.0.0

Please install node 12 instead of 16 (documented here:
https://docs.bigbluebutton.org/dev/dev23.html).

Cheers,
Lorenz

Marco Cassisa

unread,
Apr 30, 2021, 10:25:59 AM4/30/21
to BigBlueButton-Setup
Thank you for the help
if I try to install the repository for v. 12

curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -

I got

## Confirming "bionic" is supported...


## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 12.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_12.x bionic main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_12.x bionic main' >> /etc/apt/sources.list.d/nodesource.list

ok, 12.x is going to be considered...
BUT then the process runs into errors again...

apt-get install -y nodejs
Reading package lists... Done
Building dependency tree       
Reading state information... Done
nodejs is already the newest version (16.0.0-1nodesource1).
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up bbb-record-core (1:2.3.0-31) ...
ERROR:  While executing gem ... (Gem::RemoteFetcher::UnknownHostError)
dpkg: error processing package bbb-record-core (--configure):
 installed bbb-record-core package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of bbb-libreoffice-docker:
 bbb-libreoffice-docker depends on bbb-record-core; however:
  Package bbb-record-core is not configured yet.

dpkg: error processing package bbb-libreoffice-docker (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bbb-web:
 bbb-web depends on bbb-libreoffice-docker; however:
  Package bbb-libreoffice-docker is not configured yet.

dpkg: error processing package bbb-web (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bbb-html5:
 bbb-html5 depends on bbb-web; however:
  Package bbb-web is not configured yet.

dpkg: error processing package bbb-html5 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of bbb-config:
 bbb-config depends on bbb-html5; however:
  Package bbb-html5 is not configured yet.

dpkg: error processing package bbb-configNo apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                                                                   No apport report written because the error message indicates its a followup error from a previous failure.
                             No apport report written because MaxReports is reached already
                                                                                           No apport report written because MaxReports is reached already
                                                                                                                                                          (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 bbb-record-core
 bbb-libreoffice-docker
 bbb-web
 bbb-html5
 bbb-config
E: Sub-process /usr/bin/dpkg returned an error code (1)

Lorenz Schori

unread,
Apr 30, 2021, 10:37:22 AM4/30/21
to Marco Cassisa, bigbluebu...@googlegroups.com
Hi Marco,

On Fri, 30 Apr 2021 07:25:59 -0700 (PDT)
Marco Cassisa <marco....@gmail.com> wrote:

> [...]
> nodejs is already the newest version (16.0.0-1nodesource1).
> 5 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> [...]

Please *remove* node 16 before attempting to install node 12:

sudo apt-get remove nodejs

Cheers,
Lorenz

Marco Cassisa

unread,
Apr 30, 2021, 10:46:54 AM4/30/21
to BigBlueButton-Setup
Thank you for suggesting the way, Lorenz.
If I apt remove nodejs
I also
The following packages will be REMOVED:
  bbb-config bbb-html5 bbb-webrtc-sfu bigbluebutton nodejs

and I fear to broke my installation.
Should I go further? and then should I run bbb-install.sh again?
Thank you again for bearing me fears

Marco
PS: How did it come that nodjs 16 is installed? 

Lorenz Schori

unread,
Apr 30, 2021, 11:31:43 AM4/30/21
to Marco Cassisa, bigbluebu...@googlegroups.com
Hi Marco,

On Fri, 30 Apr 2021 07:46:53 -0700 (PDT)
Marco Cassisa <marco....@gmail.com> wrote:

> Thank you for suggesting the way, Lorenz.
> If I apt remove nodejs
> I also
> The following packages will be REMOVED:
> bbb-config bbb-html5 bbb-webrtc-sfu bigbluebutton nodejs
>
> and I fear to broke my installation.

Ah, my bad. Instead of removing, you also can downgrade:

sudo apt-get install nodejs=12.*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '12.22.1-1nodesource1' (Node Source:deb.nodesource.com [amd64]) for 'nodejs'
The following packages will be DOWNGRADED:
nodejs
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 9 not upgraded.
Need to get 18.2 MB of archives.
After this operation, 25.6 MB disk space will be freed.
Do you want to continue? [Y/n] y

> Should I go further? and then should I run bbb-install.sh again?

Yes, run bbb-install.sh again after fixing node.

> [...]
> PS: How did it come that nodjs 16 is installed?

The bbb-install.sh does hard-code node 12 (on bionic). If the server
has been used for some different application before, then that might be
an explanation. If you installed from scratch to a fresh server, then I
really do not have any idea on how node 16 could possibly find its way
into your sources.list.

Cheers,
Lorenz

Marco Cassisa

unread,
Apr 30, 2021, 12:29:04 PM4/30/21
to BigBlueButton-Setup
Thanks again Lorenz for taking care of my case


>Il giorno venerdì 30 aprile 2021 alle 17:31:43 UTC+2 lorenz...@gmail.com ha scritto:
>Hi Marco,
>
>
>sudo apt-get install nodejs=12.*

>
>Yes, run bbb-install.sh again after fixing node.
>
>> [...]
>> PS: How did it come that nodjs 16 is installed?

after downgrading, the server started to prefer to use ipv6 and couldn't solve addresses (I can't figure out why).
I somehow managed to make ipv4 preferred appending 
precedence ::ffff:0:0/96  100
to /etc/gai.conf

It may be useful for others, maybe
Apparently it worked even without running install.sh
Have a nice day!

Marco

Reply all
Reply to author
Forward
0 new messages