You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running the .deb package updates on an ubuntu/debian system the post install scripts run chown bigbluebutton:bigbluebutton -R on the main top level directory of the bbb installation. This chown then gets run 2 more times on the recording/ and published/ subdirectories.
This chown post install script is present in at least 2 of the deb packages making it run the 3 chowns twice. It only needs 1 chown on the main bbb install directory on initial install, why would it need to also do the internal subdirectories also?
The post install scripts are these file:
/var/lib/dpkg/info/bbb-config.postinst
/var/lib/dpkg/info/bbb-record-core.postinst
/var/lib/dpkg/info/bbb-playback-presentation.postinst
/var/lib/dpkg/info/bbb-webrtc-sfu.postinst
Firewall and IP address type
Server is stand alone, has its own IP and domain.
Console output
We updated yesterday to the following pakage versions that have this post-install script:
apt list --installed | grep bbb
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
bbb-apps-akka/unknown,now 2.5-51 all [installed,automatic]
bbb-config/unknown,now 1:2.5-74 amd64 [installed,automatic]
bbb-etherpad/unknown,now 1:2.5-11 amd64 [installed,automatic]
bbb-freeswitch-core/unknown,now 2:2.5-18 amd64 [installed,automatic]
bbb-freeswitch-sounds/unknown,now 1:2.5-8 amd64 [installed,automatic]
bbb-fsesl-akka/unknown,now 2.5-40 all [installed,automatic]
bbb-html5/unknown,now 1:2.5-2913 amd64 [installed,automatic]
bbb-learning-dashboard/unknown,now 1:2.5-23 amd64 [installed,automatic]
bbb-libreoffice-docker/unknown,now 1:2.5-9 amd64 [installed,automatic]
bbb-mkclean/unknown,now 1:2.5-5 amd64 [installed,automatic]
bbb-pads/unknown,now 1:2.5-14 amd64 [installed,automatic]
bbb-playback-presentation/unknown,now 1:2.5-11 amd64 [installed,automatic]
bbb-playback/unknown,now 1:2.5-9 amd64 [installed,automatic]
bbb-record-core/unknown,now 1:2.5-38 amd64 [installed,automatic]
bbb-web/unknown,now 1:2.5-78 amd64 [installed,automatic]
bbb-webrtc-sfu/unknown,now 1:2.5-33 amd64 [installed,automatic]
libopusenc0/focal,now 0.2.1-1bbb2 amd64 [installed,automatic]
yq/focal,now 3.4.1bbb1 amd64 [installed]
Additional context
The problem with these cascading chowns shows up when you have several 100 GB of recordings and any apt upgrade then takes, in our case, 2h+ due to these chowns. If you already do a chown on the root directory of BBB why do you then need separately another set of chowns on the internal directories?
The second point, if bbb was already installed why does it need to do these chowns at all?
We have the following repo active:
cat /etc/apt/sources.list.d/bigbluebutton.list
deb https://ubuntu.bigbluebutton.org/focal-250 bigbluebutton-focal main
The text was updated successfully, but these errors were encountered:
Describe the bug
When running the .deb package updates on an ubuntu/debian system the post install scripts run chown bigbluebutton:bigbluebutton -R on the main top level directory of the bbb installation. This chown then gets run 2 more times on the recording/ and published/ subdirectories.
This chown post install script is present in at least 2 of the deb packages making it run the 3 chowns twice. It only needs 1 chown on the main bbb install directory on initial install, why would it need to also do the internal subdirectories also?
The post install scripts are these file:
/var/lib/dpkg/info/bbb-config.postinst
/var/lib/dpkg/info/bbb-record-core.postinst
/var/lib/dpkg/info/bbb-playback-presentation.postinst
/var/lib/dpkg/info/bbb-webrtc-sfu.postinst
Installation type
The installation is done with the install script like so:
wget -qO- https://ubuntu.bigbluebutton.org/bbb-install-2.5.sh | bash -s -- -v focal-250 -s some.domain.com -e some@email.com -g -d
Firewall and IP address type
Server is stand alone, has its own IP and domain.
Console output
We updated yesterday to the following pakage versions that have this post-install script:
Additional context
The problem with these cascading chowns shows up when you have several 100 GB of recordings and any apt upgrade then takes, in our case, 2h+ due to these chowns. If you already do a chown on the root directory of BBB why do you then need separately another set of chowns on the internal directories?
The second point, if bbb was already installed why does it need to do these chowns at all?
We have the following repo active:
The text was updated successfully, but these errors were encountered: