Upgrading from 16.04 to 18.04 and upgrading of BBB fails

[JYPDWhite]

Hello,

I recently upgraded the Ubuntu version from 16.04 to 18.04 and after that I ran ./bbb-install.sh -v bionic-23 -s meeting.example.de -e [email protected] -w -g

But the upgrade of BBB fails with this error message bbb-install: Did not detect nodejs 12.x candidate for installation. After that I ran an apt update && apt dist-upgrade and updatet remaining packages. But after a reboot the bbb-install call still fails with the same error message. Can anyone help?

This is the full output of bbb-install

root@streamy /home/white # ./bbb-install.sh -v bionic-23 -s meeting.example.de -e [email protected] -w -g
Hit:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Hit:3 http://ppa.launchpad.net/bigbluebutton/support/ubuntu bionic InRelease
Hit:4 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                                                                                                       
Hit:5 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease                                                                                                                                     
Hit:6 http://ppa.launchpad.net/libreoffice/ppa/ubuntu bionic InRelease                                                                                                             
Hit:7 http://ppa.launchpad.net/rmescandon/yq/ubuntu bionic InRelease                                                                                                               
Hit:8 https://ubuntu.bigbluebutton.org/bionic-23 bigbluebutton-bionic InRelease                            
Fetched 88.7 kB in 1s (80.3 kB/s)            
Reading package lists... Done
Warning: apt-key output should not be parsed (stdout is not a terminal)
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
LESSCLOSE=/usr/bin/lesspipe %s %s
LANG=en_US.UTF-8
SUDO_GID=1000
OLDPWD=/root
USERNAME=root
SUDO_COMMAND=/bin/bash
USER=root
PWD=/home/white
HOME=/root
SUDO_USER=white
DEBIAN_FRONTEND=noninteractive
SUDO_UID=1000
MAIL=/var/mail/root
TERM=screen.xterm-256color
SHELL=/bin/bash
SHLVL=2
LOGNAME=root
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
LESSOPEN=| /usr/bin/lesspipe %s
_=/usr/bin/env
'universe' distribution component is already enabled for all sources.
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
Warning: apt-key output should not be parsed (stdout is not a terminal)
bbb-install: Did not detect nodejs 12.x candidate for installation

It seems as there is no nodejs12

root@streamy /home/white # apt-cache madison nodejs
    nodejs | 8.10.0~dfsg-2ubuntu0.4 | http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages
    nodejs | 8.10.0~dfsg-2ubuntu0.2 | http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages
    nodejs | 8.10.0~dfsg-2 | http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

Regards White

[GhaziTriki]

Hi @JYPDWhite,

This is not recommended to do so. Instead please start from a fresh server. Are you able to install BigBlueButton on a fresh server?

[JYPDWhite]

Hi @GhaziTriki,

thanks for the information I'm currently setting the server up with 18.04 and than I will try again. Can you give me an advice should I run the bbb-setup and after the installation finished copy back my user configs etc. (saved recordings, user database, sip configuration)? or should I copy them back before running bbb-setup?

[JYPDWhite]

Okay i managed to install it after that I replace the /root/greenlight folder with my old folder and changed the .env values (SECRET_KEY_BASE, BIGBLUEBUTTON_ENDPOINT, BIGBLUEBUTTON_SECRET) to the values of the new installation. So all the users and rooms are restored --> success so far. But I can't get the recording recovered I followed the steps mentioned here: https://docs.bigbluebutton.org/admin/customize.html#transfer-published-recordings-from-another-server but without success ( the Recording list of the organistation is empty)

[DocEpsilon]

Hi @JYPDWhite,

This is not recommended to do so. Instead please start from a fresh server. Are you able to install BigBlueButton on a fresh server?

Wow. Can't believe that this should be a prerequisite? That is just so far from any reality. People won't do clean installs of their whole environments just to make an upgrade to BBB. We are also hosting other stuff like websites etc. And not everyone uses VMs or Docker to run their BBB-Server in a sandbox (which is not recommended anyway, by the way.)

[RokkuCode]

Don't do that. BBB is intended to run on its own instance and not hosting dozens of other services in the same vm. vms or cloud insances are cheap today. no need for building big piles of services into one instance. reinstalling a bbb and migrating the needed files like recordings etc. are far more easier and scriptable instead of dist-upgrading. to your self a favor and use bbb on its own instance, a reinstalling / migration instance temporarily for dist-upgrades and you have no stress at the end.

[GhaziTriki]

BigBlueButton now works on Ubuntu 20.04