![docker fsync failed docker write docker fsync failed docker write](https://miro.medium.com/max/1034/1*DT7wzPplzx5p-AmLYrEVmA.png)
Trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log trilium-.log
![docker fsync failed docker write docker fsync failed docker write](https://images.manning.com/360/480/resize/book/6/bf788ca-9b2a-463e-ba15-9cb7009131cc/Stoneman_Docker_hires.png)
Logs from my upgraded Trilium 0.47.7 client below: I should also mention that I use 2 computers times 2 OSes (Windows 10 and Ubuntu 20.04LTS) = 4 Trilium Clients.
Docker fsync failed docker write upgrade#
This happens with the old (now gone) server, the new server, and the clients running Trilium version 0.47.5 and the issue persists if I upgrade one of my clients to the most recent Trilium version (0.47.7) and try to sync it with a new v0.47.7 server. Sync failed: Request to POST failed, error: 401 Unauthorized Only thing was that Raspberry Pi OS started to crash every 1-2 days and not write logs to the SD card anymore, which is why I decided to simply reinstall the OS (without taking a backup, of course ?♀️️) and set up a new Trilium Notes server using the exact same Docker Image as before.ĭuring the setup process of the new Trilium Notes Server, I get prompted to configure one of my Trilium clients to initiate synchronization, but when I do so the client responds with the following message and does not synchronize: The only thing I did differently was that I used the unofficial ARM Docker Image from jcoin because hlince had apparently stopped releasing ARM builds for Trilium, and everything worked quite nicely regarding Trilium. About a month ago I bought a Raspberry Pi 4B and set up a private Trilium Notes server according to your tutorial using Docker.