"We're sorry, but something went wrong." after updating the image

Ch0wW commented 4 years ago

May be a continuation of Issue #40 .

Starting with commit https://github.com/chrisvel/wreeto_official/commit/b0ab235a4528217209ba81622c462d0f30841071 (and probably 2/3 commits earlier), I cannot use the Docker image anymore.

No matter the page used, I have this error shown:

Logs show nothing unusual at all, the classic warning messages appearing. The CPU stresses to 100% before stopping suddenly, and making this error appear.

Also, tested by using the latest Docker image from your docker-compose file, and by creating the docker image locally from my RPI4,

chrisvel commented 4 years ago

@Ch0wW I am sorry for the late reply. I have introduced a fix just 4 days ago that should solve this issue. Can you please pull your docker images and let me know If this is fixed ?

Ch0wW commented 4 years ago

No worries! I just updated the latest commit, created the image, and unfortunately, it didn't work.

Here's the log output:

pi@RPI3:~/wreeto_official $ docker-compose up
Creating network "wreeto_official_default" with the default driver
Creating wreeto_official_redis_1    ... done
Creating wreeto_official_postgres_1 ... done
Creating wreeto_official_app_1      ... done
Attaching to wreeto_official_redis_1, wreeto_official_postgres_1, wreeto_official_app_1
postgres_1  |
postgres_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1  |
postgres_1  | 2020-10-31 20:11:55.471 UTC [1] LOG:  starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
redis_1     | 1:C 31 Oct 2020 20:11:54.005 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1     | 1:C 31 Oct 2020 20:11:54.005 # Redis version=5.0.7, bits=32, commit=00000000, modified=0, pid=1, just started
redis_1     | 1:C 31 Oct 2020 20:11:54.005 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
postgres_1  | 2020-10-31 20:11:55.476 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres_1  | 2020-10-31 20:11:55.476 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1  | 2020-10-31 20:11:55.517 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2020-10-31 20:11:55.543 UTC [25] LOG:  database system was shut down at 2020-10-31 20:11:39 UTC
redis_1     | 1:M 31 Oct 2020 20:11:54.014 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
postgres_1  | 2020-10-31 20:11:55.604 UTC [1] LOG:  database system is ready to accept connections
redis_1     | 1:M 31 Oct 2020 20:11:54.061 * Running mode=standalone, port=6379.
redis_1     | 1:M 31 Oct 2020 20:11:54.062 # Server initialized
redis_1     | 1:M 31 Oct 2020 20:11:54.062 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1     | 1:M 31 Oct 2020 20:11:54.063 * Ready to accept connections
app_1       | == 20201012113301 ReplaceCategorySlugs: migrating =============================
app_1       | == 20201012113301 ReplaceCategorySlugs: migrated (1.1305s) ====================
app_1       |
app_1       | 20:12:14 web.1     | started with pid 8
app_1       | 20:12:14 sidekiq.1 | started with pid 9
app_1       | 20:12:24 sidekiq.1 | 2020-10-31T20:12:24.976Z pid=9 tid=2uk3x INFO: Booting Sidekiq 6.0.7 with redis options {:host=>"redis", :port=>"6379"}
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.496Z pid=9 tid=2uk3x INFO: Booted Rails 5.2.4.4 application in production environment
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.496Z pid=9 tid=2uk3x INFO: Running in ruby 2.6.6p146 (2020-03-31 revision 67876) [arm-linux-musleabihf]
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.496Z pid=9 tid=2uk3x INFO: See LICENSE and the LGPL-3.0 for licensing details.
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.496Z pid=9 tid=2uk3x INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
app_1       | 20:12:32 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-scheduler-3.0.1/lib/sidekiq-scheduler/redis_manager.rb:99:in `block in schedule_exist?')
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.507Z pid=9 tid=2uk3x INFO: Loading Schedule
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.507Z pid=9 tid=2uk3x INFO: Schedule empty! Set Sidekiq.schedule
app_1       | 20:12:32 sidekiq.1 | 2020-10-31T20:12:32.508Z pid=9 tid=2uk3x INFO: Schedules Loaded
app_1       | 20:12:32 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:12:35 web.1     | => Booting Puma
app_1       | 20:12:35 web.1     | => Rails 5.2.4.4 application starting in production
app_1       | 20:12:35 web.1     | => Run `rails server -h` for more startup options
app_1       | 20:12:35 web.1     | Puma starting in single mode...
app_1       | 20:12:35 web.1     | * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
app_1       | 20:12:35 web.1     | * Min threads: 5, max threads: 5
app_1       | 20:12:35 web.1     | * Environment: production
app_1       | 20:12:35 web.1     | * Listening on tcp://0.0.0.0:8383
app_1       | 20:12:35 web.1     | Use Ctrl-C to stop
app_1       | 20:12:37 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:12:42 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:12:47 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:12:52 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:12:57 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:02 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:07 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:12 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:17 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:22 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:27 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:32 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:37 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:42 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:47 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:52 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:13:57 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:02 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:07 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:12 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:17 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:22 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:27 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:32 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:37 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:42 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:47 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:52 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:14:58 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:15:03 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:15:06 web.1     | terminated by SIGKILL
app_1       | 20:15:06 system    | sending SIGTERM to all processes
app_1       | 20:15:06 sidekiq.1 | 2020-10-31T20:15:06.422Z pid=9 tid=2uk3x INFO: Shutting down
app_1       | 20:15:06 sidekiq.1 | 2020-10-31T20:15:06.422Z pid=9 tid=2uk3x INFO: Terminating quiet workers
app_1       | 20:15:06 sidekiq.1 | 2020-10-31T20:15:06.545Z pid=9 tid=dp9jx INFO: Scheduler exiting...
app_1       | 20:15:07 sidekiq.1 | 2020-10-31T20:15:07.046Z pid=9 tid=2uk3x INFO: Pausing to allow workers to finish...
app_1       | 20:15:08 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:15:09 sidekiq.1 | 2020-10-31T20:15:09.050Z pid=9 tid=2uk3x INFO: Bye!
app_1       | 20:15:09 sidekiq.1 | exited with code 0
wreeto_official_app_1 exited with code 0

Please note that I haven't pressed anything, the app quit by itself, as I was just trying to access it.

chrisvel commented 4 years ago

I don't see any issues in the logs... I know this sounds foolish but.. have you tried to docker-compose down docker-compose up ? I will try to set up a VM and do a clean install there.

Ch0wW commented 4 years ago

I did yep.

EDIT: the issue persists. I managed to get a page, but that's the same default error message.

chrisvel commented 4 years ago

I did yep.

EDIT: the issue persists. I managed to get a page, but that's the same default error message.

Can I see the logs of the app? There must be a 500 error there.

Ch0wW commented 4 years ago

Where are they located? There isn't any kind of error message in the logs when I try accessing the page...

chrisvel commented 4 years ago

Can you try a docker-compose exec app bundle exec rake assets:precompile ?

Ch0wW commented 4 years ago

Here's the logs:

pi@RPI3:~/wreeto_official $ docker-compose up -d
Starting wreeto_official_postgres_1 ... done
Starting wreeto_official_redis_1    ... done
Creating wreeto_official_app_1      ... done
pi@RPI3:~/wreeto_official $ docker-compose exec app bundle exec rake assets:precompile
I, [2020-10-31T21:12:06.003548 #14]  INFO -- : Writing /app/wreeto/public/assets/manifest-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js
I, [2020-10-31T21:12:06.005308 #14]  INFO -- : Writing /app/wreeto/public/assets/manifest-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js.gz
I, [2020-10-31T21:12:06.008568 #14]  INFO -- : Writing /app/wreeto/public/assets/accounts-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js
I, [2020-10-31T21:12:06.010413 #14]  INFO -- : Writing /app/wreeto/public/assets/accounts-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js.gz
I, [2020-10-31T21:12:06.012508 #14]  INFO -- : Writing /app/wreeto/public/assets/application-backend-826052360c427e16a36ced9d22be5e4e196cf3dca9261cb4c3e0601d61a0ecde.css
I, [2020-10-31T21:12:06.015143 #14]  INFO -- : Writing /app/wreeto/public/assets/application-backend-826052360c427e16a36ced9d22be5e4e196cf3dca9261cb4c3e0601d61a0ecde.css.gz
I, [2020-10-31T21:12:06.067953 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-82ff0fe46a6f60e0ab3c4a9891a0ae0a1f7b7e84c625f55358379177a2dcb202.eot
I, [2020-10-31T21:12:06.079900 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-82ff0fe46a6f60e0ab3c4a9891a0ae0a1f7b7e84c625f55358379177a2dcb202.eot.gz
I, [2020-10-31T21:12:06.127005 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-fa79d127baca4558a0b973f5f514b90fc5ef43314c41095f5cb285ffaa0a4029.woff2
I, [2020-10-31T21:12:06.134242 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-c9a0a23a23a3f6f7165cba218b40483a0b1750d92b49c40842f1d8f566f5f421.woff
I, [2020-10-31T21:12:06.142603 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-2794b002e3568f5abce8991e2431ca79e0ce84a08ea1268884b4e097b62762a6.ttf
I, [2020-10-31T21:12:06.154600 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-2794b002e3568f5abce8991e2431ca79e0ce84a08ea1268884b4e097b62762a6.ttf.gz
I, [2020-10-31T21:12:06.201343 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-67c6c8e9ffb0fcd7c7c64eaff12a298abf5b54a54b54f0e6c4c49161dba62d6d.svg
I, [2020-10-31T21:12:06.229669 #14]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-67c6c8e9ffb0fcd7c7c64eaff12a298abf5b54a54b54f0e6c4c49161dba62d6d.svg.gz
pi@RPI3:~/wreeto_official $ docker-compose logs
Attaching to wreeto_official_app_1, wreeto_official_postgres_1, wreeto_official_redis_1
postgres_1  |
postgres_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1  |
postgres_1  | 2020-10-31 21:11:09.148 UTC [1] LOG:  starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
postgres_1  | 2020-10-31 21:11:09.149 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres_1  | 2020-10-31 21:11:09.150 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1  | 2020-10-31 21:11:09.174 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2020-10-31 21:11:09.223 UTC [26] LOG:  database system was interrupted; last known up at 2020-10-31 21:04:50 UTC
postgres_1  | 2020-10-31 21:11:11.510 UTC [26] LOG:  database system was not properly shut down; automatic recovery in progress
postgres_1  | 2020-10-31 21:11:11.534 UTC [26] LOG:  redo starts at 0/16D48A8
postgres_1  | 2020-10-31 21:11:11.534 UTC [26] LOG:  invalid record length at 0/16D4990: wanted 24, got 0
postgres_1  | 2020-10-31 21:11:11.534 UTC [26] LOG:  redo done at 0/16D4958
postgres_1  | 2020-10-31 21:11:11.637 UTC [1] LOG:  database system is ready to accept connections
app_1       | 21:11:32 web.1     | started with pid 11
app_1       | 21:11:32 sidekiq.1 | started with pid 12
app_1       | 21:11:43 sidekiq.1 | 2020-10-31T21:11:43.287Z pid=12 tid=9s8js INFO: Booting Sidekiq 6.0.7 with redis options {:host=>"redis", :port=>"6379"}
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.746Z pid=12 tid=9s8js INFO: Booted Rails 5.2.4.4 application in production environment
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.747Z pid=12 tid=9s8js INFO: Running in ruby 2.6.6p146 (2020-03-31 revision 67876) [arm-linux-musleabihf]
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.747Z pid=12 tid=9s8js INFO: See LICENSE and the LGPL-3.0 for licensing details.
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.747Z pid=12 tid=9s8js INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
app_1       | 21:11:49 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-scheduler-3.0.1/lib/sidekiq-scheduler/redis_manager.rb:99:in `block in schedule_exist?')
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.759Z pid=12 tid=9s8js INFO: Loading Schedule
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.760Z pid=12 tid=9s8js INFO: Schedule empty! Set Sidekiq.schedule
app_1       | 21:11:49 sidekiq.1 | 2020-10-31T21:11:49.760Z pid=12 tid=9s8js INFO: Schedules Loaded
app_1       | 21:11:49 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:11:54 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:11:59 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:04 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:09 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:13 web.1     | => Booting Puma
app_1       | 21:12:13 web.1     | => Rails 5.2.4.4 application starting in production
app_1       | 21:12:13 web.1     | => Run `rails server -h` for more startup options
app_1       | 21:12:13 web.1     | Puma starting in single mode...
app_1       | 21:12:13 web.1     | * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
app_1       | 21:12:13 web.1     | * Min threads: 5, max threads: 5
app_1       | 21:12:13 web.1     | * Environment: production
app_1       | 21:12:13 web.1     | * Listening on tcp://0.0.0.0:8383
app_1       | 21:12:13 web.1     | Use Ctrl-C to stop
app_1       | 21:12:14 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:19 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:24 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:29 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:34 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 21:12:39 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
redis_1     | 1:C 31 Oct 2020 21:11:07.997 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1     | 1:C 31 Oct 2020 21:11:07.997 # Redis version=5.0.7, bits=32, commit=00000000, modified=0, pid=1, just started
redis_1     | 1:C 31 Oct 2020 21:11:07.997 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1     | 1:M 31 Oct 2020 21:11:08.002 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
redis_1     | 1:M 31 Oct 2020 21:11:08.003 * Running mode=standalone, port=6379.
redis_1     | 1:M 31 Oct 2020 21:11:08.004 # Server initialized
redis_1     | 1:M 31 Oct 2020 21:11:08.004 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1     | 1:M 31 Oct 2020 21:11:08.004 * Ready to accept connections
pi@RPI3:~/wreeto_official

App still outputs the same error message.

chrisvel commented 4 years ago

I added a flag which displays more verbose code errors, so you may docker-compose pull in some minutes and try again.

EDIT: I believe I found the error, I added accounts for users and it might be blank. I will prepare a patch and deploy.

Ch0wW commented 4 years ago

In case of, here's the error found: error

chrisvel commented 4 years ago

@Ch0wW can you please docker-compose exec app bundle exec rake assets:clobber, then docker-compose exec app bundle exec rake assets:precompile and then down/up docker-compose ? It deletes all assets and precompiles them again.

Ch0wW commented 4 years ago

The first command can't be executed properly :

pi@RPI3:~/wreeto_official $ docker-compose exec app bundle exec rake assets:clobber
rake aborted!
Errno::EBUSY: Resource busy @ dir_s_rmdir - /app/wreeto/public/assets
/usr/local/bundle/gems/sprockets-4.0.2/lib/sprockets/manifest.rb:269:in `clobber'
/usr/local/bundle/gems/sprockets-rails-3.2.2/lib/sprockets/rails/task.rb:81:in `block (3 levels) in define'
/usr/local/bundle/gems/sprockets-4.0.2/lib/rake/sprocketstask.rb:148:in `with_logger'
/usr/local/bundle/gems/sprockets-rails-3.2.2/lib/sprockets/rails/task.rb:80:in `block (2 levels) in define'
/usr/local/bundle/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `load'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:74:in `kernel_load'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/cli/exec.rb:28:in `run'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/cli.rb:465:in `exec'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/cli.rb:27:in `dispatch'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/cli.rb:18:in `start'
/usr/local/bundle/gems/bundler-2.0.2/exe/bundle:30:in `block in <top (required)>'
/usr/local/bundle/gems/bundler-2.0.2/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/usr/local/bundle/gems/bundler-2.0.2/exe/bundle:22:in `<top (required)>'
/usr/local/bundle/bin/bundle:23:in `load'
/usr/local/bundle/bin/bundle:23:in `<main>'
Tasks: TOP => assets:clobber
(See full trace by running task with --trace)

After using the first command...

pi@RPI3:~/wreeto_official $ docker-compose exec app bundle exec rake assets:precompile
I, [2020-11-02T20:45:04.051010 #71]  INFO -- : Writing /app/wreeto/public/assets/manifest-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js
I, [2020-11-02T20:45:04.052770 #71]  INFO -- : Writing /app/wreeto/public/assets/manifest-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js.gz
I, [2020-11-02T20:45:04.055215 #71]  INFO -- : Writing /app/wreeto/public/assets/accounts-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js
I, [2020-11-02T20:45:04.056544 #71]  INFO -- : Writing /app/wreeto/public/assets/accounts-04024382391bb910584145d8113cf35ef376b55d125bb4516cebeb14ce788597.js.gz
I, [2020-11-02T20:45:04.059001 #71]  INFO -- : Writing /app/wreeto/public/assets/application-backend-826052360c427e16a36ced9d22be5e4e196cf3dca9261cb4c3e0601d61a0ecde.css
I, [2020-11-02T20:45:04.062209 #71]  INFO -- : Writing /app/wreeto/public/assets/application-backend-826052360c427e16a36ced9d22be5e4e196cf3dca9261cb4c3e0601d61a0ecde.css.gz
I, [2020-11-02T20:45:04.117502 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-82ff0fe46a6f60e0ab3c4a9891a0ae0a1f7b7e84c625f55358379177a2dcb202.eot
I, [2020-11-02T20:45:04.129744 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-82ff0fe46a6f60e0ab3c4a9891a0ae0a1f7b7e84c625f55358379177a2dcb202.eot.gz
I, [2020-11-02T20:45:04.178944 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-fa79d127baca4558a0b973f5f514b90fc5ef43314c41095f5cb285ffaa0a4029.woff2
I, [2020-11-02T20:45:04.186066 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-c9a0a23a23a3f6f7165cba218b40483a0b1750d92b49c40842f1d8f566f5f421.woff
I, [2020-11-02T20:45:04.194328 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-2794b002e3568f5abce8991e2431ca79e0ce84a08ea1268884b4e097b62762a6.ttf
I, [2020-11-02T20:45:04.205966 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-2794b002e3568f5abce8991e2431ca79e0ce84a08ea1268884b4e097b62762a6.ttf.gz
I, [2020-11-02T20:45:04.253008 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-67c6c8e9ffb0fcd7c7c64eaff12a298abf5b54a54b54f0e6c4c49161dba62d6d.svg
I, [2020-11-02T20:45:04.283714 #71]  INFO -- : Writing /app/wreeto/public/assets/fontawesome-webfont-67c6c8e9ffb0fcd7c7c64eaff12a298abf5b54a54b54f0e6c4c49161dba62d6d.svg.gz
pi@RPI3:~/wreeto_official $ docker-compose down
Stopping wreeto_official_postgres_1 ... done
Stopping wreeto_official_redis_1    ... done
Removing wreeto_official_app_1      ... done
Removing wreeto_official_postgres_1 ... done
Removing wreeto_official_redis_1    ... done
Removing network wreeto_official_default
pi@RPI3:~/wreeto_official $ docker-compose up
Creating network "wreeto_official_default" with the default driver
Creating wreeto_official_postgres_1 ... done
Creating wreeto_official_redis_1    ... done
Creating wreeto_official_app_1      ... done
Attaching to wreeto_official_postgres_1, wreeto_official_redis_1, wreeto_official_app_1
postgres_1  |
redis_1     | 1:C 02 Nov 2020 20:45:37.085 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1     | 1:C 02 Nov 2020 20:45:37.085 # Redis version=5.0.7, bits=32, commit=00000000, modified=0, pid=1, just started
redis_1     | 1:C 02 Nov 2020 20:45:37.085 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1     | 1:M 02 Nov 2020 20:45:37.093 # Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
postgres_1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
redis_1     | 1:M 02 Nov 2020 20:45:37.095 * Running mode=standalone, port=6379.
redis_1     | 1:M 02 Nov 2020 20:45:37.095 # Server initialized
redis_1     | 1:M 02 Nov 2020 20:45:37.096 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1     | 1:M 02 Nov 2020 20:45:37.096 * Ready to accept connections
postgres_1  |
postgres_1  | 2020-11-02 20:45:38.299 UTC [1] LOG:  starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on arm-unknown-linux-gnueabihf, compiled by gcc (Debian 8.3.0-6) 8.3.0, 32-bit
postgres_1  | 2020-11-02 20:45:38.302 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres_1  | 2020-11-02 20:45:38.302 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1  | 2020-11-02 20:45:38.331 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1  | 2020-11-02 20:45:38.367 UTC [26] LOG:  database system was shut down at 2020-11-02 20:45:21 UTC
postgres_1  | 2020-11-02 20:45:38.407 UTC [1] LOG:  database system is ready to accept connections
app_1       | 20:45:56 web.1     | started with pid 8
app_1       | 20:45:56 sidekiq.1 | started with pid 9
app_1       | 20:46:07 sidekiq.1 | 2020-11-02T20:46:07.016Z pid=9 tid=3n03x INFO: Booting Sidekiq 6.0.7 with redis options {:host=>"redis", :port=>"6379"}
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.864Z pid=9 tid=3n03x INFO: Booted Rails 5.2.4.4 application in production environment
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.864Z pid=9 tid=3n03x INFO: Running in ruby 2.6.6p146 (2020-03-31 revision 67876) [arm-linux-musleabihf]
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.864Z pid=9 tid=3n03x INFO: See LICENSE and the LGPL-3.0 for licensing details.
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.864Z pid=9 tid=3n03x INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
app_1       | 20:46:13 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-scheduler-3.0.1/lib/sidekiq-scheduler/redis_manager.rb:99:in `block in schedule_exist?')
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.877Z pid=9 tid=3n03x INFO: Loading Schedule
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.877Z pid=9 tid=3n03x INFO: Schedule empty! Set Sidekiq.schedule
app_1       | 20:46:13 sidekiq.1 | 2020-11-02T20:46:13.877Z pid=9 tid=3n03x INFO: Schedules Loaded
app_1       | 20:46:13 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:46:18 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:46:23 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:46:28 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:46:28 web.1     | => Booting Puma
app_1       | 20:46:28 web.1     | => Rails 5.2.4.4 application starting in production
app_1       | 20:46:28 web.1     | => Run `rails server -h` for more startup options
app_1       | 20:46:28 web.1     | Puma starting in single mode...
app_1       | 20:46:28 web.1     | * Version 4.3.5 (ruby 2.6.6-p146), codename: Mysterious Traveller
app_1       | 20:46:28 web.1     | * Min threads: 5, max threads: 5
app_1       | 20:46:28 web.1     | * Environment: production
app_1       | 20:46:29 web.1     | * Listening on tcp://0.0.0.0:8383
app_1       | 20:46:29 web.1     | Use Ctrl-C to stop
app_1       | 20:46:33 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:46:38 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
app_1       | 20:46:43 sidekiq.1 | `Redis#exists(key)` will return an Integer in redis-rb 4.3. `exists?` returns a boolean, you should use it instead. To opt-in to the new behavior now you can set Redis.exists_returns_integer =  true. To disable this message and keep the current (boolean) behaviour of 'exists' you can set `Redis.exists_returns_integer = false`, but this option will be removed in 5.0. (/usr/local/bundle/gems/sidekiq-6.0.7/lib/sidekiq/launcher.rb:160:in `block (2 levels) in ❤')
♥Gracefully stopping... (press Ctrl+C again to force)
Stopping wreeto_official_app_1      ...
Stopping wreeto_official_postgres_1 ...
Stopping wreeto_official_redis_1    ...
Killing wreeto_official_app_1       ... done
Killing wreeto_official_postgres_1  ... done
Killing wreeto_official_redis_1     ... done

Error is the same:

chrisvel commented 4 years ago

Then you can remove them manually with docker-compose exec app rm -rf app/wreeto/public/assets and run docker-compose exec app bundle exec rake assets:precompile again. If they don't get removed, nothing will change with the next command.

Ch0wW commented 4 years ago

Unfortunately, nothing changes... The actions are successful, but I have the same error messages as earlier.

chrisvel commented 4 years ago

@Ch0wW I forced precompilation of application.js the file that seems to have the issue in your image. Can you please pull your docker images and retry ?

https://github.com/chrisvel/wreeto_official/commit/9ac7751c51d6a4057ccb6c6fd1be6e9ab3cb5409

Ch0wW commented 4 years ago

Looks like that was the culprit, application now works again!

chrisvel commented 4 years ago

@Ch0wW Phew! I am sorry that it took a lot of time to be solved!

chrisvel / wreeto_official

"We're sorry, but something went wrong." after updating the image #47