Kimai won't install, says: Error: connect ECONNREFUSED 172.18.18.234:8000
-
From the logs:
Apr 08 10:14:05 [OK] Already at the latest version ("DoctrineMigrations\Version20240926111739") Apr 08 10:14:05 Database `be52dca4b193b615` for connection named default already exists. Skipped. Apr 08 10:14:05 // Clearing the cache for the prod environment with debug false Apr 08 10:14:05 => Create cloudron.yaml Apr 08 10:14:05 => Ensure directories Apr 08 10:14:05 => Ensure permissions Apr 08 10:14:05 => Run installer Apr 08 10:14:05 Creating database ... Apr 08 10:14:05 Rebuilding cache ... Apr 08 10:14:05 Start installation ... Apr 08 10:14:05 chown: warning: '.' should be ':': 'www-data.www-data' Apr 08 10:14:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.18.234:8000 Apr 08 10:14:18 2025-04-08T03:14:18Z Apr 08 10:14:18 2025-04-08T03:14:18Z Apr 08 10:14:18 2025-04-08T03:14:18Z Apr 08 10:14:18 Apr 08 10:14:18 Apr 08 10:14:18 [OK] Cache for the "prod" environment (debug=false) was successfully cleared. Apr 08 10:14:18 // Warming up the cache for the prod environment with debug false Apr 08 10:14:18 /app/pkg/start.sh: line 41: 11 Killed sudo -u www-data bin/console kimai:install -n Apr 08 10:14:19 => Create cloudron.yaml Apr 08 10:14:19 => Ensure directories Apr 08 10:14:19 => Ensure permissions Apr 08 10:14:19 => Run installer Apr 08 10:14:19 chown: warning: '.' should be ':': 'www-data.www-data' Apr 08 10:14:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.18.234:8000 Apr 08 10:14:20 2025-04-08T03:14:20Z Apr 08 10:14:20 2025-04-08T03:14:20Z Apr 08 10:14:20 2025-04-08T03:14:20Z Apr 08 10:14:20 2025-04-08T03:14:20Z Apr 08 10:14:20 Apr 08 10:14:20 Apr 08 10:14:20 [OK] Already at the latest version ("DoctrineMigrations\Version20240926111739") Apr 08 10:14:20 Database `be52dca4b193b615` for connection named default already exists. Skipped. Apr 08 10:14:20 // Clearing the cache for the prod environment with debug false Apr 08 10:14:20 Creating database ... Apr 08 10:14:20 Rebuilding cache ... Apr 08 10:14:20 Start installation ... Apr 08 10:14:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.18.234:8000 Apr 08 10:14:32 2025-04-08T03:14:32Z Apr 08 10:14:32 2025-04-08T03:14:32Z Apr 08 10:14:32 2025-04-08T03:14:32Z Apr 08 10:14:32 Apr 08 10:14:32 Apr 08 10:14:32 [OK] Cache for the "prod" environment (debug=false) was successfully cleared. Apr 08 10:14:32 // Warming up the cache for the prod environment with debug false Apr 08 10:14:33 /app/pkg/start.sh: line 41: 11 Killed sudo -u www-data bin/console kimai:install -n Apr 08 10:14:34 2025-04-08T03:14:34Z Apr 08 10:14:34 2025-04-08T03:14:34Z Apr 08 10:14:34 2025-04-08T03:14:34Z Apr 08 10:14:34 2025-04-08T03:14:34Z Apr 08 10:14:34 Apr 08 10:14:34 Apr 08 10:14:34 [OK] Already at the latest version ("DoctrineMigrations\Version20240926111739") Apr 08 10:14:34 Database `be52dca4b193b615` for connection named default already exists. Skipped. Apr 08 10:14:34 // Clearing the cache for the prod environment with debug false Apr 08 10:14:34 => Create cloudron.yaml Apr 08 10:14:34 => Ensure directories Apr 08 10:14:34 => Ensure permissions Apr 08 10:14:34 => Run installer Apr 08 10:14:34 Creating database ... Apr 08 10:14:34 Rebuilding cache ... Apr 08 10:14:34 Start installation ... Apr 08 10:14:34 chown: warning: '.' should be ':': 'www-data.www-data' Apr 08 10:14:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.18.234:8000 Apr 08 10:14:49 2025-04-08T03:14:49Z Apr 08 10:14:49 2025-04-08T03:14:49Z Apr 08 10:14:49 2025-04-08T03:14:49Z -
Welp, once again, I post a problem that I end up solving, if I had only thought more. Somewhere I read that there might not be enough ram allotted. I checked and the default for this app is 256MB. So I upped it to 1GB, started it, and it finished installing (had to make an admin user), and is now running.
-
I don't always remember to do it, but as a general rule of thumb I tend to always double the so-called minimum RAM, as I find in practice it is very often too low.
-
Since we test all app packages with the default (minimum) memory specified, I wonder how this had solved it. Is it possible that the system itself is running low on memory?
@nebulon said in Kimai won't install, says: Error: connect ECONNREFUSED 172.18.18.234:8000:
system itself is running low on memory?
I've seen VPS setups where even RAM is a shared resource

Or even worse, no real RAM but SSD RAM like swap
Could also be the case

-
Well, the error logs don't contain anything that I recognize as memory related. I have one of those SSDNodes servers which people either love or disbelieve:
Platform Version v8.3.1 (Ubuntu 22.04.3 LTS)
Vendor Red Hat
Product KVM
CPU 12 Core "Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz"
Memory 50.51 GB RAM & 4.29 GB Swap
Uptime 5 daysI suppose it needed just that little extra ram past 256MB in order to use the db to make the admin user. Once I upped the ram this is what followed in the logs:
2025-04-08T07:44:57Z 2025-04-08T07:44:57Z 2025-04-08T07:44:57Z 2025-04-08T07:44:57Z 2025-04-08T07:44:57Z 2025-04-08T07:44:57Z 2025-04-08T07:44:57Z [30;42m [39;49m 2025-04-08T07:44:57Z [30;42m [39;49m 2025-04-08T07:44:57Z [30;42m [39;49m 2025-04-08T07:44:57Z [30;42m [39;49m 2025-04-08T07:44:57Z [30;42m [39;49m 2025-04-08T07:44:57Z [30;42m [39;49m 2025-04-08T07:44:57Z [30;42m [OK] Cache for the "prod" environment (debug=false) was successfully cleared. [39;49m 2025-04-08T07:44:57Z [30;42m [OK] Cache for the "prod" environment (debug=false) was successfully warmed. [39;49m 2025-04-08T07:44:57Z [30;42m [OK] Successfully installed Kimai version 2.32.0 🎉 [39;49m 2025-04-08T07:44:57Z [39;49m // [39;49mWarming up the cache for the [32mprod[39m environment with debug [32mfalse[39m 2025-04-08T07:44:57Z ==> Create admin account 2025-04-08T07:44:57Z => Ensure admin account 2025-04-08T07:44:57Z mysql: [Warning] Using a password on the command line interface can be insecure. 2025-04-08T07:44:59Z 2025-04-08T07:44:59Z 2025-04-08T07:44:59Z [30;42m [39;49m 2025-04-08T07:44:59Z [30;42m [39;49m 2025-04-08T07:44:59Z [30;42m [OK] Success! Created user: admin [39;49m 2025-04-08T07:44:59Z => Starting apache 2025-04-08T07:44:59Z => Tailing app logs 2025-04-08T07:44:59Z [Tue Apr 08 07:44:59.550824 2025] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.58 (Ubuntu) mod_perl/2.0.13 Perl/v5.38.2 configured -- resuming normal operations 2025-04-08T07:44:59Z [Tue Apr 08 07:44:59.550941 2025] [core:notice] [pid 1] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' 2025-04-08T07:44:59Z tail: cannot open '/run/kimai/log/prod.log' for reading: No such file or directory 2025-04-08T07:45:01Z - - - [08/Apr/2025:07:45:00 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:45:10Z - - - [08/Apr/2025:07:45:10 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:45:20Z - - - [08/Apr/2025:07:45:20 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:45:30Z - - - [08/Apr/2025:07:45:30 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:45:40Z - - - [08/Apr/2025:07:45:40 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:45:50Z - - - [08/Apr/2025:07:45:50 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:46:00Z - - - [08/Apr/2025:07:46:00 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:46:10Z - - - [08/Apr/2025:07:46:10 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:46:20Z - - - [08/Apr/2025:07:46:20 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:46:30Z - - - [08/Apr/2025:07:46:30 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:46:40Z - - - [08/Apr/2025:07:46:40 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla (CloudronHealth)" 2025-04-08T07:46:46Z 124.122.43.134 - - [08/Apr/2025:07:46:46 +0000] "GET / HTTP/1.1" 302 294 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36"Previously it would reach "clearing the cache", but then crash before "warming the cache". I don't know what any of that means, but upping the allocatted ram to 1GG from 256MB seemed to do the trick.

Looks like there was a CPU surge from Kimai:

Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login