Upgrade to 2.3 on bionic from 2.2 on xenial

[mhier]

I am trying to install bbb 2.3 on bionic after upgrade from xenial (with do-release-upgrade). In that case I have an existing file /etc/apt/sources.list.d/nodesource.list but with all lines commented. As a consequence, the script won't download the new file and subsequently fail due to the missing nodejs 12 requirement. Maybe the check whether the file exists should be improved, or the file should be downloaded in any case, if nodejs 12 is not found.

[ffdixon]

We recommend folks start with a new 18.04 server (no prior version of BigBlueButton installed).

We have not tested upgrading BigBlueButton 2.2 -> 2.3 by updating an existing xenial server to bionic. There are a lot of package changes that may conflict with the older version. Recommend, if possible, starting with a new 18.04 server.

[mhier]

Well, it is not easily possible in my case (upgrade from home office). I am not asking for a guarantee for this to work, I am just trying to point out how to improve the script to make such upgrade easier.

Another helpful thing would be to uninstall old BBB 2.2 packages if present, or at least warn about them and ask the user to uninstall them.

Then, the check for the MongoDB PPA key does not work, if the key for MongoDB 3.4 is present but not for 4.0 (I think the check should be done for the key ID like it is done for Xenial).

And somehow the bigbluebutton/support PPA was not activated. I think this is the same issue as with the nodejs PPA.

[jibon57]

@mhier I've written a blog post on it. You can read it from here: How to upgrade BigBlueButton 2.2 to 2.3 (Ubuntu 16.04 to 18.04) but make sure you've read the warnings.

@ffdixon I ain't sure linking some page is allow here or not. If not allow then can delete my comment.

[mhier]

@mhier I've written a blog post on it. You can read it from here: How to upgrade BigBlueButton 2.2 to 2.3 (Ubuntu 16.04 to 18.04) but make sure you've read the warnings.

Thanks, I already managed to do the upgrade. I listed all my trouble points in by post above.

[ffdixon]

Thanks @jibon57 for sharing the link.

[angelaki]

Does install.sh support 2.3 stable (Wooohooo!) already?

[abockhold]

Does install.sh support 2.3 stable (Wooohooo!) already?

Yes, it does since quite some time. Use "-v bionic-230" (but be careful to do this on an Ubuntu 18.04).

[octomike]

We recommend folks start with a new 18.04 server (no prior version of BigBlueButton installed).

Curious, how would I migrate existing rooms/users to the new instance?

[ffdixon]

Sorry, should have put in a link to the docs. See https://docs.bigbluebutton.org/2.2/customize.html#transfer-recordings

[staeglis]

The link is only about transferring recordings and not about transferring the users/rooms /Greenlight) or have I've missed something?

[peterVoisin]

@jibon57 I'm also trying to update my BBB 2.2 on Ubuntu 16.04 to 2.3 on 18.04. By following your procedure, everything seems to be going well but BBB does not work, I get a 404 not found error when launching a room.

[jibon57]

Can you run bbb-conf --check & give output here?

[peterVoisin]

... I use an LXC container and I see in the log Starting BigBlueButton HTML5 service... systemd[1]: Started BigBlueButton HTML5 service. systemd[1]: bbb-html5.service: Failed to reset devices.list: Operation not permitted My problem may be here Sorry I restored a backup, I'll post the bbb-conf --check output when I can try again

[staeglis]

@jibon57 If I follow your guide, I have to delete a lot of files? Are all rooms and relevant settings preserved during the update?

[peterVoisin]

@staeglis The Jibon57 guide doesn't make any changes to your Greenlight instance, you keep all your users / rooms / records. But this is a new install of BBB, you will need to reconfigure your .env with bbb-conf --secret .

[staeglis]

In this case I would prefer doing a clean installation on new virtual machine with migrating the settings / your users / rooms / record. How I can achieve this?

[EmmyGraugans]

Simply copy the recordings and the greenlight to the new instance. Everything else will (and should) be new.

[peterVoisin]

@jibon57

Hello, I tried to update again and I have come to the same issue. I get a 404 not found error when launching a room.

My problem would probably come from the CPU scheduling with lxc container.

journalctl -f -u bbb-html5-*
-- Logs begin at Sat 2021-05-15 09:15:59 CEST. --
May 15 12:06:32 visio systemd[1]: [email protected]: Failed with result 'exit-code'.
May 15 12:06:32 visio systemd[509]: [email protected]: Failed at step SETSCHEDULER spawning /usr/share/meteor/bundle/systemd_start_frontend.sh: Operation not permitted
May 15 12:06:32 visio systemd[1]: [email protected]: Main process exited, code=exited, status=214/SETSCHEDULER
May 15 12:06:32 visio systemd[1]: [email protected]: Failed with result 'exit-code'.
May 15 12:06:32 visio systemd[1]: [email protected]: Main process exited, code=exited, status=214/SETSCHEDULER
May 15 12:06:32 visio systemd[1]: [email protected]: Failed with result 'exit-code'.
May 15 12:06:32 visio systemd[484]: [email protected]: Failed to set up CPU scheduling: Operation not permitted
May 15 12:06:32 visio systemd[484]: [email protected]: Failed at step SETSCHEDULER spawning /usr/share/meteor/bundle/systemd_start_frontend.sh: Operation not permitted
May 15 12:06:32 visio systemd[1]: [email protected]: Main process exited, code=exited, status=214/SETSCHEDULER
May 15 12:06:32 visio systemd[1]: [email protected]: Failed with result 'exit-code'.

[Bschalck]

Hy @peterVoisin , did you solve you problem ?

[peterVoisin]

Hi @Bschalck, yes I solved it. I reinstall a vm with KVM to replace the container(LXC), and transferred my Greenlight and its database. It's less light...

Thanks

[nasilaj]

Thank you for your email. I have tried to install BBB but I cant succeed.

Please help

On Sat, Aug 21, 2021 at 8:55 PM Peter Voisin @.***> wrote:

Hi @Bschalck https://github.com/Bschalck, yes I solved it. I reinstall a vm with KVM to replace the container(LXC), and transferred my Greenlight and its database. It's less light...

Thanks

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bigbluebutton/bbb-install/issues/366#issuecomment-903160933, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVIX3MPPOAOTBWGVPOPV4ALT57ZCRANCNFSM43XHCWRA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .