scalelite installation from SCRATCH - stuck somewhere
1,192 views
Skip to first unread message
rschu...@gmail.com
Aug 23, 2020, 8:30:54 PM8/23/20
to BigBlueButton-Setup
OK, I tried the lazy way and failed, so i tried the long run .. but failed again.
I will show you MY way and maybe someone is willing to help (or immediately knows what my error is.
I used the bbb-manual and a document I found here: https://events.ubuntunet.net/event/29/attachments/201/246/Installing_and_Scaling_BBB.pdf
Ich suche zur Not auch deutschsprachigen kommerziellen Support um das zum Laufen zu bekommen.
********************************************************************************
4 Machines with enough ressources:
Basic Install Ubuntu 16.04 LTS for BBB, Greenlight and 18.04 LTS for scaler
2 running instances of BBB
Hostnames: bbb1, bbb2
DNS-Names: tele.domain.com, tele2.domain.com
Basic Install Ubuntu 16.04 LTS for BBB, Greenlight and 18.04 LTS for scaler
2 running instances of BBB
Hostnames: bbb1, bbb2
DNS-Names: tele.domain.com, tele2.domain.com
1 host für greenlight:
Hostname: conf
DNS-Name: conf.domain.com
1 host for the scalelite/redis/postgrsql stuff:
Hostname: scaler
DNS-Name for IP: scaler.domain.com
******************************************************************************
Hostname: scaler
DNS-Name for IP: scaler.domain.com
******************************************************************************
Following the first step - setup of NFS:
On bbb1,bbb2:
# 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
On scaler:
sudo apt install nfs-kernel-server
vi /etc/exports
add line: /mnt/scalelite-recordings *(rw,sync,no_root_squash)
# Create the spool directory for recording transfer from BigBlueButton
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/spool
chown 1000:2000 /mnt/scalelite-recordings/var/bigbluebutton/spool
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/spool
# Create the temporary (working) directory for recording import
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/recording/scalelite
chown 1000:1000 /mnt/scalelite-recordings/var/bigbluebutton/recording/scalelite
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/recording/scalelite
# Create the directory for published recordings
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/published
chown 1000:1000 /mnt/scalelite-recordings/var/bigbluebutton/published
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/published
# Create the directory for unpublished recordings
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/unpublished
chown 1000:1000 /mnt/scalelite-recordings/var/bigbluebutton/unpublished
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/unpublished
sudo systemctl start nfs-kernel-server.service
At this point NFS should be complete except configuring recording importer
***************
Postgres installation
***************
sudo apt-get install postgresql postgresql-contrib
We need a user and a DB so:
su postgres
createuser scalelite
createdb scalelite
QUESTION: Do I need to setup this user with a password?( I dont think so because we run a localhost installation)
In postesql.conf die listen adressen freigeben
vi /etc/postgresql/10/main/postgresql.conf
listen_addresses = ‘*'
vi /etc/postgresql/10/main/postgresql.conf
host scalelite scalelite 172.18.0.2/32 trust
host scalelite scalelite 172.18.0.3/32 trust
*************
Setup redis
*************
I found a document about the redis installation but again I am uncertain what to do.
I can install and autoenable redis using the below commands (it will *NOT* work from default repository for unknown reason)
sudo add-apt-repository ppa:chris-lea/redis-server
sudo apt-get update
sudo apt -install redis-server
sudo systemctl enable redis-server.service
I did configure Redis by editing
# 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
On scaler:
sudo apt install nfs-kernel-server
vi /etc/exports
add line: /mnt/scalelite-recordings *(rw,sync,no_root_squash)
# Create the spool directory for recording transfer from BigBlueButton
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/spool
chown 1000:2000 /mnt/scalelite-recordings/var/bigbluebutton/spool
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/spool
# Create the temporary (working) directory for recording import
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/recording/scalelite
chown 1000:1000 /mnt/scalelite-recordings/var/bigbluebutton/recording/scalelite
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/recording/scalelite
# Create the directory for published recordings
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/published
chown 1000:1000 /mnt/scalelite-recordings/var/bigbluebutton/published
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/published
# Create the directory for unpublished recordings
mkdir -p /mnt/scalelite-recordings/var/bigbluebutton/unpublished
chown 1000:1000 /mnt/scalelite-recordings/var/bigbluebutton/unpublished
chmod 0775 /mnt/scalelite-recordings/var/bigbluebutton/unpublished
sudo systemctl start nfs-kernel-server.service
At this point NFS should be complete except configuring recording importer
***************
Postgres installation
***************
sudo apt-get install postgresql postgresql-contrib
We need a user and a DB so:
su postgres
createuser scalelite
createdb scalelite
QUESTION: Do I need to setup this user with a password?( I dont think so because we run a localhost installation)
In postesql.conf die listen adressen freigeben
vi /etc/postgresql/10/main/postgresql.conf
listen_addresses = ‘*'
vi /etc/postgresql/10/main/postgresql.conf
host scalelite scalelite 172.18.0.2/32 trust
host scalelite scalelite 172.18.0.3/32 trust
*************
Setup redis
*************
I found a document about the redis installation but again I am uncertain what to do.
I can install and autoenable redis using the below commands (it will *NOT* work from default repository for unknown reason)
sudo add-apt-repository ppa:chris-lea/redis-server
sudo apt-get update
sudo apt -install redis-server
sudo systemctl enable redis-server.service
I did configure Redis by editing
vi redis.conf
bind 127.0.0.1 ::1
supervised systemd
After that redis-server starts:
root@scaler:/usr/local/bin# sudo systemctl status redis-server
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-23 21:50:07 UTC; 18min ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Main PID: 4834 (redis-server)
Tasks: 5 (limit: 4622)
CGroup: /system.slice/redis-server.service
└─4834 /usr/bin/redis-server 127.0.0.1:6379
Aug 23 21:50:07 scaler systemd[1]: Starting Advanced key-value store...
Aug 23 21:50:08 scaler systemd[1]: Started Advanced key-value store.
But then there are these 2 points mentioned within the linked pdf:
You can easily install Redis using docker allowing access only from Scalelite docker network and enabling persistence on your Redis server:
First create Redis’s .env file /etc/default/redis
vi /etc/default/redis
with content of:
REDIS_DATA_DIR=/mnt/redis
Then run the docker container:
/usr/bin/docker run --name redis --env-file /etc/default/redis --network scalelite --hostname redis -v ${REDIS_DATA_DIR}:/data redis redis-server --appendonly yes
This will save alot of time you would have spent why Redis is not persisting the servers you configure on Scalelite.
Set the redis_url in Scalelite env file /etc/default/scalelite:
REDIS_URL=redis://redis
Question: Do I need to do all the steps to start redis-server.service or do I ONLY need the /usr/bin/docker run ... ?
However, after a reboot i get this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f7f8e3479162 redis "docker-entrypoint.s…" 13 minutes ago Created redis
IS this correct? I dont know... Because if i do:
/usr/bin/docker run --name redis --env-file /etc/default/redis-server --network scalelite --hostname redis -v ${REDIS_DATA_DIR}:/data redis redis-server --appendonly yes
bind 127.0.0.1 ::1
supervised systemd
After that redis-server starts:
root@scaler:/usr/local/bin# sudo systemctl status redis-server
● redis-server.service - Advanced key-value store
Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-23 21:50:07 UTC; 18min ago
Docs: http://redis.io/documentation,
man:redis-server(1)
Main PID: 4834 (redis-server)
Tasks: 5 (limit: 4622)
CGroup: /system.slice/redis-server.service
└─4834 /usr/bin/redis-server 127.0.0.1:6379
Aug 23 21:50:07 scaler systemd[1]: Starting Advanced key-value store...
Aug 23 21:50:08 scaler systemd[1]: Started Advanced key-value store.
But then there are these 2 points mentioned within the linked pdf:
You can easily install Redis using docker allowing access only from Scalelite docker network and enabling persistence on your Redis server:
First create Redis’s .env file /etc/default/redis
vi /etc/default/redis
with content of:
REDIS_DATA_DIR=/mnt/redis
Then run the docker container:
/usr/bin/docker run --name redis --env-file /etc/default/redis --network scalelite --hostname redis -v ${REDIS_DATA_DIR}:/data redis redis-server --appendonly yes
This will save alot of time you would have spent why Redis is not persisting the servers you configure on Scalelite.
Set the redis_url in Scalelite env file /etc/default/scalelite:
REDIS_URL=redis://redis
Question: Do I need to do all the steps to start redis-server.service or do I ONLY need the /usr/bin/docker run ... ?
However, after a reboot i get this:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f7f8e3479162 redis "docker-entrypoint.s…" 13 minutes ago Created redis
IS this correct? I dont know... Because if i do:
/usr/bin/docker run --name redis --env-file /etc/default/redis-server --network scalelite --hostname redis -v ${REDIS_DATA_DIR}:/data redis redis-server --appendonly yes
docker: Error response from daemon: Conflict. The container name "/redis" is already in use by container "f7f8e3479162026c7492fbed3d054173ee8ccbf306634263b7ccadfdc8be8b5c". You have to remove (or rename) that container to be able to reuse that name.
The next step within the manual is to install the scalelite-docker containers.
At first create the network:
docker network create scalelite
create the /etc/default/scalelite file:
vi /etc/default/scalelite
URL_HOST=scaler.domain.com
SECRET_KEY_BASE=xxxxx
LOADBALANCER_SECRET=yyyyy
DATABASE_URL=postgresql://127.0.0.1:5432
REDIS_URL=redis://redis
SCALELITE_TAG=v1
SCALELITE_RECORDING_DIR=/mnt/scalelite-recordings/var/bigbluebutton
NGINX_SSL=true
SCALELITE_NGINX_EXTRA_OPTS=--mount type=bind,source=/etc/letsencrypt,target=/etc/nginx/ssl,readonly
******************************************
Getting nginx to obtain SSL certificates:
apt install nginx
apt install letsencrypt
apt install certbot
sudo mkdir -p /etc/nginx/ssl
sudo certbot --webroot -w /var/www/html/ -d scaler.domain.com certonly --agree-tos --email hostm...@domain.com --no-eff-email
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for scaler.domain.com
Using the webroot path /var/www/html for all unmatched domains.
Waiting for verification...
Cleaning up challenges
IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/scaler.domain.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/scaler.domain.com/privkey.pem
Your cert will expire on 2020-11-21. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew *all* of your certificates, run
"certbot renew"
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
Afterwards remove nginx:
apt-get remove nginx nginx-common
apt install letsencrypt
apt install certbot
sudo mkdir -p /etc/nginx/ssl
sudo certbot --webroot -w /var/www/html/ -d scaler.domain.com certonly --agree-tos --email hostm...@domain.com --no-eff-email
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for scaler.domain.com
Using the webroot path /var/www/html for all unmatched domains.
Waiting for verification...
Cleaning up challenges
IMPORTANT NOTES:
- Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/scaler.domain.com/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/scaler.domain.com/privkey.pem
Your cert will expire on 2020-11-21. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew *all* of your certificates, run
"certbot renew"
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
Afterwards remove nginx:
apt-get remove nginx nginx-common
*****************************************************************
Scalelite Container configuration:
Next
you should Create a file /etc/systemd/system/scalelite.target with the
content found in the scalelite.target file. This unit is a helper to
allow starting and stopping all of the Scalelite containers together.
vi /etc/systemd/system/scalelite.target
[Unit]
Description=Scalelite
[Install]
WantedBy=multi-user.target
And enable the target by running:
systemctl enable scalelite.target
Created symlink /etc/systemd/system/multi-user.target.wants/scalelite.target → /etc/systemd/system/scalelite.target.
************************************
Create a systemd unit file /etc/systemd/system/scalelite-api.service with the content found in the scalelite-api.service file.
vi /etc/systemd/system/scalelite-api.service
<snipped>
And enable it by running:
systemctl enable scalelite-api.service
Created symlink /etc/systemd/system/scalelite.target.wants/scalelite-api.service → /etc/systemd/system/scalelite-api.service.
*************************************
Create a systemd unit file /etc/systemd/system/scalelite-nginx.service with the content found in the scalelite-nginx.service file.
vi /etc/systemd/system/scalelite-nginx.service
<snipped>
And enable it by running systemctl
Created symlink /etc/systemd/system/scalelite.target.wants/scalelite-nginx.service → /etc/systemd/system/scalelite-nginx.service.
*************************************
You can now restart all scalelite services by running
systemctl restart scalelite.target
Afterwards, check the status with
systemctl status scalelite-api.service scalelite-nginx.service
to verify that the containers started correctly:
This is my output:
root@scaler:/home/it# systemctl status scalelite-api.service scalelite-nginx.service
● scalelite-api.service - Scalelite API
Loaded: loaded (/etc/systemd/system/scalelite-api.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-23 23:18:00 UTC; 1min 29s ago
Process: 3051 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-api (code=exited, status=0/SUCCESS)
Process: 3042 ExecStartPre=/usr/bin/docker rm scalelite-api (code=exited, status=1/FAILURE)
Process: 3017 ExecStartPre=/usr/bin/docker kill scalelite-api (code=exited, status=1/FAILURE)
Main PID: 3071 (docker)
Tasks: 10 (limit: 4622)
CGroup: /system.slice/scalelite-api.service
└─3071 /usr/bin/docker run --name scalelite-api --env-file /etc/default/scalelite --network scalelite --mount type=bind,source
Aug 23 23:18:00 scaler docker[3051]: Digest: sha256:90449bc6793c643e4fabdc148ecf4d7af13039d59927974b40691d04acf0fd32
Aug 23 23:18:00 scaler docker[3051]: Status: Image is up to date for blindsidenetwks/scalelite:v1-api
Aug 23 23:18:00 scaler docker[3051]: docker.io/blindsidenetwks/scalelite:v1-api
Aug 23 23:18:00 scaler systemd[1]: Started Scalelite API.
Aug 23 23:18:05 scaler docker[3071]: Puma starting in single mode...
Aug 23 23:18:05 scaler docker[3071]: * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
Aug 23 23:18:05 scaler docker[3071]: * Min threads: 5, max threads: 5
Aug 23 23:18:05 scaler docker[3071]: * Environment: production
Aug 23 23:18:10 scaler docker[3071]: * Listening on tcp://0.0.0.0:3000
Aug 23 23:18:10 scaler docker[3071]: Use Ctrl-C to stop
● scalelite-nginx.service - Scalelite Nginx
Loaded: loaded (/etc/systemd/system/scalelite-nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-23 23:18:01 UTC; 1min 27s ago
Process: 3115 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-nginx (code=exited, status=0/SUCCESS)
Process: 3106 ExecStartPre=/usr/bin/docker rm scalelite-nginx (code=exited, status=1/FAILURE)
Process: 3072 ExecStartPre=/usr/bin/docker kill scalelite-nginx (code=exited, status=1/FAILURE)
Main PID: 3195 (docker)
Tasks: 10 (limit: 4622)
CGroup: /system.slice/scalelite-nginx.service
└─3195 /usr/bin/docker run --name scalelite-nginx --env-file /etc/default/scalelite --network scalelite --publish 80:80 --publ
Aug 23 23:18:01 scaler docker[3115]: v1-nginx: Pulling from blindsidenetwks/scalelite
Aug 23 23:18:01 scaler docker[3115]: Digest: sha256:fb80a8288b7a9d4b99daf938761d367f071621915ab696cb36e110be43e9c693
Aug 23 23:18:01 scaler docker[3115]: Status: Image is up to date for blindsidenetwks/scalelite:v1-nginx
Aug 23 23:18:01 scaler docker[3115]: docker.io/blindsidenetwks/scalelite:v1-nginx
Aug 23 23:18:01 scaler systemd[1]: Started Scalelite Nginx.
Aug 23 23:18:04 scaler docker[3195]: Startup script was run as init, re-execing using tini.
Aug 23 23:18:04 scaler docker[3195]: Generating templated nginx configuration...
Aug 23 23:18:04 scaler docker[3195]: Using SSL configuration template.
Aug 23 23:18:05 scaler docker[3195]: Starting nginx periodic reload process...
Aug 23 23:18:05 scaler docker[3195]: Starting nginx...
******************
***************
On firt run I should initiliace the database, it looks like that failed:
root@scaler:/home/it# docker exec -it scalelite-api bin/rake db:setup
could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
Couldn't create 'scalelite' database. Please check your configuration.
rake aborted!
PG::ConnectionBad: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `initialize'
****
vi /etc/systemd/system/scalelite.target
[Unit]
Description=Scalelite
[Install]
WantedBy=multi-user.target
And enable the target by running:
systemctl enable scalelite.target
Created symlink /etc/systemd/system/multi-user.target.wants/scalelite.target → /etc/systemd/system/scalelite.target.
************************************
Create a systemd unit file /etc/systemd/system/scalelite-api.service with the content found in the scalelite-api.service file.
vi /etc/systemd/system/scalelite-api.service
<snipped>
And enable it by running:
systemctl enable scalelite-api.service
Created symlink /etc/systemd/system/scalelite.target.wants/scalelite-api.service → /etc/systemd/system/scalelite-api.service.
*************************************
Create a systemd unit file /etc/systemd/system/scalelite-nginx.service with the content found in the scalelite-nginx.service file.
vi /etc/systemd/system/scalelite-nginx.service
<snipped>
And enable it by running systemctl
Created symlink /etc/systemd/system/scalelite.target.wants/scalelite-nginx.service → /etc/systemd/system/scalelite-nginx.service.
*************************************
You can now restart all scalelite services by running
systemctl restart scalelite.target
Afterwards, check the status with
systemctl status scalelite-api.service scalelite-nginx.service
to verify that the containers started correctly:
This is my output:
root@scaler:/home/it# systemctl status scalelite-api.service scalelite-nginx.service
● scalelite-api.service - Scalelite API
Loaded: loaded (/etc/systemd/system/scalelite-api.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-23 23:18:00 UTC; 1min 29s ago
Process: 3051 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-api (code=exited, status=0/SUCCESS)
Process: 3042 ExecStartPre=/usr/bin/docker rm scalelite-api (code=exited, status=1/FAILURE)
Process: 3017 ExecStartPre=/usr/bin/docker kill scalelite-api (code=exited, status=1/FAILURE)
Main PID: 3071 (docker)
Tasks: 10 (limit: 4622)
CGroup: /system.slice/scalelite-api.service
└─3071 /usr/bin/docker run --name scalelite-api --env-file /etc/default/scalelite --network scalelite --mount type=bind,source
Aug 23 23:18:00 scaler docker[3051]: Digest: sha256:90449bc6793c643e4fabdc148ecf4d7af13039d59927974b40691d04acf0fd32
Aug 23 23:18:00 scaler docker[3051]: Status: Image is up to date for blindsidenetwks/scalelite:v1-api
Aug 23 23:18:00 scaler docker[3051]: docker.io/blindsidenetwks/scalelite:v1-api
Aug 23 23:18:00 scaler systemd[1]: Started Scalelite API.
Aug 23 23:18:05 scaler docker[3071]: Puma starting in single mode...
Aug 23 23:18:05 scaler docker[3071]: * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
Aug 23 23:18:05 scaler docker[3071]: * Min threads: 5, max threads: 5
Aug 23 23:18:05 scaler docker[3071]: * Environment: production
Aug 23 23:18:10 scaler docker[3071]: * Listening on tcp://0.0.0.0:3000
Aug 23 23:18:10 scaler docker[3071]: Use Ctrl-C to stop
● scalelite-nginx.service - Scalelite Nginx
Loaded: loaded (/etc/systemd/system/scalelite-nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-08-23 23:18:01 UTC; 1min 27s ago
Process: 3115 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-nginx (code=exited, status=0/SUCCESS)
Process: 3106 ExecStartPre=/usr/bin/docker rm scalelite-nginx (code=exited, status=1/FAILURE)
Process: 3072 ExecStartPre=/usr/bin/docker kill scalelite-nginx (code=exited, status=1/FAILURE)
Main PID: 3195 (docker)
Tasks: 10 (limit: 4622)
CGroup: /system.slice/scalelite-nginx.service
└─3195 /usr/bin/docker run --name scalelite-nginx --env-file /etc/default/scalelite --network scalelite --publish 80:80 --publ
Aug 23 23:18:01 scaler docker[3115]: v1-nginx: Pulling from blindsidenetwks/scalelite
Aug 23 23:18:01 scaler docker[3115]: Digest: sha256:fb80a8288b7a9d4b99daf938761d367f071621915ab696cb36e110be43e9c693
Aug 23 23:18:01 scaler docker[3115]: Status: Image is up to date for blindsidenetwks/scalelite:v1-nginx
Aug 23 23:18:01 scaler docker[3115]: docker.io/blindsidenetwks/scalelite:v1-nginx
Aug 23 23:18:01 scaler systemd[1]: Started Scalelite Nginx.
Aug 23 23:18:04 scaler docker[3195]: Startup script was run as init, re-execing using tini.
Aug 23 23:18:04 scaler docker[3195]: Generating templated nginx configuration...
Aug 23 23:18:04 scaler docker[3195]: Using SSL configuration template.
Aug 23 23:18:05 scaler docker[3195]: Starting nginx periodic reload process...
Aug 23 23:18:05 scaler docker[3195]: Starting nginx...
******************
***************
On firt run I should initiliace the database, it looks like that failed:
root@scaler:/home/it# docker exec -it scalelite-api bin/rake db:setup
could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
Couldn't create 'scalelite' database. Please check your configuration.
rake aborted!
PG::ConnectionBad: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `initialize'
****
snipped many more of these gems... messages
*****
/railties/databases.rake:39:in `block (2 levels) in <main>'
Tasks: TOP => db:setup => db:schema:load_if_ruby => db:create
(See full trace by running task with --trace)
Tasks: TOP => db:setup => db:schema:load_if_ruby => db:create
(See full trace by running task with --trace)
BUT If i open a browser on https://scaler.domain.com
<response>
<returncode>SUCCESS</returncode>
<version>2.0</version>
<build>v1.0.5</build>
</response>
Adding a server:
docker exec -i scalelite-api bundle exec rake servers:add[https://tele1.domain.com/bigbluebutton/api/,<long ----- secret>]
rake aborted!
Name does not resolve
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/connection/hiredis.rb:19:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/connection/hiredis.rb:19:in `connect'
*** snipped****
/srv/scalelite/lib/tasks/servers.rake:33:in `block (2 levels) in <main>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/usr/bin/bundle:23:in `load'
/usr/bin/bundle:23:in `<main>'
Tasks: TOP => servers:add
(See full trace by running task with --trace)
<response>
<returncode>SUCCESS</returncode>
<version>2.0</version>
<build>v1.0.5</build>
</response>
Adding a server:
docker exec -i scalelite-api bundle exec rake servers:add[https://tele1.domain.com/bigbluebutton/api/,<long ----- secret>]
rake aborted!
Name does not resolve
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/connection/hiredis.rb:19:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/connection/hiredis.rb:19:in `connect'
*** snipped****
/srv/scalelite/lib/tasks/servers.rake:33:in `block (2 levels) in <main>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/usr/bin/bundle:23:in `load'
/usr/bin/bundle:23:in `<main>'
Tasks: TOP => servers:add
(See full trace by running task with --trace)
Well, I am stucked right now and dont know where to look at.
rschu...@gmail.com
Aug 24, 2020, 6:57:12 AM8/24/20
to BigBlueButton-Setup
I can't create the needed database. Dont find my error ( I know this is more related to postgresql but as i call it from the scalelite-api container I ask here)
As you can see below the connectoin is failing REFUSED, I dot get why, the port 5432 is open:
netstat -nlt
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN
tcp6 0 0 :::5432 :::* LISTEN
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN
tcp6 0 0 :::5432 :::* LISTEN
I can connect thes that th port is open from another machine in local network without problem. This is within hba_conf:
local all postgres peer
#
# # TYPE DATABASE USER ADDRESS METHOD
#
# # "local" is for Unix domain socket connections only
local all all peer
# # IPv4 local connections:
host all all 127.0.0.1/32 md5
# # IPv6 local connections:
host all all ::1/128 md5
# # Allow replication connections from localhost, by a user with the
# # replication privilege.
local replication postgres peer
host replication postgres 127.0.0.1/32 md5
host replication postgres ::1/128 md5
host scalelite scalelite 172.19.0.2/32 trust
host scalelite scalelite 172.19.0.3/32 trust
host all all 0.0.0.0/0 trust
host all all ::/0 trust
#
# # TYPE DATABASE USER ADDRESS METHOD
#
# # "local" is for Unix domain socket connections only
local all all peer
# # IPv4 local connections:
host all all 127.0.0.1/32 md5
# # IPv6 local connections:
host all all ::1/128 md5
# # Allow replication connections from localhost, by a user with the
# # replication privilege.
local replication postgres peer
host replication postgres 127.0.0.1/32 md5
host replication postgres ::1/128 md5
host scalelite scalelite 172.19.0.2/32 trust
host scalelite scalelite 172.19.0.3/32 trust
host all all 0.0.0.0/0 trust
host all all ::/0 trust
From what I understand is that the docker-user that onnects would be scalelite. I created a DB user name "scalelite" (at first without a password)
In the scalelite/default I tried all this:
DATABASE_URL=postgresql://127.0.0.1:5432
DATABASE_URL=postgresql://scal...@127.0.0.1:5432
DATABASE_URL=postgresql://localhost:5432
Nothing worked.
Then I did a:
ALTER USER scalelite SET PASSWORD 'xxxx'
But even with this setting, it did not work.
DATABASE_URL=postgresql://scalelite:xx...@127.0.0.1:5432
DATABASE_URL=postgresql://scalelite:xxxx@localhost:5432
Martin Thomas Schrott
Aug 24, 2020, 7:21:54 AM8/24/20
to bigbluebu...@googlegroups.com, rschu...@gmail.com
why are you allowing 0.0.0.0 to postgresql? is your scalelite host
another host than postgres is running on?
you really should not trust all external hosts.
try to connect to postgres with psql first - when you get that to run
enter the settings to scalelite config.
read the postgres docs to find out how to get psql to connect / users /
passwords set up.
cheers
Martin
another host than postgres is running on?
you really should not trust all external hosts.
try to connect to postgres with psql first - when you get that to run
enter the settings to scalelite config.
read the postgres docs to find out how to get psql to connect / users /
passwords set up.
cheers
Martin
rschu...@gmail.com
Aug 24, 2020, 7:40:20 AM8/24/20
to BigBlueButton-Setup
Hi Martin,
the 0.0.0.0 was of course only for testing purpose (and this system is behind a firewall dropping all sql connections)
But good news! I read through ALL the entries regarding postgres in here and NOW my rake setupdb succeeded by using the local IP address (not localhost or 127.0.0.1)
rschu...@gmail.com
Aug 24, 2020, 8:21:50 AM8/24/20
to BigBlueButton-Setup
Ok, well next problem - I am not able to execute any of the other api-comannds (add server, status etc.)
Suspicious: "Name dos not resolve".
Maybe on of the containers is not runnig correctly?
root@scaler:/home/it# docker exec -i scalelite-api bundle exec rake status --trace
** Invoke status (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute status
** Invoke status (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute status
rake aborted!
Name does not resolve
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/connection/hiredis.rb:19:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/connection/hiredis.rb:19:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:349:in `establish_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:106:in `block in connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:306:in `with_reconnect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:105:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:381:in `ensure_connected'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:231:in `block in process'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:319:in `logging'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:230:in `process'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:125:in `call'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:1447:in `block in smembers'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:52:in `block in synchronize'
/usr/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:52:in `synchronize'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:1446:in `smembers'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-namespace-1.7.0/lib/redis/namespace.rb:469:in `call_with_namespace'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-namespace-1.7.0/lib/redis/namespace.rb:349:in `block (2 levels) in <class:Namespace>'
/srv/scalelite/app/models/server.rb:189:in `block in all'
/srv/scalelite/app/models/application_redis_record.rb:133:in `block in with_connection'
/srv/scalelite/lib/redis_store.rb:35:in `block in with_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:65:in `block (2 levels) in with'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in `handle_interrupt'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in `block in with'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in `handle_interrupt'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in `with'
/srv/scalelite/lib/redis_store.rb:35:in `with_connection'
/srv/scalelite/app/models/application_redis_record.rb:132:in `with_connection'
/srv/scalelite/app/models/server.rb:188:in `all'
/srv/scalelite/lib/tasks/status.rake:10:in `block in <main>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `block in execute'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `each'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `execute'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/usr/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:188:in `invoke'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:160:in `invoke_task'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `each'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block in top_level'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:125:in `run_with_threads'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:110:in `top_level'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:83:in `block in run'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:106:in `block in connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:306:in `with_reconnect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:105:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:381:in `ensure_connected'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:231:in `block in process'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:319:in `logging'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:230:in `process'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:125:in `call'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:1447:in `block in smembers'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:52:in `block in synchronize'
/usr/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:52:in `synchronize'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis.rb:1446:in `smembers'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-namespace-1.7.0/lib/redis/namespace.rb:469:in `call_with_namespace'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-namespace-1.7.0/lib/redis/namespace.rb:349:in `block (2 levels) in <class:Namespace>'
/srv/scalelite/app/models/server.rb:189:in `block in all'
/srv/scalelite/app/models/application_redis_record.rb:133:in `block in with_connection'
/srv/scalelite/lib/redis_store.rb:35:in `block in with_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:65:in `block (2 levels) in with'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in `handle_interrupt'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:64:in `block in with'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in `handle_interrupt'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/connection_pool-2.2.2/lib/connection_pool.rb:61:in `with'
/srv/scalelite/lib/redis_store.rb:35:in `with_connection'
/srv/scalelite/app/models/application_redis_record.rb:132:in `with_connection'
/srv/scalelite/app/models/server.rb:188:in `all'
/srv/scalelite/lib/tasks/status.rake:10:in `block in <main>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `block in execute'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `each'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:281:in `execute'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:219:in `block in invoke_with_call_chain'
/usr/lib/ruby/2.6.0/monitor.rb:235:in `mon_synchronize'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:199:in `invoke_with_call_chain'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/task.rb:188:in `invoke'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:160:in `invoke_task'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block (2 levels) in top_level'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `each'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:116:in `block in top_level'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:125:in `run_with_threads'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:110:in `top_level'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:83:in `block in run'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:186:in `standard_exception_handling'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/lib/rake/application.rb:80:in `run'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/bin/rake:23:in `load'
/srv/scalelite/vendor/bundle/ruby/2.6.0/bin/rake:23:in `<top (required)>'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `load'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:28:in `run'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:465:in `exec'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:27:in `dispatch'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:18:in `start'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/exe/bundle:30:in `block in <top (required)>'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/exe/bundle:22:in `<top (required)>'
/srv/scalelite/vendor/bundle/ruby/2.6.0/bin/rake:23:in `<top (required)>'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `load'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:28:in `run'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:465:in `exec'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:27:in `dispatch'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/cli.rb:18:in `start'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/exe/bundle:30:in `block in <top (required)>'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/usr/lib/ruby/gems/2.6.0/gems/bundler-2.0.2/exe/bundle:22:in `<top (required)>'
/usr/bin/bundle:23:in `load'
/usr/bin/bundle:23:in `<main>'
Tasks: TOP => status
So i did:
root@scaler:/home/it# systemctl status scalelite-api.service scalelite-nginx.service
● scalelite-api.service - Scalelite API
Loaded: loaded (/etc/systemd/system/scalelite-api.service; enabled; vendor preset: enabled)
● scalelite-api.service - Scalelite API
Loaded: loaded (/etc/systemd/system/scalelite-api.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-08-24 11:51:27 UTC; 11min ago
Process: 2264 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-api (code=exited, status=0/SUCCESS)
Process: 1998 ExecStartPre=/usr/bin/docker rm scalelite-api (code=exited, status=0/SUCCESS)
Process: 1144 ExecStartPre=/usr/bin/docker kill scalelite-api (code=exited, status=1/FAILURE)
Main PID: 2281 (docker)
Process: 2264 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-api (code=exited, status=0/SUCCESS)
Process: 1998 ExecStartPre=/usr/bin/docker rm scalelite-api (code=exited, status=0/SUCCESS)
Process: 1144 ExecStartPre=/usr/bin/docker kill scalelite-api (code=exited, status=1/FAILURE)
Main PID: 2281 (docker)
Tasks: 10 (limit: 4622)
CGroup: /system.slice/scalelite-api.service
└─2281 /usr/bin/docker run --name scalelite-api --env-file /etc/default/scalelite --network scalelite --mount type=bind,source=/mnt/scalelite-recordings/var/
Aug 24 11:51:27 scaler docker[2264]: Digest: sha256:90449bc6793c643e4fabdc148ecf4d7af13039d59927974b40691d04acf0fd32
Aug 24 11:51:27 scaler docker[2264]: Status: Image is up to date for blindsidenetwks/scalelite:v1-api
Aug 24 11:51:27 scaler docker[2264]: docker.io/blindsidenetwks/scalelite:v1-api
Aug 24 11:51:27 scaler systemd[1]: Started Scalelite API.
Aug 24 11:51:31 scaler docker[2281]: Puma starting in single mode...
Aug 24 11:51:31 scaler docker[2281]: * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
Aug 24 11:51:31 scaler docker[2281]: * Min threads: 5, max threads: 5
Aug 24 11:51:31 scaler docker[2281]: * Environment: production
Aug 24 11:51:34 scaler docker[2281]: * Listening on tcp://0.0.0.0:3000
Aug 24 11:51:34 scaler docker[2281]: Use Ctrl-C to stop
Aug 24 11:51:27 scaler docker[2264]: Digest: sha256:90449bc6793c643e4fabdc148ecf4d7af13039d59927974b40691d04acf0fd32
Aug 24 11:51:27 scaler docker[2264]: Status: Image is up to date for blindsidenetwks/scalelite:v1-api
Aug 24 11:51:27 scaler docker[2264]: docker.io/blindsidenetwks/scalelite:v1-api
Aug 24 11:51:27 scaler systemd[1]: Started Scalelite API.
Aug 24 11:51:31 scaler docker[2281]: Puma starting in single mode...
Aug 24 11:51:31 scaler docker[2281]: * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
Aug 24 11:51:31 scaler docker[2281]: * Min threads: 5, max threads: 5
Aug 24 11:51:31 scaler docker[2281]: * Environment: production
Aug 24 11:51:34 scaler docker[2281]: * Listening on tcp://0.0.0.0:3000
Aug 24 11:51:34 scaler docker[2281]: Use Ctrl-C to stop
● scalelite-nginx.service - Scalelite Nginx
Loaded: loaded (/etc/systemd/system/scalelite-nginx.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-08-24 11:51:29 UTC; 11min ago
Process: 2325 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-nginx (code=exited, status=0/SUCCESS)
Process: 2314 ExecStartPre=/usr/bin/docker rm scalelite-nginx (code=exited, status=0/SUCCESS)
Process: 2282 ExecStartPre=/usr/bin/docker kill scalelite-nginx (code=exited, status=1/FAILURE)
Main PID: 2424 (docker)
Process: 2325 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-nginx (code=exited, status=0/SUCCESS)
Process: 2314 ExecStartPre=/usr/bin/docker rm scalelite-nginx (code=exited, status=0/SUCCESS)
Process: 2282 ExecStartPre=/usr/bin/docker kill scalelite-nginx (code=exited, status=1/FAILURE)
Main PID: 2424 (docker)
Tasks: 10 (limit: 4622)
CGroup: /system.slice/scalelite-nginx.service
└─2424 /usr/bin/docker run --name scalelite-nginx --env-file /etc/default/scalelite --network scalelite --publish 80:80 --publish 443:443 --mount type=bind,s
Aug 24 11:51:29 scaler docker[2325]: Status: Image is up to date for blindsidenetwks/scalelite:v1-nginx
Aug 24 11:51:29 scaler docker[2325]: docker.io/blindsidenetwks/scalelite:v1-nginx
Aug 24 11:51:29 scaler systemd[1]: Started Scalelite Nginx.
Aug 24 11:51:31 scaler docker[2424]: Startup script was run as init, re-execing using tini.
Aug 24 11:51:31 scaler docker[2424]: Generating templated nginx configuration...
Aug 24 11:51:31 scaler docker[2424]: Using SSL configuration template.
Aug 24 11:51:31 scaler docker[2424]: Starting nginx periodic reload process...
Aug 24 11:51:31 scaler docker[2424]: Starting nginx...
● scalelite-poller.service - Scalelite Meeting Status Poller
Loaded: loaded (/etc/systemd/system/scalelite-poller.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-08-24 12:11:42 UTC; 1min 33s ago
Process: 2421 ExecStart=/usr/bin/docker run --name scalelite-poller --env-file /etc/default/scalelite --network scalelite blindsidenetwks/scalelite:${SCALELITE_TAG}-p
Process: 2377 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-poller (code=exited, status=0/SUCCESS)
Process: 2358 ExecStartPre=/usr/bin/docker rm scalelite-poller (code=exited, status=1/FAILURE)
Process: 2308 ExecStartPre=/usr/bin/docker kill scalelite-poller (code=exited, status=1/FAILURE)
Main PID: 2421 (code=exited, status=1/FAILURE)
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/lib/tasks/poll.rake:12:in `block (2 levels) in <main>'
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/lib/tasks/poll.rake:10:in `loop'
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/lib/tasks/poll.rake:10:in `block in <main>'
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Aug 24 12:11:36 scaler docker[2421]: /usr/bin/bundle:23:in `load'
Aug 24 12:11:36 scaler docker[2421]: /usr/bin/bundle:23:in `<main>'
Aug 24 12:11:36 scaler docker[2421]: Tasks: TOP => poll:all => poll:meetings
Aug 24 12:11:36 scaler docker[2421]: (See full trace by running task with --trace)
Aug 24 12:11:42 scaler systemd[1]: scalelite-poller.service: Main process exited, code=exited, status=1/FAILURE
Aug 24 12:11:42 scaler systemd[1]: scalelite-poller.service: Failed with result 'exit-code'.
Aug 24 11:51:29 scaler docker[2325]: Status: Image is up to date for blindsidenetwks/scalelite:v1-nginx
Aug 24 11:51:29 scaler docker[2325]: docker.io/blindsidenetwks/scalelite:v1-nginx
Aug 24 11:51:29 scaler systemd[1]: Started Scalelite Nginx.
Aug 24 11:51:31 scaler docker[2424]: Startup script was run as init, re-execing using tini.
Aug 24 11:51:31 scaler docker[2424]: Generating templated nginx configuration...
Aug 24 11:51:31 scaler docker[2424]: Using SSL configuration template.
Aug 24 11:51:31 scaler docker[2424]: Starting nginx periodic reload process...
Aug 24 11:51:31 scaler docker[2424]: Starting nginx...
● scalelite-poller.service - Scalelite Meeting Status Poller
Loaded: loaded (/etc/systemd/system/scalelite-poller.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2020-08-24 12:11:42 UTC; 1min 33s ago
Process: 2421 ExecStart=/usr/bin/docker run --name scalelite-poller --env-file /etc/default/scalelite --network scalelite blindsidenetwks/scalelite:${SCALELITE_TAG}-p
Process: 2377 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-poller (code=exited, status=0/SUCCESS)
Process: 2358 ExecStartPre=/usr/bin/docker rm scalelite-poller (code=exited, status=1/FAILURE)
Process: 2308 ExecStartPre=/usr/bin/docker kill scalelite-poller (code=exited, status=1/FAILURE)
Main PID: 2421 (code=exited, status=1/FAILURE)
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/lib/tasks/poll.rake:12:in `block (2 levels) in <main>'
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/lib/tasks/poll.rake:10:in `loop'
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/lib/tasks/poll.rake:10:in `block in <main>'
Aug 24 12:11:36 scaler docker[2421]: /srv/scalelite/vendor/bundle/ruby/2.6.0/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
Aug 24 12:11:36 scaler docker[2421]: /usr/bin/bundle:23:in `load'
Aug 24 12:11:36 scaler docker[2421]: /usr/bin/bundle:23:in `<main>'
Aug 24 12:11:36 scaler docker[2421]: Tasks: TOP => poll:all => poll:meetings
Aug 24 12:11:36 scaler docker[2421]: (See full trace by running task with --trace)
Aug 24 12:11:42 scaler systemd[1]: scalelite-poller.service: Main process exited, code=exited, status=1/FAILURE
Aug 24 12:11:42 scaler systemd[1]: scalelite-poller.service: Failed with result 'exit-code'.
Does that look fine`? I dont think so. The poller at least has a problem.
Where to look next?
rschu...@gmail.com
Aug 24, 2020, 10:29:14 AM8/24/20
to BigBlueButton-Setup
Even without the poller I thought the scalelite would work.
But from greenlight I always get - endpoint and scret error.
The scallite health check under:
shows:
Health Check Failure: Name does not resolve
Martin Thomas Schrott
Aug 24, 2020, 10:30:55 AM8/24/20
to bigbluebu...@googlegroups.com, rschu...@gmail.com
have a look at your hosts file - is the domain you configured there with the external ip?
recheck all other hostnames and configs.
--
You received this message because you are subscribed to the Google Groups "BigBlueButton-Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-s...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/265a0886-8336-4244-a407-1237d705d2b1n%40googlegroups.com.
rschu...@gmail.com
Aug 24, 2020, 10:56:12 AM8/24/20
to BigBlueButton-Setup
Hallo Martin ,
thanks for helping, I really appreciate that!
But I dont understand your question completely. What would you expect to see in there- an external IP/complete hostname resolution?
111.222.333.444 scaler.domain.com ?
root@scaler:/home/it# vi /etc/hosts
127.0.0.1 localhost
127.0.1.1 scaler
127.0.0.1 localhost
127.0.1.1 scaler
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
Any chance you take a look /to get in contact? Right now I think i am SO CLOSE to get this up .and running..
Martin Thomas Schrott
Aug 24, 2020, 11:14:04 AM8/24/20
to bigbluebu...@googlegroups.com, rschu...@gmail.com
Am 24.08.2020 um 16:56 schrieb
rschu...@gmail.com:
Hallo Martin ,
thanks for helping, I really appreciate that!
But I dont understand your question completely. What would you expect to see in there- an external IP/complete hostname resolution?
111.222.333.444 scaler.domain.com ?
yes exactly.
on all your bbb/greenlight/scalelite hosts this should be the case.
bbb and it's components seem to check this in different situations. Maybe it can help to solve your problem.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-setup/4b39cf5c-6822-4eab-adff-1ca475d6c9d4n%40googlegroups.com.
rschu...@gmail.com
Aug 24, 2020, 11:51:59 AM8/24/20
to BigBlueButton-Setup
Sad to say but it did not help :-(
Right now thinking of starting (again) from scratch
Fran Pereyra
Aug 25, 2020, 4:29:29 PM8/25/20
to BigBlueButton-Setup
I've Been there. Don't loose more time, try again with the docker "lazy" deployment, the process is 400% more straightforward and the docs are much more clear than the standard setup.. and there's less fail chances.
rschu...@gmail.com
Aug 26, 2020, 7:44:57 AM8/26/20
to BigBlueButton-Setup
Hi,
I had some help from an Linux epxert - and it is finally working.
I dont really now EXACTLY where I made a mistake, but obviously I made one :-)
In other words, this thread is closed for good *gg*
Reply all
Reply to author
Forward
0 new messages