Cloudron Forum

We followed the official Cloudron tutorial for moving data to an external volume:
https://docs.cloudron.io/storage/

During the migration process, we faced several issues:

Issue #1: Docker Restart Loop

We attempted to migrate /home/yellowtent/platformdata/logs, but the migration failed because Docker was still using this directory even after stopping the Docker service. Docker automatically restarted itself, preventing the move. To resolve this, we ran the following command:

systemctl mask docker

This allowed us to stop Docker and proceed with the migration.

We attached an ext4 volume from Hetzner to the server, and there is sufficient space on the volume for Cloudron data.

Issue #2: Services Fail to Start After Migration

After completing the migration we restarted services:
box, docker (unmask docker), nginx, collectd

But most services failed to start in "Services" tab in Cloudron. For example graphite, postgresql, unbound, etc. And we can't restart them due to error.

The error message from Cloudron (when we want to start service) is as follows:

(HTTP code 500) server error - Cannot restart container mysql: failed to create task for container: failed to initialize logging driver: dial unix /home/yellowtent/platformdata/logs/syslog.sock: connect: connection refused

Troubleshooting Steps

1. We verified that /mnt/tc-cloudron-volume-1/platformdata/logs/syslog.sock is being created with the root:root ownership and permissions:

srw-rw-rw- 1 root root 0 ...

2. We updated /etc/rsyslog.conf to include the following lines:

module( load="imuxsock" SysSock.Name="/mnt/tc-cloudron-volume-1/platformdata/logs/syslog.sock" SysSock.Owner="yellowtent" SysSock.Group="yellowtent" SysSock.Perm="0666" )

Despite restarting rsyslog and Docker multiple times, the issue persists.

3. We also manually removed the syslog.sock file, restarted rsyslog, and confirmed that it recreates the file. However, it still reverts to root:root ownership.

Current State

• The syslog.sock file is being created with root:root ownership, which prevents Docker containers (e.g., MySQL, PostgreSQL) from initializing correctly.
• Even after applying the correct ownership and permissions manually (chown yellowtent:yellowtent and chmod 0666), the services fail to start.
• We suspect this might be due to a deeper integration issue between rsyslog, Docker, and Cloudron's specific logging requirements.

Environment Details

• Cloudron version: v8.2.3
• OS: Ubuntu 22.04.1 LTS
• Rsyslog version: 8.2.3
• Hosting provider: Hetzner
• Attached volume: ext4 formatted with sufficient space

Request for Assistance

We kindly request guidance on how to resolve the syslog.sock ownership issue and ensure proper integration of logging between Docker and Cloudron after migration to an external volume.

Thank you in advance for your help!

Hi @joseph,

No, I haven’t tried running
systemctl restart cloudron-syslog

Do you think this could help resolve the issue?

I followed the official Cloudron documentation for migrating the default data directory: https://docs.cloudron.io/storage/. However, the documentation doesn’t mention restarting cloudron-syslog as part of the process.

To try this command, I’ll need to wait until my scheduled maintenance window at night to work on the server. If you have any other suggestions, please let me know so I can try everything during my maintenance period.

Thank you for your assistance!

@joseph , got it!
thanks. will do and let you know about result