Thilo-Alexander Ginkel

Understood. Logs are difficult to access as they are located in Grafana Loki, which is using seaweedfs as storage backend and its buckets also seem to be affected. I did...

I restored all nodes from backups and downgraded to 3.59. Unfortunately, filer is logging the following error since bringing the cluster back up on the old data: ``` I0201 21:00:46.485940...

Thanks for your speedy response! Regarding the last-known-good version: I remember that the cluster experienced the same issue during the last upgrade, which I could also remedy using a restart...

I tried building a reproducer based on the docker-compose from this repo (extended to three master nodes) and updated via watchtower, to match our pro setup as closely as possible....

A few hours ago, all SeaweedFS docker containers were updated in our cluster following the recent release. Unfortunately, the cluster did not come back up as the three master nodes...

Is there at least a way to detect the error situation and react by restarting the master process? In Prometheus I can see that all master nodes return `SeaweedFS_master_is_leader` =...

The Docker image build is somewhat proprietary due to the way I am building the image in GitLab CI to build a multiarch image (that also supports arm, which I...

I am deploying though Ansible, but with a very similar syntax to Docker Compose. ``` - name: deploy gigaset-elements-proxy container include_role: name: docker/container vars: docker: image: tgbyte/gigaset-elements-proxy name: gigaset-elements-proxy init:...

Raspberry Pi / Raspbian Regarding config: You need to have the `default.yaml` file mounted at `/config/default.yaml`. Just another thought: IIRC the Gigaset Elements API is picky about special characters in...

> I thought docker images run on any plattform. Isn‘t that correct? Nope. `tgbyte/gigaset-elements-proxy` is a so-called multiarch image that supports amd64 and armv7, though.