Cant transfer old records about scalelite HOT 38 CLOSED

Thanks! is there a way to track the state of the records? scalelite side

from scalelite.

Change

( cd "$scripts_dir" && sudo -n -u bigbluebutton ./post_publish/scalelite_post_publish.rb -m "$record_id" )

to

( cd "$scripts_dir" && sudo -n -u bigbluebutton ruby ./post_publish/scalelite_post_publish.rb -m "$record_id" )

from scalelite.

@IamLuksha I solved with this

#90

but now the recordings are not listing in the greenligh, know why?

from scalelite.

Done!
now i get
Permission denied, how can I change that? thanks
http://prntscr.com/rwvrbe

from scalelite.

Change

( cd "$scripts_dir" && sudo -n -u bigbluebutton ./post_publish/scalelite_post_publish.rb -m "$record_id" )

to

( cd "$scripts_dir" && sudo -n -u bigbluebutton ruby ./post_publish/scalelite_post_publish.rb -m "$record_id" )

@kepstin Can you take a look? the main script here has that mistake. Thanks
https://github.com/blindsidenetworks/scalelite/blob/master/bigbluebutton/scalelite_batch_import.sh

from scalelite.

@agustinmono Have you done everything here?
https://github.com/blindsidenetworks/scalelite/blob/master/sharedvolume-README.md

from scalelite.

Yes @IamLuksha
All permissions set
http://prntscr.com/rwwd76

, I have 2 concerns .

1- I Followed this instuctive to create the NFS, configuring the Scalelite Server as NFS Server, and each BBB Server as NFS Client Machine, its that ok?

2- here https://github.com/blindsidenetworks/scalelite/blob/master/bigbluebutton/README.md#shared-filesystem-eg-nfs-mount says

" Ensure that the bigbluebutton user has permission to enter and write to the spool directory."

How can I test that? in case that bigbluebutton doesnt has permission, how can I give permissions to him.

Thanks a lot

from scalelite.

@agustinmono
There is an example setup via ssh.
If you need to configure the nfs server not via ssh, here is an example
https://www.tecmint.com/how-to-setup-nfs-server-in-linux/

All permissions are here.
https://github.com/blindsidenetworks/scalelite/blob/master/sharedvolume-README.md

You can check the permission by writing a file from the user bigbluebutton

from scalelite.

I did all of that, but when I try to create a file here it says permission denied

nano /mnt/scalelite-recordings/var/bigbluebutton/spool/test.txt
http://prntscr.com/rwwq92

Permissions :

http://prntscr.com/rwwqhq

http://prntscr.com/rwwu15

I did all that documentation says.. what im missing ?? i dont understand

If i do:
cat /etc/passwd

i get
[...]
bigbluebutton:x:998:998:bigbluebutton:/home/bigbluebutton:/bin/false
[...]

from scalelite.

@agustinmono

If you do:
getent group

You should receive
scalelite-spool:x:2000:bigbluebutton

and your permissions are correct
I have the same and everything works

from scalelite.

So why i cant write a file?

how can i write a file as bigbluebutton ? currently Im as root user, maybe is that?

maybe my /etc/exports/ are wrong

/mnt/scalelite-recordings MY.CLIENT.IP(rw,sync,no_subtree_check)

from scalelite.

for instance

It was

root@bbb-sl-pool1:/# ll /mnt/scalelite-recordings/var/bigbluebutton/spool/    
total 8
drwxrwxr-x 2 bbb-server scalelite-spool 4096 Apr 10 21:10 ./
drwxr-xr-x 6 root       root            4096 Apr  8 22:40 ../

I created a file from root user

root@bbb-sl-pool1:/# touch /mnt/scalelite-recordings/var/bigbluebutton/spool/111                         
root@bbb-sl-pool1:/# ll /mnt/scalelite-recordings/var/bigbluebutton/spool/      
total 8
drwxrwxr-x 2 bbb-server scalelite-spool 4096 Apr 10 21:11 ./
drwxr-xr-x 6 root       root            4096 Apr  8 22:40 ../
-rw-r--r-- 1 root       root               0 Apr 10 21:11 111

I created a file from BBB user

root@bbb-sl-pool1:/# sudo -n -u bigbluebutton touch /mnt/scalelite-recordings/var/bigbluebutton/spool/222
root@bbb-sl-pool1:/# ll /mnt/scalelite-recordings/var/bigbluebutton/spool/                               
total 8
drwxrwxr-x 2 bbb-server    scalelite-spool 4096 Apr 10 21:11 ./
drwxr-xr-x 6 root          root            4096 Apr  8 22:40 ../
-rw-r--r-- 1 root          root               0 Apr 10 21:11 111
-rw-r--r-- 1 bigbluebutton bigbluebutton      0 Apr 10 21:11 222

from scalelite.

I executed the same commands and I get permission denied, can you share with me your
/etc/exports/ file config?

touch: setting times of '/mnt/scalelite-recordings/var/bigbluebutton/spool/': Permission denied

of course without the IP, just to check if this its OK:

/mnt/scalelite-recordings MY_IP(rw,sync,no_subtree_check)

from scalelite.

No problem

But you see the folders, so this config is right for you

with no_subtree_check thinks for a long time and nothing happens

/mnt/scalelite-recordings IP_ScaleLite (rw,sync,no_root_squash)
/mnt/scalelite-recordings IP_BBB_server_1 (rw,sync,no_root_squash)
.........
/mnt/scalelite-recordings  IP_BBB_server_2 (rw,sync,no_root_squash)

from scalelite.

exportfs: /etc/exports [6]: Neither 'subtree_check' or 'no_subtree_check' specified for export "IP:/mnt/scalelite-recordings". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x

from scalelite.

what have you done
Is there a space between IP and ()? If yes. Take it away

from scalelite.

No i dont have any space

/mnt/scalelite-recordings 217.79.240.42(rw,sync,no_root_squash)

After that i did

exportfs -r

from scalelite.

touch: setting times of '/mnt/scalelite-recordings/var/bigbluebutton/spool/': Permission denied

Still getting that, i really dont know whats wrong, just a quick question

Your nfs server... is the BigblueButton or the Scalelite?

I have the Scalelite ad NFS Server and each Bigbluebutton is a client

from scalelite.

I am using a standalone server under NFS on the local network.
SL and BBB are client

But this should not affect

from scalelite.

Any idea? really dont know whats wrong

from scalelite.

@agustinmono
I have no ideas either
If I come up with something I will write

from scalelite.

Thanks so much for your time, really appreciate the help

from scalelite.

@agustinmono
I am very glad that you have solved the problem.

I do not use Greenlight. I use Moodle to authorize users. To monitor the rallies on the servers I wrote a simple site

from scalelite.

@agustinmono
Yes
You can use the BBB API
https://docs.bigbluebutton.org/dev/api.html#getrecordings

from scalelite.

Change

( cd "$scripts_dir" && sudo -n -u bigbluebutton ./post_publish/scalelite_post_publish.rb -m "$record_id" )

to

( cd "$scripts_dir" && sudo -n -u bigbluebutton ruby ./post_publish/scalelite_post_publish.rb -m "$record_id" )

@IamLuksha @farhatahmad

after suggested changes as above iam getting the following error https://prnt.sc/tivr2r
Please help

from scalelite.

maybe because ?

/mnt/scalelite-recordings/var/bigbluebutton/ failed: no such file or directory (2)

from scalelite.

has per the the docs i have created that directory on the scalelite server. Can you please let me know what iam missing here?

from scalelite.

have you mounted this directory on bbb server?
check if this directory exists on bbb server

from scalelite.

Firstly thanks for your help. i created a directory as per your suggestion. but ran into a different error
https://prnt.sc/tiwldc

from scalelite.

permission denied...

did you do on the BBB server?

#Create a new group with GID 2000
groupadd -g 2000 scalelite-spool
#Add the bigbluebutton user to the group
usermod -a -G scalelite-spool bigbluebutton

from scalelite.

@IamLuksha yes i did i also had gone through this thread as well .
i ran command getent group
https://prnt.sc/tixl2g

from scalelite.

Hi @IamLuksha
Finally i managed to solve it. iam getting the following result. I hope its the desired one.
https://prnt.sc/tj31c2

from scalelite.

@rexon07 what was wrong?

from scalelite.

scalelite-recording-importer works?
Did you create it?

from scalelite.

@IamLuksha i have not yet created it. I went through it . I guess what i have done is right.

from scalelite.

i just changed the owner to bigbluebutton for this directory /mnt/scalelite-recordings/var/bigbluebutton/spool

from scalelite.

@rexon07 read this readme

from scalelite.

@IamLuksha @farhatahmad Hi,
i continued the process of deploying scalelite docker containers. after fixing most of the issues. i got service running But still there is an error :

● scalelite-api.service - Scalelite API
Loaded: loaded (/etc/systemd/system/scalelite-api.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-07-20 11:07:51 CEST; 1s ago
Process: 3267 ExecStart=/usr/bin/docker run --name scalelite-api --env-file /etc/default/scalelite --network scalelite --mount type=bind,source=${SCALELITE_RECORDING_
Process: 3240 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-api (code=exited, status=0/SUCCESS)
Process: 3219 ExecStartPre=/usr/bin/docker rm scalelite-api (code=exited, status=0/SUCCESS)
Process: 3193 ExecStartPre=/usr/bin/docker kill scalelite-api (code=exited, status=1/FAILURE)
Main PID: 3267 (code=exited, status=1/FAILURE)

Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/puma-4.3.5/lib/puma/configuration.rb:246:in app' Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/puma-4.3.5/lib/puma/runner.rb:155:in load_and_bind'
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/puma-4.3.5/lib/puma/single.rb:98:in run' Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/puma-4.3.5/lib/puma/launcher.rb:172:in run'
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/puma-4.3.5/lib/puma/cli.rb:80:in run' Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/puma-4.3.5/bin/puma:10:in <top (required)>'
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/bin/puma:23:in load' Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3267]: /srv/scalelite/vendor/bundle/ruby/2.6.0/bin/puma:23:in <top (required)>'
Jul 20 11:07:51 Ubuntu-1804-bionic-64-minimal systemd[1]: scalelite-api.service: Main process exited, code=exited, status=1/FAILURE
Jul 20 11:07:51 Ubuntu-1804-bionic-64-minimal systemd[1]: scalelite-api.service: Failed with result 'exit-code'.

● scalelite-nginx.service - Scalelite Nginx
Loaded: loaded (/etc/systemd/system/scalelite-nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-07-20 11:07:48 CEST; 4s ago
Process: 3319 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-nginx (code=exited, status=0/SUCCESS)
Process: 3306 ExecStartPre=/usr/bin/docker rm scalelite-nginx (code=exited, status=0/SUCCESS)
Process: 3268 ExecStartPre=/usr/bin/docker kill scalelite-nginx (code=exited, status=1/FAILURE)
Main PID: 3428 (docker)
Tasks: 13 (limit: 4915)
CGroup: /system.slice/scalelite-nginx.service
└─3428 /usr/bin/docker run --name scalelite-nginx --env-file /etc/default/scalelite --network scalelite --publish 80:80 --publish 443:443 --mount type=bind,s

Jul 20 11:07:48 Ubuntu-1804-bionic-64-minimal docker[3319]: v1-nginx: Pulling from blindsidenetwks/scalelite
Jul 20 11:07:48 Ubuntu-1804-bionic-64-minimal docker[3319]: Digest: sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxx
Jul 20 11:07:48 Ubuntu-1804-bionic-64-minimal docker[3319]: Status: Image is up to date for blindsidenetwks/scalelite:v1-nginx
Jul 20 11:07:48 Ubuntu-1804-bionic-64-minimal docker[3319]: docker.io/blindsidenetwks/scalelite:v1-nginx
Jul 20 11:07:48 Ubuntu-1804-bionic-64-minimal systemd[1]: Started Scalelite Nginx.
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3428]: Startup script was run as init, re-execing using tini.
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3428]: Generating templated nginx configuration...
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3428]: Using SSL configuration template.
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3428]: Starting nginx periodic reload process...
Jul 20 11:07:50 Ubuntu-1804-bionic-64-minimal docker[3428]: Starting nginx...

from scalelite.