Error from daemon when installing Baserow on VDS

Technical Help
,
1

Hi all.
I really need your help.
Baserow can not install on my server. There is an error.
Error response from daemon: Cannot restart container 667a5c13b4f89c61624cdbb00a2 06f2fcd97e2d27c0008edab6285e4b842eb55: driver failed programming external connec tivity on endpoint baserow-caddy-1 (1b1ba74b3c21b280b9924ebe68b1e0c0924798560689 f9c6070d10e6a4aa6836): Bind for 0.0.0.0:443 failed: port is already allocated

I have n8n and traefik running in docker compose on my server and they are probably occupying port 443.
Can you tell me how to install Baserow so it doesn’t conflict with other applications?

Screenshot_243
Screenshot_243864×390 36.5 KB

2

Hi @SimpleMake ,

Do you want to use our more complex one service per container docker-compose file for a particular reason? If not I’d recommend sticking with our simpler version:

version: "3.4"
services:
  baserow:
    container_name: baserow
    image: baserow/baserow:1.10.2
    environment:
      BASEROW_PUBLIC_URL: 'http://localhost'
    ports:
      - "80:80"
    volumes:
      - baserow_data:/baserow/data
volumes:
  baserow_data:

If you want to stick with your current compose file all you need to do is remove the following line from your caddy service ports section:

      - "${HOST_PUBLISH_IP:-0.0.0.0}:${WEB_FRONTEND_SSL_PORT:-443}:443"
3

Hello, @nigel .
Thank you for your reply.
I am using the simple option that you suggested to me. There is still an error.

Error response from daemon: Cannot restart container dc63c01c764e6dbcb3efdf9d141e87fed4d6c4763240d5af4712c3e08d0de6df: driver failed programming external connectivity on endpoint baserow (4679b92479778646db1db39708a129e981836c015a76c72d0fe27cda6f9bc8b2): Bind for 0.0.0.0:80 failed: port is already allocated

The installer does not like the standard port

4

@SimpleMake You can simply change the left hand port number to whatever port is free on your system!

version: "3.4"
services:
  baserow:
    container_name: baserow
    image: baserow/baserow:1.10.2
    environment:
      BASEROW_PUBLIC_URL: 'http://localhost'
    ports:
      - "CHANGE_ME:80"
    volumes:
      - baserow_data:/baserow/data
volumes:
  baserow_data:

If you are using Traefik however don’t you want to configure Baserow to be proxied by trafiek? If so you can instead do something like:

version: "3.4"
services:
  baserow:
    image: baserow/baserow:1.10.2
    container_name: baserow
    labels:
        # Explicitly tell Traefik to expose this container
        - "traefik.enable=true"
        # The domain the service will respond to
        - "traefik.http.routers.baserow.rule=Host(`domain.com`)"
    environment:
      - BASEROW_PUBLIC_URL=https://domain.com
    volumes:
      - baserow_data:/baserow/data
volumes:
  baserow_data:
5

@nigel, can you tell me what the problem may be? Not enough server resources?

baserow_1  | 2022-07-26 14:57:49,988 INFO exited: beatworker (exit status 1; not expected)
baserow_1  | 2022-07-26 14:57:49,988 INFO exited: beatworker (exit status 1; not expected)
baserow_1  | 2022-07-26 14:57:49,993 INFO reaped unknown pid 426
baserow_1  | 2022-07-26 14:57:49,993 INFO reaped unknown pid 426
baserow_1  | 2022-07-26 14:57:50,007 INFO spawned: 'beatworker' with pid 554
baserow_1  | 2022-07-26 14:57:50,007 INFO spawned: 'beatworker' with pid 554
baserow_1  | Baserow was stopped or one of it's services crashed, see the logs above for more details.
baserow_1  | 2022-07-26 14:57:50,051 WARN received SIGTERM indicating exit request
baserow_1  | 2022-07-26 14:57:50,051 WARN received SIGTERM indicating exit request
baserow_1  | 2022-07-26 14:57:50,052 INFO waiting for processes, postgresql, baserow-watcher, beatworker, redis, c                   eleryworker, webfrontend, caddy, exportworker, backend to die
baserow_1  | 2022-07-26 14:57:50,052 INFO waiting for processes, postgresql, baserow-watcher, beatworker, redis, c                   eleryworker, webfrontend, caddy, exportworker, backend to die
baserow_1  | 2022-07-26 14:57:50,486 INFO stopped: beatworker (terminated by SIGQUIT (core dumped))
baserow_1  | 2022-07-26 14:57:50,486 INFO stopped: beatworker (terminated by SIGQUIT (core dumped))
baserow_1  |  [WEBFRONTEND][2022-07-26 14:57:50] ℹ Listening on: http://localhost:3000/
baserow_1  | 2022-07-26 14:57:50,591 INFO stopped: webfrontend (terminated by SIGTERM)
baserow_1  | 2022-07-26 14:57:50,591 INFO stopped: webfrontend (terminated by SIGTERM)
baserow_1  | 2022-07-26 14:57:50,592 INFO reaped unknown pid 413
baserow_1  | 2022-07-26 14:57:50,592 INFO reaped unknown pid 413
baserow_1  |  [BACKEND][2022-07-26 14:57:50] [2022-07-26 14:57:44 +0000] [551] [INFO] Booting worker with pid: 551                   
baserow_1  |  [BASEROW-WATCHER][2022-07-26 14:57:50] Waiting for Baserow to become available, this might take 30+                    seconds...
baserow_1  |  [BACKEND][2022-07-26 14:57:50] [2022-07-26 14:57:50 +0000] [247] [INFO] Handling signal: term
baserow_1  |  [BACKEND][2022-07-26 14:57:50] [2022-07-26 14:57:50 +0000] [247] [WARNING] Worker with pid 551 was t                   erminated due to signal 15
baserow_1  |  [BACKEND][2022-07-26 14:57:50] [2022-07-26 14:57:50 +0000] [247] [WARNING] Worker with pid 549 was t                   erminated due to signal 15
baserow_1  |  [BACKEND][2022-07-26 14:57:50] [2022-07-26 14:57:50 +0000] [247] [WARNING] Worker with pid 550 was t                   erminated due to signal 15
baserow_1  |  [BACKEND][2022-07-26 14:57:50] [2022-07-26 14:57:50 +0000] [247] [INFO] Shutting down: Master
baserow_1  | 2022-07-26 14:57:50,814 INFO stopped: backend (exit status 0)
baserow_1  | 2022-07-26 14:57:50,814 INFO stopped: backend (exit status 0)
baserow_1  | 2022-07-26 14:57:50,815 INFO reaped unknown pid 402
baserow_1  | 2022-07-26 14:57:50,815 INFO reaped unknown pid 402
baserow_1  |  [EXPORT_WORKER][2022-07-26 14:57:50] [2022-07-26 14:57:42,534: INFO/MainProcess] missed heartbeat fr                   om default-worker@2ed4c6bab081
baserow_1  |  [EXPORT_WORKER][2022-07-26 14:57:50]
baserow_1  |  [EXPORT_WORKER][2022-07-26 14:57:51] worker: Warm shutdown (MainProcess)
2022-07-26 14:57:53,550 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker, caddy, expor                   tworker to die
baserow_1  | 2022-07-26 14:57:53,550 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker,                    caddy, exportworker to die
baserow_1  | 2022-07-26 14:57:56,554 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker,                    caddy, exportworker to die
baserow_1  | 2022-07-26 14:57:56,554 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker,                    caddy, exportworker to die
baserow_1  |  [EXPORT_WORKER][2022-07-26 14:57:56] Syncing Baserow templates. Disable by setting BASEROW_TRIGGER_S                   YNC_TEMPLATES_AFTER_MIGRATION=false.:   2%|2         | 1/50 [02:03<1:40:29, 123.06s/it]
2022-07-26 14:57:59,707 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker, caddy, expor                   tworker to die
baserow_1  | 2022-07-26 14:57:59,707 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker,                    caddy, exportworker to die
baserow_1  |  [EXPORT_WORKER][2022-07-26 14:58:00] Syncing Baserow templates. Disable by setting BASEROW_TRIGGER_S                   YNC_TEMPLATES_AFTER_MIGRATION=false.:   4%|4         | 2/50 [02:08<42:57, 53.70s/it]
 [BASEROW-WATCHER][2022-07-26 14:58:00] Waiting for Baserow to become available, this might take 30+ seconds...
baserow_1  | 2022-07-26 14:58:01,676 WARN killing 'exportworker' (238) with SIGKILL
baserow_1  | 2022-07-26 14:58:01,676 WARN killing 'exportworker' (238) with SIGKILL
baserow_1  | 2022-07-26 14:58:01,699 INFO stopped: exportworker (terminated by SIGKILL)
baserow_1  | 2022-07-26 14:58:01,699 INFO stopped: exportworker (terminated by SIGKILL)
baserow_1  |  [CELERY_WORKER][2022-07-26 14:58:01] [2022-07-26 14:57:42,495: INFO/MainProcess] missed heartbeat fr                   om export-worker@2ed4c6bab081
baserow_1  |  [CELERY_WORKER][2022-07-26 14:58:01]
baserow_1  |  [POSTGRES][2022-07-26 14:58:01] 2022-07-26 14:55:29.643 UTC [227] LOG:  database system is ready to                    accept connections
baserow_1  |  [POSTGRES][2022-07-26 14:58:01] 2022-07-26 14:58:01.740 UTC [530] baserow@baserow LOG:  could not re                   ceive data from client: Connection reset by peer
baserow_1  | 2022-07-26 14:58:01,747 INFO reaped unknown pid 382
baserow_1  | 2022-07-26 14:58:01,747 INFO reaped unknown pid 382
baserow_1  | 2022-07-26 14:58:01,750 INFO reaped unknown pid 526
baserow_1  | 2022-07-26 14:58:01,750 INFO reaped unknown pid 526
baserow_1  | 2022-07-26 14:58:02,753 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker,                    caddy to die
baserow_1  | 2022-07-26 14:58:02,753 INFO waiting for processes, postgresql, baserow-watcher, redis, celeryworker,                    caddy to die
baserow_1  |  [CELERY_WORKER][2022-07-26 14:58:03] worker: Warm shutdown (MainProcess)
baserow_1  | 2022-07-26 14:58:03,807 INFO stopped: celeryworker (exit status 0)
baserow_1  | 2022-07-26 14:58:03,807 INFO stopped: celeryworker (exit status 0)
baserow_1  | 2022-07-26 14:58:03,808 INFO reaped unknown pid 369
baserow_1  | 2022-07-26 14:58:03,808 INFO reaped unknown pid 369
baserow_1  |  [CADDY][2022-07-26 14:58:03] {"level":"info","ts":1658847329.4867127,"logger":"tls","msg":"finished                    cleaning storage units"}
baserow_1  |  [CADDY][2022-07-26 14:58:03] {"level":"info","ts":1658847483.8172839,"msg":"shutting down apps, then                    terminating","signal":"SIGTERM"}
baserow_1  |  [CADDY][2022-07-26 14:58:03] {"level":"warn","ts":1658847483.822033,"msg":"exiting; byeee!! 👋","sig                   nal":"SIGTERM"}
baserow_1  |  [CADDY][2022-07-26 14:58:03] {"level":"info","ts":1658847483.8374321,"logger":"tls.cache.maintenance                   ","msg":"stopped background certificate maintenance","cache":"0xc00027ed90"}
baserow_1  |  [CADDY][2022-07-26 14:58:03] {"level":"info","ts":1658847483.8458488,"logger":"admin","msg":"stopped                    previous server","address":"tcp/localhost:2019"}
baserow_1  |  [CADDY][2022-07-26 14:58:03] {"level":"info","ts":1658847483.8474753,"msg":"shutdown complete","sign                   al":"SIGTERM","exit_code":0}
baserow_1  | 2022-07-26 14:58:03,852 INFO stopped: caddy (exit status 0)
baserow_1  | 2022-07-26 14:58:03,852 INFO stopped: caddy (exit status 0)
baserow_1  | 2022-07-26 14:58:03,853 INFO reaped unknown pid 330
baserow_1  | 2022-07-26 14:58:03,853 INFO reaped unknown pid 330
baserow_1  |  [REDIS][2022-07-26 14:58:03] 229:M 26 Jul 2022 14:55:29.010 * Ready to accept connections
baserow_1  |  [REDIS][2022-07-26 14:58:03] 229:signal-handler (1658847483) Received SIGTERM scheduling shutdown...                   
baserow_1  |  [REDIS][2022-07-26 14:58:03] 229:M 26 Jul 2022 14:58:03.945 # User requested shutdown...
baserow_1  |  [REDIS][2022-07-26 14:58:03] 229:M 26 Jul 2022 14:58:03.945 # Redis is now ready to exit, bye bye...                   
baserow_1  | 2022-07-26 14:58:03,953 INFO stopped: redis (exit status 0)
baserow_1  | 2022-07-26 14:58:03,953 INFO stopped: redis (exit status 0)
baserow_1  | 2022-07-26 14:58:03,953 INFO reaped unknown pid 341
baserow_1  | 2022-07-26 14:58:03,953 INFO reaped unknown pid 341
baserow_1  | 2022-07-26 14:58:03,955 INFO stopped: baserow-watcher (terminated by SIGTERM)
baserow_1  | 2022-07-26 14:58:03,955 INFO stopped: baserow-watcher (terminated by SIGTERM)
baserow_1  |  [POSTGRES][2022-07-26 14:58:03] 2022-07-26 14:58:01.740 UTC [530] baserow@baserow LOG:  unexpected E                   OF on client connection with an open transaction
baserow_1  |  [POSTGRES][2022-07-26 14:58:03] 2022-07-26 14:58:03.956 UTC [227] LOG:  received smart shutdown requ                   est
baserow_1  |  [POSTGRES][2022-07-26 14:58:03] 2022-07-26 14:58:03.977 UTC [227] LOG:  background worker "logical r                   eplication launcher" (PID 511) exited with exit code 1
baserow_1  |  [POSTGRES][2022-07-26 14:58:04] 2022-07-26 14:58:03.980 UTC [506] LOG:  shutting down
baserow_1  |  [POSTGRES][2022-07-26 14:58:04] 2022-07-26 14:58:04.031 UTC [227] LOG:  database system is shut down                   
baserow_1  | 2022-07-26 14:58:04,037 INFO stopped: postgresql (exit status 0)
baserow_1  | 2022-07-26 14:58:04,037 INFO stopped: postgresql (exit status 0)
baserow_1  | 2022-07-26 14:58:04,038 INFO reaped unknown pid 306
baserow_1  | 2022-07-26 14:58:04,038 INFO reaped unknown pid 306
baserow_1  | 2022-07-26 14:58:04,040 INFO stopped: processes (terminated by SIGTERM)
baserow_1  | 2022-07-26 14:58:04,040 INFO stopped: processes (terminated by SIGTERM)
baserow_1  | 2022-07-26 14:58:04,040 ERRO pool processes event buffer overflowed, discarding event 1
baserow_1  | 2022-07-26 14:58:04,040 ERRO pool processes event buffer overflowed, discarding event 1
**baserow_1 exited with code 0**
6

Could you include all the logs? It seems to be cutoff, feel free to PM me directly if and/or anonymizing private info in them.

Currently I know that the single container self hosted Baserow takes about 600-800mb of memory to run unfortunately, so if there isn’t enough RAM available this might be one cause.

7

Thank you very much for your help. I will write to you in private messages.

8

How do I write to you in a private message?
I am attaching the server logs.
I looked in the control panel that the RAM is 2 GB of which 1.81 GB is used. Do I need to expand it?
sys log file