FunnyPocketBook

I'm running a very similar setup to yours, but the main thing I'm still missing is monitoring how much each container reads/write onto the filesystem. Did you figure out how to get that?

No, sadly not. I had been looking around more since I posted this but nothing has worked so far...

Is there a way to preclear a new disk on Windows (or any OS except for Unraid), such that I have a more or less seamless integration of the new disk when I add it to the array? My server is in a remote location and I will only have access to it for a few days.

Hello! I've noticed some I/O spikes on my SSD, and want to figure out which Docker container is causing that. While `docker stats` shows Block I/O, it's constantly at 0 for me, no matter where and what kind of data is written or read. I have also tried csysdig, which requires a kernel module, which isn't in the unraid kernel. Another tool that was looked at is bcc-tools, but that needs to be run bare-metal. My objective is to track down the I/O metrics for each disk for each container, but more specifically, I want to measure how much each container is reading from or writing to a particular drive, in this case, my SSD. Eventually, I want to store those metrics in InfluxDB to display the reads/writes in Grafana. I'm already using the telegraf docker plugin, but that doesn't report the block I/O. Appreciate any insight help you can offer!

Hi @BMCave Please use https://forums.unraid.net/topic/124146-support-smartphonelover-firefly-iii-data-importer/#comment-1132082 as my container is not supported anymore

Here is a setup of the data importer if you wanna add it yourself

Oh, sorry! I must have missed the part in which you said you are absolutely new to Unraid, I misbelieved that you already knew how to create your own templates.

I sadly don't have the capacity to support more importers, so I won't add them, sorry @sescheiThe Nordigen importer has been moved to the general Firefly III Data Importer (FIDI) An example setup of how you can add the template yourself looks like this

v2 is under heavy development and has quite a few features missing. V1 is "not supported" as in no changes are happening there anymore but IMO it's still the version to use if you don't want to bother with bugs and missing features

Hey! I'm on vacation until the 20th, will have a look at that after I'm back. Sorry for that, guys!

@mattie112 I saw the changes but I'm on vacation/without a computer until tomorrow, so I couldn't update the template yet. Will do as soon as I come back though!

The data loss here is actually my fault, nothing you could have done if you aren't always reading the release changes of Firefly. I misread the changelogs for an update back in... October? I think and didn't adjust the container paths accordingly in the template

Did you change the container path for UPLOAD_PATH to /var/www/html/storage/upload and after restarting upload the files? You have to do that, otherwise the files won't be stored in /mnt/user/appdata/firefly-iii/upload/

Hey @Camilo It sounds like you had a < 5.4.0 version installed before you updated to the new version. The container path for newer versions for UPLOAD_PATH is `/var/www/html/storage/upload` instead of `/var/www/firefly-iii/storage/upload`. Updating to a newer version without updating the path may result in a data loss. You should check your host path `/mnt/user/appdata/firefly-iii/upload/` if the old attachments are still there. If they are, make a backup of them and then update the UPLOAD_PATH to `/var/www/html/storage/upload`. This should preserve your previously uploaded attachments. If not, then I'm terribly sorry, but your attachments might be lost for good

V1 isn't supported anymore, which is why I set the default layout to V2.

@40foot Can you check the container logs and the browser console for any errors? Also, did you already try readding the docker image?

Did you also make sure that the user firefly has the needed privileges for the database?

Did you create the firefly user and set a password?

Change the repository to jc5x/firefly-iii:beta instead of jc5x/firefly-iii

Pretty much! If you have attachments, make sure to also save the APP_KEY environment variable.

Have you followed this step already? Also, meinnamehier reported that the same issue got fixed after an array restart or a reboot.

Thanks for reporting that!

It appears that the Firefly-III CSV Importer saves the URI somewhere internally and doesn't look at the environment variable anymore once it's set. When I changed the URI to something invalid, it still pointed to the old, correct URI. In the CSV Importer WebUI, have you already clicked "Reauthenticate"? Clicking that fixed the issue for me.

Hm, I have only ever experienced this behaviour when I had duplicate containers that were using different templates. Go to the console of the CSV importer and execute printenv, that shows you the environment variables of the container. Does the variable FIREFLY_III_ACCESS_TOKEN show up? Is the FIREFLY_III_URI correct?

@meinnamehier I assume Firefly doesn't run on port 8080? What did you set FIREFLY_III_URI to, can you send a screenshot of your config? It could also be that you have tried to install the CSV Importer multiple times and are now stuck with multiple templates. Check if /boot/config/plugins/dockerMan/templates-user lists more than one CSV Importer and if so, you can remove the template that you don't want.