Paperless-ngx Update
Today I did an update of my paperless-ngx installation. Unplanned. 😅
I logged into my Synology DSM and saw that there was an update for the Redis image. Like always, I started the update and went on. Later that Day, I wanted to upload some files, but I got an 500: Error. I've searched the web and found that there could be an error with Redis.
First, I thought that this could be an issue with file permissions. Because I tried, for the first time, uploading an PDF via the share button on my Phone. But then it also failed while uploading a normal image of a Document. So I started my investigation.
First, I found this error message in the Redis logs: WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition.. Did a small search and found some shell command for sysctl which didn't help. Because in this Redis image, there is no sysctl installed.
This was one of the commands:
sudo sysctl -w vm.overcommit_memory=1
If set to 1, it is enabled. Mine was set to 0. Without sysctl installed, it looked that there was no way to set it. So I searched again. With no luck.
Then I thought maybe I could just restart the Redis container, but this also leaded into nothing.
So maybe I just could re-use the instructions (Link to a German Synology Forum), I've used to install paperless-ngx.
There were 4 commands I simply run again.
cd /volume1/docker/paperlessngx/config
sudo docker-compose pull
sudo docker-compose run --rm webserver createsuperuser
sudo docker-compose up -d
This helped. In some way. The downside was, that it reinstalled everything and also deleted the database. Luckily, I could restore all my files from the File system. The only thing I needed to add again were tags. For the next time, I should make a real backup with the document_exporter from paperless-ngx. (Second time I need to do this. https://bruegge.dev/paperless-ngx, maybe I should not postpone it for too long. 😅)
In the End, I have no solution to the initial problem. Just solved it accidentally by updating my installation and lost my database.
This post is also more or less a documentation for future-me, if I come to this point again. 👍
7/100 of #100DaysToOffload