bubiman

I spend an other 2 hours ... and got it working. To "fix" that bug I had to change Rails Environment (it is under More Settings) to development .... and got a few other errors after that.

Hi, after spending way to long to get the DB Connection for dawarich to work, I am now running into an error I can not fix. After starting the dawarich docker the log shows the following: bottom of the log: OIDC: Not configured (missing OIDC_CLIENT_ID or OIDC_CLIENT_SECRET) top of the log: ArgumentError: Missing secret_key_base for 'production' environment, set this string with bin/rails credentials:edit (ArgumentError) raise ArgumentError, "Missing secret_key_base for '#{Rails.env}' environment, set this string with bin/rails credentials:edit" I have tried to google myself out of this but had no luck for 2h so far. I added an extra variable to the docker config named secret_key_base based on this https://github.com/truenas/apps/pull/4705 but I have absolutely no idea what value I have to fill in. I tried leaving it empty, I tried <%= ENV["SECRET_KEY_BASE"] %> based of this site https://stackoverflow.com/questions/23180650/how-to-solve-error-missing-secret-key-base-for-production-environment-rai but nothing is working. Can anyone help me with this?

After ignoring the version 7 for quite some time now, I now want to upgrade my Server. I bought an "Unraid OS Plus" license a few years ago. 1) Do I have to buy a new license to use Unraid 7? I do not need more than 12 drives. I tried to read the upgrading instructions, but all I get is a 404 error: 2) Where can I find a How-To-Uprade guide? I realy realy do not want to break my system Thanks for your help

Out of nowhere my paperless would not start anymore. I hope this saves someone some time troubleshooting the problem. I got the following errors in the log: Traceback (most recent call last): File "/usr/src/paperless/src/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.12/site-packages/django/core/management/__init__.py", line 382, in execute settings.INSTALLED_APPS File "/usr/local/lib/python3.12/site-packages/django/conf/__init__.py", line 81, in __getattr__ self._setup(name) File "/usr/local/lib/python3.12/site-packages/django/conf/__init__.py", line 68, in _setup self._wrapped = Settings(settings_module) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/django/conf/__init__.py", line 201, in __init__ raise ValueError("Incorrect timezone setting: %s" % self.TIME_ZONE) ValueError: Incorrect timezone setting: CET s6-rc: warning: unable to start service init-migrations: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. Traceback (most recent call last): File "/usr/src/paperless/src/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.12/site-packages/django/core/management/__init__.py", line 382, in execute settings.INSTALLED_APPS File "/usr/local/lib/python3.12/site-packages/django/conf/__init__.py", line 81, in __getattr__ self._setup(name) File "/usr/local/lib/python3.12/site-packages/django/conf/__init__.py", line 68, in _setup self._wrapped = Settings(settings_module) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/django/conf/__init__.py", line 201, in __init__ raise ValueError("Incorrect timezone setting: %s" % self.TIME_ZONE) ValueError: Incorrect timezone setting: CETIt took my quite some time to find out what was wrong: I had to change PAPERLESS_TIME_ZONE to Europe/Berlin. I don`t know why CET is no longer working for me. You can find the time zones names here https://en.wikipedia.org/wiki/List_of_tz_database_time_zones I also changed PAPERLESS_FILENAME_FORMAT to {{ created }}-{{ correspondent }}-{{ title }} technically this was just a warning and no error but the new format requires {{ instead of {

Well, I am just stupid. I don`t know why, I don`t know when but disk4 was not included in the "Global Share Settings" under "Included Disks"

I have deleted the Mover Tuning Plugin (ca.mover.tuning.plg) because some mentioned problems with version 7 of unraid (yes I know I am still on 6). Mover is still not moving the files to the still empty disk4

Hi, I do not understand why the mover is not moving some files. I got some big files on my cache pool: When I start the mover, I can see it trying to move the files to disk3 but disk3 does not have enough free-space left to actually move the file there The share in question is set to Cache->Array The share is configured to use all disks and no disk is excluded What I do not get: Why is the Mover not using disk4? That drive is practically empty. What have I done wrong? Thanks for your help

I don`t get this docker working. I even can not open the log window to see what is going on because the windows is closed instantly after opening it.

I set up my mariadb container years ago to use it for my iobroker and it is working without any problems. Today a want to try out nextcloud and to use nextcloud I want to add a database in mariadb but I am unable to login with adminer: I change the MYSQL_ROOT_PASSWORD variable to "root" to be sure to use the right password but it is still not working. I tried to login in via console but that is not working either: Is there a way to regain access to my mariadb? I dont what to lose years of collected iobroker data

Ah now I understand. Thanks for your help. I have to check what the script is doing. I don`t want to be the guy hitting ALT-F4 because someone said so So removing a drive is no core function, I have to rely on a script an user wrote ... but that script is not working in 6.12.13. And now stopping an array is no core function, I have to reley on a script an other user wrote. What is Lime Technology doing?

I am sorry for my bad english. Thats why I wrote I fave to follow the "Remove Drives Then Rebuild Parity" methode but I can not remove the drive if unraid will not unmount it

What script do you mean? I just want to stop the array to remove the broken HDD

No nothing is open. I think Disk4 is damaged beyond using at all. The listed size is 16.8GB of a 3TB HDD:

One of the drives is broken and I want to remove it. I stopped the array to follow the "The "Remove Drives Then Rebuild Parity" Method" https://docs.unraid.net/legacy/FAQ/shrink-array/#the-remove-drives-then-rebuild-parity-method instructions (because the "The "Clear Drive Then Remove Drive" Method is not working at the moment) ... but unraid is trying to stop the array for 19min now: What should I do now? Disk4 is the broken one. How do I stop the array to remove the drive and rebuild parity?

Sorry but removing a drive safely from an array should be a core function. I should not have to follow some 7 years old instructions that someone wrote with the potential to ruin a drive I did not meant to delete because I screwed up 3 "Identify which disk you're removing" How do I know that these instructions are still valid in 6.12.13? The official (?) FAQ said I should use the "clear array drive" script (again something someone wrote) and that did not work