Nextcloud Error : redis problem

[Benoit]

Hello, after a disk full situation, one of my Nextcloud apps no longer starts. I’ve identified two issues: first, the config.php file was corrupted, so I replaced it with a good version from a backup. Secondly, the dump.rdb file is 0KB, and Redis won’t start for this particular app. All the other apps are running fine. There are currently 20 GB free on the disk. How can we get a Nextcloud instance running again if Redis has stopped working? What steps can we take, other than reinstalling everything? I should note that I’ve already tried recovery mode, as well as restarting Cloudron and the server, etc.

Thanks for your help!

[joseph]

@Benoit can you just delete the empty redis file ? And maybe temporarily disable redis - https://docs.cloudron.io/apps/#redis ?

[Benoit]

Hello @joseph , I'd like to clarify that I'm running Ubuntu 20.04 with Cloudron 8.2.4. I don't have the option to disable Redis from the 'Services' menu link on the app. Only Turn.

[joseph]

@Benoit nextcloud doesn't have optional redis it seems. So, you can take the redis.rdb from your latest backup (just like you did for config.php) and put it there . this will make the restore logic reimport redis properly.

[joseph]

To be clearer: you would put the dump.rdb in /home/yellowtent/appsdata/<appid>/ directory with filename dump.rdb . It will look like:

root@my /home/yellowtent/appsdata/30c49bfe-8adf-4644-a030-fd95f00f5632 # ls
config.json  data  dump.rdb  postgresqldump

@Benoit sorry, maybe you are not trying to restore at all. just trying to recover a running app already? if that's the case, copy the redis.rdb to /home/yellowtent/platformdata/redis/appid/dump.rdb instead . Then, just toggle the recovery mode

[Benoit]

@joseph The app was working fine until the disk got full. I haven't attempted any restore yet. I only replaced the correct config.php, and all of the app’s files are still there. I do have a dump.rdb file in /home/yellowtent/appsdata/<app_id> that seems corrupted (0 bytes). The one in /home/yellowtent/platformdata/redis/<app_id> is over 30MB, but I'm not sure if it's the same file. I have a backup of the /home/yellowtent/appsdata/<app_id> version from Minio.

[joseph]

@Benoit yes, you can just copy over that 30MB file. The redis is only used for caching, so it's fine if it loses some data.

[Benoit]

@joseph i tried to copy the dump.rdb file from /home/yellowtent/platformdata/redis/<app_id> in /home/yellowtent/appsdata/<app_id> (app was stopped) and it doesn't work... I tried to put the app in recovery mode but it fails too with many message like this : box:services Attempt 6 failed. Will retry: Error waiting for redis-<ID>. Status code: 200 message: process not running

[joseph]

@Benoit I have fixed it up now. I simply deleted the redis dump and restarted redis from Services vivew.

[Benoit]

Thank you, @joseph ! Great! But how were you able to restart Redis? When I tried, I could only put it in recovery mode. I had renamed the file from dump.rdb to dump.rdb.corrupt and then tried restarting Redis, but it didn’t work. I must have missed a step. Thanks again!"

[joseph]

@Benoit don't think I did anything else! redis always starts afresh if the dump file is missing . I just removed the dump file and restarted redis. But next time, I will pay more attention and put this in our docs.