[BUG] App crashes when i scan library about romm HOT 6 OPEN

How come you're not using the volumes romm_redis_data and romm_resources?

i found the compose file here in the repo & setup instructions, tweeked it to my needs. (save presistent data on my /DockerData and "read" the roms from my rom storage ...

did i set up anything wrong?

from romm.

Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

It's possible the folder /DockerData/RomManager/redis_data may not have the right perms for redis-in-romm to write to it. You'll want to check the perms on that folder, change them so the internal user has access.

from romm.

Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

It's possible the folder /DockerData/RomManager/redis_data may not have the right perms for redis-in-romm to write to it. You'll want to check the perms on that folder, change them so the internal user has access.

i leave docker to create the folders under /DockerData , this usualy assists not running into those premmision erros .

this is the premisions that the folders have :

drwxr-xr-x  2 root             root             4.0K Mar 26 22:29 assets
drwxr-xr-x  2 root             root             4.0K Mar 29 19:19 config
drwxr-xr-x  6 systemd-coredump systemd-coredump 4.0K Mar 26 22:30 mysql_data
drwxr-xr-x  2 root             root             4.0K Mar 26 22:29 redis_data
drwxr-xr-x  2 root             root             4.0K Mar 26 22:29 resources

from romm.

How come you're not using the volumes romm_redis_data and romm_resources?

In any case this like likely the permission bug we've seen on 3.0.3, and will be fixed in 3.1. You can wait a couple days or try chmod 777 on those folders.

from romm.

So you compose seems fine! There's a chance this will start working again when the 3.1 RC is released in a bit, report back here when it does and you've had a chance to try it.

from romm.

So you compose seems fine! There's a chance this will start working again when the 3.1 RC is released in a bit, report back here when it does and you've had a chance to try it.

I shall wait then !

from romm.