Network errors after recent upgrade

[dacook]

After a recent upgrade, our cloudron server has stopped working.

The web interface says:

Cloudron is offline. Reconnecting...

When accessing an app, it says:

This app is currently not responding. Please try refreshing the page in a few minutes.

On the server, we can see the following errors in the log (/home/yellowtent/platformdata/logs/box.log)

2023-12-15T05:56:08.152Z box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
2023-12-15T05:56:08.175Z box:shell reload (stderr): sudo: unable to resolve host my: No address associated with hostname
...
2023-12-15T05:56:08.306Z box:dockerproxy startDockerProxy: started proxy on port 3003
Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003
    at Server.setupListenHandle [as _listen2] (node:net:1446:21)
    at listenInCluster (node:net:1511:12)
    at doListen (node:net:1660:7)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)

Also:

root@my:~# systemctl status box
● box.service - Cloudron Admin
     Loaded: loaded (/etc/systemd/system/box.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2023-12-15 06:11:50 UTC; 1s ago
   Main PID: 4035 (node)
      Tasks: 11 (limit: 4595)
     Memory: 82.4M (max: 400.0M)
     CGroup: /system.slice/box.service
             └─4035 node /home/yellowtent/box/box.js

Dec 15 06:11:50 my systemd[1]: Started Cloudron Admin.
Dec 15 06:11:52 my sudo[4048]: yellowtent : unable to resolve host my
Dec 15 06:11:52 my sudo[4048]: pam_unix(sudo:session): session opened for user root by (uid=0)

But am not sure how to fix it. Have tried a manual reboot of the server to no avail.

We would like to restore the service ASAP, can anybody please help?

[girish]

@dacook said in Network errors after recent upgrade:

2023-12-15T05:56:08.306Z box:dockerproxy startDockerProxy: started proxy on port 3003
Error: listen EADDRNOTAVAIL: address not available 172.18.0.1:3003

This implies that docker is not running. Can you please check systemctl status docker ? If docker is running, can you check docker network list ? There should a cloudron network inside it which is 172.18.0.0 .

[dacook]

Thanks @girish, I just checked and it is running (actually it was started a few minutes ago).

root@my:~# docker network list --no-trunc
NETWORK ID                                                         NAME       DRIVER    SCOPE
692b3c8958ff826cbe7d3bdf484623bb848513ab646afb2b0e04c934b48bdaba   bridge     bridge    local
6414da3a67553c48815fa1f6b31586cd5ae5ed19a179dfd47dfd73cbc0ec5f64   cloudron   bridge    local
a9771b5303a07fd1a5da4e2d2c4b9b728f10ca58d9a47e9b2c859d5430106919   host       host      local
feb8faa4aa8e87bd985f788884be2a1f4b000a6093e0464e1ea0b9aff81c2f91   none       null      local

Indeed, everything is running as normal. I don't suppose I can thank you for fixing it?

[girish]

@dacook no worries The core issue is that there were some defaults in /etc/defaults/docker.json (related to limiting json logs). I wonder if these were put in my some new-relic software that seemed to be installed on the server. The options were conflicting with the other options in /etc/systemd/system/docker/cloudron.conf and docker was not starting as a result.

[dacook]

Thanks again, and for sharing the details!