New baserow installation (self-hosted) - not successful

marcus · January 31, 2024, 4:08pm

Hi @bram ,
I am just trying to install another baserow instance - on my second NAS device (in docker installation via docker-composer).

This time I used a different method and settings, described here:

But unfortunately baserow container has some troubles to start successfully (redis and db look to be OK, but cannot check).

here is a log excerpt:

2024-01-31 16:06:27,801 INFO spawned: 'processes' with pid 1852
2024-01-31 16:06:27,801 INFO spawned: 'processes' with pid 1852
 [CELERY_WORKER][2024-01-31 16:06:28]   
 [CELERY_WORKER][2024-01-31 16:06:28] [2024-01-31 16:06:28,151: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@baserow-redis:6379/0: Error -2 connecting to baserow-redis:6379. Name or service not known..  
 [CELERY_WORKER][2024-01-31 16:06:28] Trying again in 32.00 seconds... (16/100)  
2024-01-31 16:06:29,153 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:29,153 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:29,156 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:29,156 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:29,156 ERRO pool processes event buffer overflowed, discarding event 341
2024-01-31 16:06:29,156 ERRO pool processes event buffer overflowed, discarding event 341
2024-01-31 16:06:29,158 INFO spawned: 'processes' with pid 1854
2024-01-31 16:06:29,158 INFO spawned: 'processes' with pid 1854
2024-01-31 16:06:30,170 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:30,170 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:30,174 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:30,174 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:30,174 ERRO pool processes event buffer overflowed, discarding event 342
2024-01-31 16:06:30,174 ERRO pool processes event buffer overflowed, discarding event 342
2024-01-31 16:06:30,176 INFO spawned: 'processes' with pid 1856
2024-01-31 16:06:30,176 INFO spawned: 'processes' with pid 1856
 [WEBFRONTEND][2024-01-31 16:06:31] ℹ Listening on: http://localhost:3000/  
 [WEBFRONTEND][2024-01-31 16:06:31]   
 [WEBFRONTEND][2024-01-31 16:06:31]  ERROR  connect ECONNREFUSED 127.0.0.1:8000  
 [WEBFRONTEND][2024-01-31 16:06:31]   
 [WEBFRONTEND][2024-01-31 16:06:31]   at module.exports.AxiosError.from (node_modules/axios/lib/core/AxiosError.js:80:0)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at RedirectableRequest.handleRequestError (node_modules/axios/lib/adapters/http.js:606:0)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at RedirectableRequest.emit (node:events:517:28)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at RedirectableRequest.emit (node:domain:489:12)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at eventHandlers.<computed> (node_modules/follow-redirects/index.js:14:24)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at ClientRequest.emit (node:events:517:28)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at ClientRequest.emit (node:domain:489:12)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at Socket.socketErrorListener (node:_http_client:501:9)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at Socket.emit (node:events:517:28)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at Socket.emit (node:domain:489:12)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at emitErrorNT (node:internal/streams/destroy:151:8)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at emitErrorCloseNT (node:internal/streams/destroy:116:3)  
 [WEBFRONTEND][2024-01-31 16:06:31]   at process.processTicksAndRejections (node:internal/process/task_queues:82:21)  
2024-01-31 16:06:32,112 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:32,112 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:32,116 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:32,116 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:32,116 ERRO pool processes event buffer overflowed, discarding event 343
2024-01-31 16:06:32,116 ERRO pool processes event buffer overflowed, discarding event 343
2024-01-31 16:06:32,119 INFO spawned: 'processes' with pid 1860
2024-01-31 16:06:32,119 INFO spawned: 'processes' with pid 1860
 [BASEROW-WATCHER][2024-01-31 16:06:32] Waiting for Baserow to become available, this might take 30+ seconds...  
2024-01-31 16:06:33,330 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:33,330 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:33,333 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:33,333 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:33,333 ERRO pool processes event buffer overflowed, discarding event 344
2024-01-31 16:06:33,333 ERRO pool processes event buffer overflowed, discarding event 344
2024-01-31 16:06:34,337 INFO spawned: 'processes' with pid 1865
2024-01-31 16:06:34,337 INFO spawned: 'processes' with pid 1865
2024-01-31 16:06:35,350 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:35,350 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:35,354 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:35,354 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:35,354 ERRO pool processes event buffer overflowed, discarding event 345
2024-01-31 16:06:35,354 ERRO pool processes event buffer overflowed, discarding event 345
2024-01-31 16:06:36,357 INFO spawned: 'processes' with pid 1867
2024-01-31 16:06:36,357 INFO spawned: 'processes' with pid 1867
2024-01-31 16:06:37,370 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:37,370 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:37,374 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:37,374 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:37,374 ERRO pool processes event buffer overflowed, discarding event 346
2024-01-31 16:06:37,374 ERRO pool processes event buffer overflowed, discarding event 346
2024-01-31 16:06:37,376 INFO spawned: 'processes' with pid 1869
2024-01-31 16:06:37,376 INFO spawned: 'processes' with pid 1869
2024-01-31 16:06:38,389 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-01-31 16:06:38,389 INFO success: processes entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Baserow was stopped or one of it's services crashed, see the logs above for more details. 
cat: supervisord.pid: No such file or directory
/baserow/supervisor/stop-supervisor.sh: line 11: kill: `': not a pid or valid job spec
2024-01-31 16:06:38,393 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:38,393 INFO exited: processes (exit status 1; not expected)
2024-01-31 16:06:38,393 ERRO pool processes event buffer overflowed, discarding event 347
2024-01-31 16:06:38,393 ERRO pool processes event buffer overflowed, discarding event 347
2024-01-31 16:06:39,397 INFO spawned: 'processes' with pid 1871
2024-01-31 16:06:39,397 INFO spawned: 'processes' with pid 1871

bram · January 31, 2024, 7:24pm

Hi @marcus, is looks like Baserow can’t reach your Redis server. Take a look at this line for your logs: [CELERY_WORKER][2024-01-31 16:06:28] [2024-01-31 16:06:28,151: ERROR/MainProcess] consumer: Cannot connect to redis://default:**@baserow-redis:6379/0: Error -2 connecting to baserow-redis:6379. Name or service not known.. .

marcus · January 31, 2024, 7:43pm

Any hint, how to fix it?
Or better, if you go through that docker-compose (from Mariushosting page) - what should be changed to get the whole thing install and work properly?

bram · February 1, 2024, 12:49pm

It can honest be many things at this point. I don’t know if you’ve followed all the steps correctly in the tutorial. Can you, for example, verify that the baserow-redis container is working as expected?

marcus · February 1, 2024, 1:36pm

baserow-redis is running and healthy (says my portainer)
But I started it again, here is a log:

9:C 01 Feb 2024 14:11:52.741 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
9:C 01 Feb 2024 14:11:52.741 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9:C 01 Feb 2024 14:11:52.741 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=9, just started
9:C 01 Feb 2024 14:11:52.741 * Configuration loaded
9:M 01 Feb 2024 14:11:52.741 * monotonic clock: POSIX clock_gettime
9:M 01 Feb 2024 14:11:52.742 * Running mode=standalone, port=6379.
9:M 01 Feb 2024 14:11:52.742 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
9:M 01 Feb 2024 14:11:52.743 * Server initialized
9:M 01 Feb 2024 14:11:52.743 * Ready to accept connections tcp

There are two warnings - one for memory overcommit and one for the TCP backLog setting of 511.
For the first one:
should I add that one mentioned parameter to the /etc/sysctl.conf ? Is it safe for my NAS device to do this change? Not sure so I am rather asking.

my sysctl.conf contains this:
kernel.panic = 3
net.core.somaxconn = 65535
net.ipv4.tcp_tw_reuse = 1

The other one:
I checked my /proc/sys/net/core/somaxconn file and it’s empy, No records or parameters there. So what to do with this one?

Frankly, I’m not docker expert. But at least I am able and willing to learn new things
So I will be thankful for any help with it.

bram · February 1, 2024, 7:57pm

That doesn’t seem to be the problem. You would need to share all your environment variables, docker configuration and output logs we can help you.