The Postgres service is not started (Update 8.3.x)
-
One of my Cloudron instances is having problems with the update.
Postgres cannot be started.Endless loops of
Mar 28 10:54:58 ==> Initializing database Mar 28 10:54:58 sudo: /etc/sudo.conf is owned by uid 1001, should be 0 Mar 28 10:54:58 sudo: /etc/sudo.conf is owned by uid 1001, should be 0 Mar 28 10:54:58 sudo: /etc/sudoers is owned by uid 1001, should be 0 Mar 28 10:54:58 sudo: error initializing audit plugin sudoers_audit Mar 28 10:55:50 ==> Creating new installation Mar 28 10:55:50 ==> Initializing database
Is there a quick solution to this problem?
-
Hm this sounds quite wrong.
/etc/sudo.conf
is part of the actual image and should be owned by root (0). It is further readonly.Possibly that docker image on your disk is corrupt?
You can recreate the docker setup with
cloudron-support --recreate-docker
over SSH -
wohoo.
cloudron-support --recreate-docker
solved the problem. -
L luckow has marked this topic as solved
-
Today I maybe had the same problem with the VPN app.
cloudron-support --recreate-docker
maybe solved the problem. I am currently working onError: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003
.
Any idea how to solve this (should be owned by root (0)) problem permanently?Apr 18 14:32:40 An updated CRL has been created: Apr 18 14:32:40 * /app/data/pki/crl.pem Apr 18 14:32:40 2025-04-18T12:32:40Z Apr 18 14:32:40 gen-crl (stdout): Apr 18 14:32:40 2025-04-18T12:32:40Z Apr 18 14:32:41 ==> Server has IPv6 connectivity, setting as default route Apr 18 14:32:41 sudo: /etc/sudo.conf is owned by uid 1001, should be 0 Apr 18 14:32:41 sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set Apr 18 14:32:41 file:///app/code/src/vpn.js:193 Apr 18 14:32:41 if (safe.error) throw new Error(`Could not restart OpenVPN: ${safe.error.message}`); Apr 18 14:32:41 ^ Apr 18 14:32:41 2025-04-18T12:32:41Z Apr 18 14:32:41 Error: Could not restart OpenVPN: Command failed: sudo /app/code/src/restart.sh Apr 18 14:32:41 at ovSyncSettings (file:///app/code/src/vpn.js:193:31) Apr 18 14:32:41 at async ovInit (file:///app/code/src/vpn.js:689:5) Apr 18 14:32:41 at async Object.init (file:///app/code/src/vpn.js:735:5) Apr 18 14:32:41 at async main (file:///app/code/server.js:173:5) Apr 18 14:32:41 2025-04-18T12:32:41Z Apr 18 14:32:41 Node.js v22.14.0 Apr 18 14:32:41 2025-04-18 12:32:41,213 WARN exited: admin (exit status 1; not expected) Apr 18 14:32:42 2025-04-18 12:32:42,220 INFO spawned: 'admin' with pid 5733 Apr 18 14:32:43 2025-04-18 12:32:43,222 INFO success: admin entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
-
to give some context:
- I followed https://docs.cloudron.io/storage/#docker-images to free disk space
cloudron-support --troubleshoot
ended up with[FAIL] box service keeps restarting, please investigate the error by inspecting /home/yellowtent/platformdata/logs/box.log
- Log shows `Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003.
docker network list
shows no Cloudron network
Maybe it's not a good idea to relocate the docker files or something changed in ubuntu or Cloudron platform versions.
-
no time for further investigation (and understanding), but
- this is a diff of a working Cloudron with Docker images on the same disk
--userland-proxy=false
- that I added to the custom conf on the instance with Docker on another disk
After
cloudron-support --recreate-dockery
everything works as expected. Maybe an outdated documentation? - this is a diff of a working Cloudron with Docker images on the same disk
-
Seems like a few issues intermixed here. For a start userland proxy in docker should be false. This set however in
/etc/systemd/system/docker.service.d/cloudron.conf
by the cloudron startup script.On port 172.18.0.1:3003 the Cloudron docker proxy addon would listen, so this also hints at docker having an issue with the network bridge it supposed to have created.
Otherwise most likely if you had a disk being 100% full situation, all bets are off, unfortunately. This is not so much related to Cloudron code but other linux services we use like mysql and docker