Question on bbb-record-core in BBB1.1

408 views
Skip to first unread message

Insightcollector

unread,
Jan 17, 2017, 8:39:01 AM1/17/17
to BigBlueButton-dev
Hi,

when I have several meetings directly following each other I usually prefer to delay the postprocessing of the video recordings until all meetings are done and the server is not used for a while. In BBB1.0 the processing of recordings was tiggered through monit so I just disabled the monit trigger and that stopped the processing until I decided to manually start it myself.

In BBB1.1 this was changed. Monit is not used anymore but there is a new process bbb-record-core. But when I stop this process through  service bbb-record-core stop   the postprocessing is started anyway. What do I have to do to temporarily delay the post processing until I decide to activate it myself?

Thanks for any help
Oliver

Fred Dixon

unread,
Jan 17, 2017, 10:29:16 AM1/17/17
to BigBlueButton-dev
Hi Oliver,

You need to stop bbb-record-core.timer as well with

$ systemctl stop bbb-record-core.timer

As an aside, the use of systemd in Ubuntu 16.04 really simplified a lot of the startup scripts in BigBlueButton and removed the need for monit.  You can see the contents of bbb-record-core.timer with the following command

$ systemctl cat bbb-record-core.timer
# /usr/lib/systemd/system/bbb-record-core.timer
[Unit]
Description=BigBlueButton record & playback processing timer

[Timer]
OnActiveSec=0
OnUnitInactiveSec=5min

[Install]
WantedBy=timers.target


Regards,... Fred


--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-dev+unsubscribe@googlegroups.com.
To post to this group, send email to bigbluebutton-dev@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.



--
BigBlueButton Developer
@bigbluebutton

Calvin Walton

unread,
Jan 17, 2017, 11:57:31 AM1/17/17
to bigblueb...@googlegroups.com
Hi,

One thing to note is that due to the switch to systemd, it's a lot
simpler to schedule recording processing differently by editing the
timer unit.

Just type "sudo systemctl edit bbb-record-core.timer", then in the text
editor that opens, paste something like the following:

[Timer]
OnActiveSec=
OnUnitInactiveSec=
OnCalendar=*-*-* 00:00:00

The two empty assignments clear the default timer, then the OnCalendar=
entry sets a timer to run at midnight (server local time) every night.
See the 'systemd.timer' and 'systemd.time' man pages for details of
what you can do with this.

Calvin.
--
Calvin Walton <calvin...@kepstin.ca>
Reply all
Reply to author
Forward
0 new messages