Hello
I have such a problem: sometimes meetings do not get archived, probably when BBB server is stopped when a meeting was still active.
If I find the meeting ID in /var/log/ and then do:
cd /usr/local/bigbluebutton/core/scripts
ruby archive/archive.rb -m <meeting ID>
then meeting is archived correctly, /var/bigbluebutton/recording/raw/<meeting ID> is created.
The question is how to make BBB archive meetings which are active at the moment when server is shutdown? They are active just because some of participant forgot to leave 1+ hours ago.
I tried to hack like this:
<...>
bbb-conf --stop
<...>
recording_units="$(systemctl list-dependencies --plain bbb-record-core.target | awk '{print $NF}' | tr '\n' ' ')"
systemctl start ${recording_units}
sleep 3m
AWAITING=1
for i in $(seq 1 30)
do
if systemctl is-active -q bbb-rap-archive-worker.service
then sleep 1m
else AWAITING=0 && break
fi
done
if [ "$AWAITING" = 1 ]; then
echo "XXX bbb-rap-archive-worker.service has been active for more than 30 mins, killing it!"
systemctl stop "$recording_units"
fi
but this did not solve the problem. Running
systemctl start bbb-record-core.target bbb-rap-archive-worker.service bbb-rap-events-worker.service bbb-rap-process-worker.service bbb-rap-publish-worker.service bbb-rap-sanity-worker.service
does not trigger archiving of such recordings.
Please help to understand how to better handle stopping BBB when there are active meetings. Thanks!