On Sat, 6 Mar 2021 12:45:41 +0100
Florian Zieboll via Dng <dng@???> wrote:

> On Sat, 6 Mar 2021 04:27:21 -0500
> Steve Litt <slitt@???> wrote:
>
> > >I /had/ Jitsi Meet running (w/o local turn server and jigasi) on a
> > >Odroid XU-4 with 2GB RAM. Tested with up to four participants and
> > >running quite well. Downside: The reserved memory of the
> > >videobridge is configured under /usr/share/ and thus is not
> > >update-proof.
> >
> > chattr +i whatever_file
>
> For me it seems to be more reasonable to 'apt-mark hold' the
> videobridge and keep the manual change in mind - particularly as the
> service just fails to start and its log points straight to this very
> issue when the file gets reverted to its original state.
>
> BTW, I just tried it: When I 'chattr +i' a file to be updated, the
> whole update (resp. reinstall in this test) fails and leaves /all/
> updated packages unconfigured.

I just reinstalled jitsi-meet and found a more elegant solution resp.
the original cause for the VIDEOBRIDGE_MAX_MEMORY issue: The sysv init
script does 'include /etc/jitsi/videobridge/config' but then it doesn't
export the variables defined there. Simply adding the line 'export
VIDEOBRIDGE_MAX_MEMORY' at the beginning of the init script's 'start()'
function solves the problem. Additional bonus: The init script can be
'chattr +i'ed without disturbing the update process.

I ran into some another trouble with the videobridge, which may or may
not have existed in my previous installation. Maybe I just didn't push
hard enough for it to appear: When I dis- and re-connect several times
in short intervals, the videobridge "goes down" for a while and needs
some minutes to be available to jicofo again. If somebody has a quick
hint on this, I'd be happy - otherwise I'll come back when I see more.
Noteworthy is that both, videobridge and jicofo, run with 'MAX_MEMORY'
of 512m.

libre Grüße,
Florian