scalelite-api.service: Failed with result 'exit-code'

587 views
Skip to first unread message

Rexon Dmello

unread,
Jul 20, 2020, 9:34:15 AM7/20/20
to BigBlueButton-dev
Hi everyone,
Iam trying to install scalelite , i ran into the following 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...


the scalelite.api-service is giving an error which iam unable to fix, looking for help.
Thanks in advance

Shashikant Vaishnav

unread,
Jul 20, 2020, 10:29:05 AM7/20/20
to bigblueb...@googlegroups.com
Check the service logs or run this command over shell
  /usr/bin/docker run --name scalelite-nginx --env-file /etc/default/scalelite --network scalelite --publish 80:80 --publish 443:443 --mount type=bind,s
--
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-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bigbluebutton-dev/daee4ef0-61f2-4a27-960b-9981614a5f93n%40googlegroups.com.
Message has been deleted

Rexon Dmello

unread,
Jul 20, 2020, 1:07:48 PM7/20/20
to BigBlueButton-dev
Hi shashikan thanks for your suggestion it fixed the issue.

but unable to setup the postgres db , the scalelite and postgresql is running on the same server. But when i run the command :
docker exec -it scalelite-api bin/rake db:setup 

getting the following error : 

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'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `new'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/pg-1.2.2/lib/pg.rb:58:in `connect'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/postgresql_adapter.rb:46:in `postgresql_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:889:in `new_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:933:in `checkout_new_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:912:in `try_to_checkout_new_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:873:in `acquire_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:595:in `checkout'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:439:in `connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:1121:in `retrieve_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_handling.rb:238:in `retrieve_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/connection_handling.rb:206:in `connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/postgresql_database_tasks.rb:12:in `connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/postgresql_database_tasks.rb:21:in `create'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:126:in `create'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:185:in `block in create_current'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:479:in `block (2 levels) in each_current_configuration'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:476:in `each'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:476:in `block in each_current_configuration'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:475:in `each'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:475:in `each_current_configuration'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/tasks/database_tasks.rb:184:in `create_current'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.2.1/lib/active_record/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)

Rexon Dmello

unread,
Jul 21, 2020, 4:29:28 AM7/21/20
to BigBlueButton-dev
Hi, 
i fixed the above issue . all docker containers are running now. But when i run the commands 
1.docker exec -it scalelite-api /bin/sh
2../bin/rake servers

getting the following error :
rake aborted!
Redis::CannotConnectError: Error connecting to Redis on 127.0.0.1:6379 (Errno::ECONNREFUSED)
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:362:in `rescue in establish_connection'
/srv/scalelite/vendor/bundle/ruby/2.6.0/gems/redis-4.1.3/lib/redis/client.rb:343: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'
/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/servers.rake:5:in `block in <main>'

Caused by:
Errno::ECONNREFUSED: Connection refused
/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'
/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/servers.rake:5:in `block in <main>'

can anyone help me on this. Thanks

Shashikant Vaishnav

unread,
Jul 21, 2020, 4:38:25 AM7/21/20
to bigblueb...@googlegroups.com
Hi there, 

The Redis needs to be accessible to the BBB servers. Also, the connection needs to be persistent. 

If you choose to allow connection from all the IPS using listen ="*"

make sure you only allow the BBB IPs using the firewall like ufw 



--
Thanks & Regards
Shashikant Vaishnav



Rexon Dmello

unread,
Jul 21, 2020, 7:19:06 AM7/21/20
to BigBlueButton-dev
Hi Shashikant ,
As per your suggestion i tried adding the above mentioned setting in redis.conf . but still iam getting the following  error : 

● scalelite-poller.service - Scalelite Meeting Status Poller
   Loaded: loaded (/etc/systemd/system/scalelite-poller.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-07-21 13:12:42 CEST; 7s ago
  Process: 23941 ExecStartPre=/usr/bin/docker pull blindsidenetwks/scalelite:${SCALELITE_TAG}-poller (code=exited, status=0/SUCCESS)
  Process: 23890 ExecStartPre=/usr/bin/docker rm scalelite-poller (code=exited, status=0/SUCCESS)
  Process: 23829 ExecStartPre=/usr/bin/docker kill scalelite-poller (code=exited, status=1/FAILURE)
 Main PID: 24099 (docker)
    Tasks: 12 (limit: 4915)
   CGroup: /system.slice/scalelite-poller.service
           └─24099 /usr/bin/docker run --name scalelite-poller --env-file /etc/default/scalelite --network scalelite blindsidenetwks/scalelite:v1-poller

Jul 21 13:12:41 Ubuntu-1804-bionic-64-minimal docker[23890]: scalelite-poller
Jul 21 13:12:42 Ubuntu-1804-bionic-64-minimal docker[23941]: v1-poller: Pulling from blindsidenetwks/scalelite
Jul 21 13:12:42 Ubuntu-1804-bionic-64-minimal docker[23941]: Digest: sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Jul 21 13:12:42 Ubuntu-1804-bionic-64-minimal docker[23941]: Status: Image is up to date for blindsidenetwks/scalelite:v1-poller
Jul 21 13:12:42 Ubuntu-1804-bionic-64-minimal docker[23941]: docker.io/blindsidenetwks/scalelite:v1-poller
Jul 21 13:12:42 Ubuntu-1804-bionic-64-minimal systemd[1]: Started Scalelite Meeting Status Poller.
Jul 21 13:12:47 Ubuntu-1804-bionic-64-minimal docker[24099]: I, [2020-07-21T11:12:47.133872 #6]  INFO -- : Running poller with interval 60.0
Jul 21 13:12:47 Ubuntu-1804-bionic-64-minimal docker[24099]: D, [2020-07-21T11:12:47.154477 #6] DEBUG -- : Polling servers
Jul 21 13:12:47 Ubuntu-1804-bionic-64-minimal docker[24099]: D, [2020-07-21T11:12:47.154594 #6] DEBUG -- : Polling meetings
Jul 21 13:12:47 Ubuntu-1804-bionic-64-minimal docker[24099]: W, [2020-07-21T11:12:47.181249 #6]  WARN -- : Error connecting to Redis on 127.0.0.1:6379 (Errno::ECONNREFUSED)

Can you let me please let me know what exactly changes should i do in redis.conf file  or is it the issue with the redis url ?
Thanks in Advance

Rexon Dmello

unread,
Jul 22, 2020, 4:33:22 AM7/22/20
to BigBlueButton-dev
Hi shashikan thanks for your help  scalelite is up and running.  
the result iam getting is :
~ $ ./bin/rake status
        HOSTNAME         STATE   STATUS  MEETINGS  USERS  LARGEST MEETING  VIDEOS
 my.example.com  enabled  online         1      0                0       0

But when i run the scalelite host name getting the following error : 
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<response>
<script/>
<returncode>FAILED</returncode>
<messageKey>unsupportedRequest</messageKey>
<message>This request is not supported.</message>
</response>

can you let me the issue here.

Thanks in advance

boo...@gmail.com

unread,
Jul 23, 2020, 10:23:49 AM7/23/20
to BigBlueButton-dev
if you're going to the root of your domain, then that is correct

try going to https://<your domain>/bigbluebutton/api
Reply all
Reply to author
Forward
0 new messages