Please fill in the questionnaire below.
Technical Help Questionnaire
Answer: YES
Self-Hosted Installation and Setup Questions
Delete this section if you are using Baserow.io.
How have you self-hosted Baserow.
Heroku, using the one-click install template
What are the specs of the service or server you are using to host Baserow.
Perfomrance Dyno 2.5GB ram
Which version of Baserow are you using.
The latest one that would have been installed with the one click template today
How have you configured your self-hosted installation?
It is auto configured
What commands if any did you use to start your Baserow server?
Heroku does it automatically
Describe the problem
App keeps crashing. See attached logs.
Describe, step by step, how to reproduce the error or problem you are encountering.
Try and install and launch the app on heroku using the one click template. I ALSO GOT THE SAME ERROR when I pushed the latest version to heroku using CLI
Provide screenshots or include share links showing:
N/A
How many rows in total do you have in your Baserow tables?
Please attach full logs from all of Baserow’s services
2024-02-24T00:34:32.247036+00:00 app[web.1]: {“level”:“info”,“ts”:1708734872.2469656,“logger”:“tls”,“msg”:“finished cleaning storage units”}
2024-02-24T00:34:32.247037+00:00 app[web.1]: run: loading initial config: loading new config: http app module: start: tcp: listening on :443: listen tcp :443: bind: permission denied
2024-02-24T00:34:32.248744+00:00 app[web.1]: 2024-02-24 00:34:32,248 INFO exited: caddy (exit status 1; not expected)
2024-02-24T00:34:32.248757+00:00 app[web.1]: 2024-02-24 00:34:32,248 INFO exited: caddy (exit status 1; not expected)
2024-02-24T00:34:33.250151+00:00 app[web.1]: 2024-02-24 00:34:33,250 INFO gave up: caddy entered FATAL state, too many start retries too quickly
2024-02-24T00:34:33.250224+00:00 app[web.1]: 2024-02-24 00:34:33,250 INFO gave up: caddy entered FATAL state, too many start retries too quickly
2024-02-24T00:34:34.251644+00:00 app[web.1]: e[31mBaserow was stopped or one of it’s services crashed, see the logs above for more details. e[0m
2024-02-24T00:34:35.252996+00:00 app[web.1]: 2024-02-24 00:34:35,252 WARN received SIGTERM indicating exit request
2024-02-24T00:34:35.253061+00:00 app[web.1]: 2024-02-24 00:34:35,252 WARN received SIGTERM indicating exit request
2024-02-24T00:34:35.253143+00:00 app[web.1]: 2024-02-24 00:34:35,253 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:35.253145+00:00 app[web.1]: 2024-02-24 00:34:35,253 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:35.409561+00:00 app[web.1]: 127.0.0.1:44582 - “GET /api/_health/ HTTP/1.1” 200
2024-02-24T00:34:35.411190+00:00 app[web.1]: =======================================================================
2024-02-24T00:34:35.411191+00:00 app[web.1]: e[32mBaserow is now available at https://investor-list-2024-brandooo.herokuapp.come[0m
2024-02-24T00:34:35.411191+00:00 app[web.1]: =======================================================================
2024-02-24T00:34:38.414268+00:00 app[web.1]: 2024-02-24 00:34:38,414 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:38.414334+00:00 app[web.1]: 2024-02-24 00:34:38,414 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:40.382542+00:00 app[web.1]: celery beat v5.2.7 (dawn-chorus) is starting.
2024-02-24T00:34:42.400463+00:00 app[web.1]: 2024-02-24 00:34:42,390 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:42.401848+00:00 app[web.1]: 2024-02-24 00:34:42,390 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:43.052958+00:00 app[web.1]: WARNING 2024-02-24 00:34:43,052 kombu.connection._init_params:246- Secure redis scheme specified (rediss) with no ssl options, defaulting to insecure SSL behaviour.
2024-02-24T00:34:43.054217+00:00 app[web.1]: __ - … __ - _
2024-02-24T00:34:43.054217+00:00 app[web.1]: LocalTime → 2024-02-24 00:34:43
2024-02-24T00:34:43.054218+00:00 app[web.1]: Configuration →
2024-02-24T00:34:43.054218+00:00 app[web.1]: . broker → rediss://:@ec2-52-21-59-81.compute-1.amazonaws.com:7420//
2024-02-24T00:34:43.054218+00:00 app[web.1]: . loader → celery.loaders.app.AppLoader
2024-02-24T00:34:43.054219+00:00 app[web.1]: . scheduler → redbeat.schedulers.RedBeatScheduler
2024-02-24T00:34:43.054219+00:00 app[web.1]: . redis → rediss://:@ec2-52-21-59-81.compute-1.amazonaws.com:7420/
2024-02-24T00:34:43.054219+00:00 app[web.1]: . lock → redbeat::lock 1.33 minutes (80s)
2024-02-24T00:34:43.054220+00:00 app[web.1]: . logfile → [stderr]@%INFO
2024-02-24T00:34:43.054220+00:00 app[web.1]: . maxinterval → 20.00 seconds (20s)
2024-02-24T00:34:43.054228+00:00 app[web.1]: [2024-02-24 00:34:43,053: INFO/MainProcess] beat: Starting…
2024-02-24T00:34:43.099391+00:00 app[web.1]: [2024-02-24 00:34:43,099: WARNING/MainProcess] Secure redis scheme specified (rediss) with no ssl options, defaulting to insecure SSL behaviour.
2024-02-24T00:34:46.103042+00:00 app[web.1]: 2024-02-24 00:34:46,102 WARN killing ‘beatworker’ (92) with SIGKILL
2024-02-24T00:34:46.103096+00:00 app[web.1]: 2024-02-24 00:34:46,102 WARN killing ‘beatworker’ (92) with SIGKILL
2024-02-24T00:34:46.113628+00:00 app[web.1]: 2024-02-24 00:34:46,113 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:46.113633+00:00 app[web.1]: 2024-02-24 00:34:46,113 INFO waiting for processes, baserow-watcher, backend, celeryworker, exportworker, webfrontend, beatworker to die
2024-02-24T00:34:46.136116+00:00 app[web.1]: 2024-02-24 00:34:46,136 INFO stopped: beatworker (terminated by SIGKILL)
2024-02-24T00:34:46.136120+00:00 app[web.1]: 2024-02-24 00:34:46,136 INFO stopped: beatworker (terminated by SIGKILL)
2024-02-24T00:34:46.161037+00:00 app[web.1]: 2024-02-24 00:34:46,160 INFO stopped: webfrontend (terminated by SIGTERM)
2024-02-24T00:34:46.161042+00:00 app[web.1]: 2024-02-24 00:34:46,160 INFO stopped: webfrontend (terminated by SIGTERM)
2024-02-24T00:34:47.172008+00:00 app[web.1]: 2024-02-24 00:34:47,171 INFO stopped: exportworker (terminated by SIGTERM)
2024-02-24T00:34:47.172064+00:00 app[web.1]: 2024-02-24 00:34:47,171 INFO stopped: exportworker (terminated by SIGTERM)
2024-02-24T00:34:47.191305+00:00 app[web.1]:
2024-02-24T00:34:47.191306+00:00 app[web.1]: worker: Warm shutdown (MainProcess)
2024-02-24T00:34:49.193747+00:00 app[web.1]: 2024-02-24 00:34:49,192 INFO waiting for processes, baserow-watcher, backend, celeryworker to die
2024-02-24T00:34:49.193806+00:00 app[web.1]: 2024-02-24 00:34:49,192 INFO waiting for processes, baserow-watcher, backend, celeryworker to die
2024-02-24T00:34:51.729974+00:00 app[web.1]: 2024-02-24 00:34:51,729 INFO stopped: celeryworker (exit status 0)
2024-02-24T00:34:51.730038+00:00 app[web.1]: 2024-02-24 00:34:51,729 INFO stopped: celeryworker (exit status 0)
2024-02-24T00:34:51.868304+00:00 app[web.1]: [2024-02-24 00:34:51 +0000] [88] [INFO] Handling signal: term
2024-02-24T00:34:52.009830+00:00 app[web.1]: [2024-02-24 00:34:51 +0000] [251] [INFO] Shutting down
2024-02-24T00:34:52.118805+00:00 app[web.1]: INFO 2024-02-24 00:34:52,045 gunicorn.error.info:264- Error while closing socket [Errno 9] Bad file descriptor
2024-02-24T00:34:52.119364+00:00 app[web.1]: INFO 2024-02-24 00:34:52,045 gunicorn.error.info:264- Error while closing socket [Errno 9] Bad file descriptor
2024-02-24T00:34:52.238115+00:00 app[web.1]: [2024-02-24 00:34:52 +0000] [251] [INFO] Finished server process [251]
2024-02-24T00:34:52.238229+00:00 app[web.1]: 2024-02-24 00:34:52,238 INFO waiting for processes, baserow-watcher, backend to die
2024-02-24T00:34:52.238230+00:00 app[web.1]: 2024-02-24 00:34:52,238 INFO waiting for processes, baserow-watcher, backend to die
2024-02-24T00:34:52.289144+00:00 app[web.1]: INFO 2024-02-24 00:34:52,288 gunicorn.error.info:264- Worker exiting (pid: 251)
2024-02-24T00:34:52.289204+00:00 app[web.1]: INFO 2024-02-24 00:34:52,288 gunicorn.error.info:264- Worker exiting (pid: 251)
2024-02-24T00:34:53.710966+00:00 app[web.1]: [2024-02-24 00:34:53 +0000] [88] [INFO] Shutting down: Master
2024-02-24T00:34:30.000000+00:00 app[heroku-redis]: source=REDIS addon=redis-angular-02786 sample#active-connections=1 sample#load-avg-1m=1.045 sample#load-avg-5m=1.35 sample#load-avg-15m=1.19 sample#read-iops=0 sample#write-iops=0.93684 sample#memory-total=16070700kB sample#memory-free=10258388kB sample#memory-cached=2918224kB sample#memory-redis=513856bytes sample#hit-rate=1 sample#evicted-keys=0
2024-02-24T00:34:54.336130+00:00 app[web.1]: 2024-02-24 00:34:54,336 INFO stopped: backend (exit status 0)
2024-02-24T00:34:54.336194+00:00 app[web.1]: 2024-02-24 00:34:54,336 INFO stopped: backend (exit status 0)
2024-02-24T00:34:55.338440+00:00 app[web.1]: 2024-02-24 00:34:55,338 INFO waiting for processes, baserow-watcher to die
2024-02-24T00:34:55.338522+00:00 app[web.1]: 2024-02-24 00:34:55,338 INFO waiting for processes, baserow-watcher to die
2024-02-24T00:34:55.414255+00:00 app[web.1]: 2024-02-24 00:34:55,413 INFO stopped: baserow-watcher (terminated by SIGTERM)
2024-02-24T00:34:55.414271+00:00 app[web.1]: 2024-02-24 00:34:55,413 INFO stopped: baserow-watcher (terminated by SIGTERM)
2024-02-24T00:34:55.420953+00:00 app[web.1]: 2024-02-24 00:34:55,420 INFO stopped: processes (terminated by SIGTERM)
2024-02-24T00:34:55.420955+00:00 app[web.1]: 2024-02-24 00:34:55,420 INFO stopped: processes (terminated by SIGTERM)
2024-02-24T00:34:56.845985+00:00 heroku[web.1]: Process exited with status 0
2024-02-24T00:34:56.867113+00:00 heroku[web.1]: State changed from starting to crashed
2024-02-24T00:34:56.869446+00:00 heroku[web.1]: State changed from crashed to starting