rdagitz

For anyone who wants to try Receipt Wrangler on Unraid, I could not get llamagpt or Serge to work with it. I am trying Google's Gemini instead.

This app does not have a support link that points to the Unraid forum. That is why I posted my question on general support. I was trying to find out if anyone has tried this on Unraid. It turns out that the settings that I have are enough to find Mariadb, as long as Receipt Wrangler is in the same virtual network as Mariadb. Once Receipt Wrangler is started one time, I had to use terminal and edit a config.prod.json file in the appdata/receipt-wrangler-api/config directory. I used the following link to get my settings for the json file (https://github.com/Receipt-Wrangler/.github/blob/main/configuration/configuration.md). One AI option for Receipt Wrangler is llamagpt. I am trying the Serge Unraid app but set the config.prod.json file as "llamagpt" so we will see how it goes. I am not getting any errors in the log so far. Sounds promising.

I am trying to set up the Receipt Wrangler app on my Unraid using Mariadb that is already part of my system. I have created a Mariadb/mysql user and password for Receipt Wrangler but I am trying to decipher the variables that I need to create in the Unraid Receipt Wrangler template. I have the following variables set: 3 Path Variables for Config, Data & Logs (each set to /mnt/user/appdata/receipt-wrangler-api/ ending in "config," "data," or "logs" respectively) I have also set the following Environmental Variables MYSQL_DATABASE=wrangler MYSQL_ROOT_PASSWORD={youthinkiwouldbecrazyenoughtopostthishere?} MYSQL_USER=wrangler MYSQL_PASSWORD={youthinkiwouldbecrazyenoughtopostthishere?} I cannot seem to figure out what variable(s) I need to set to tell it to use Mariadb, its port and its location in the system. The only reference that I have found for using Mariadb with Receipt Wrangler with Mariadb contained the following code in the post: docker run --name receipt-wrangler-db -e MYSQL_ROOT_PASSWORD=123456 -e MYSQL_USER=wrangler -e MYSQL_PASSWORD=123456 -e MYSQL_DATABASE=wrangler -p 9001:3306 -d library/mariadb Thoughts?

I am diving into this conversation. I noticed that TheBird956 is running Unraid 6.12.8. I have 7 Unraid servers that I manage. I recently upgraded 2 of them from 6.12.6 to 6.12.8 and now both of the upgraded servers are randomly shutting down. I have Virtual Syslog Server running on a Windows machine in the office of one of the upgraded Unraid servers to hopefully catch some log files of what is going on. I am posting something here so that others can add if they are experiencing similar issues.

Ran the check again without the -L Looks good to me. Thoughts?

I went ahead and ran the fix again. Stopped the array Started in Maintenance Mode Went to Disk 1 Settings > Check File System Removed the -n and put in -L and hit the Check button Below is the output of the Check

I did actually run is in the GUI. I just removed the "-n" and replaced it with "-L" while in Maintenance Mode and hit the "Check" button. Is there something incorrect in the command that I ran or should this have resolved the issue so that I wouldn't have to run it again just two weeks later?

Two weeks ago I ran the following: xfs_repair -L /dev/md1 This "repaired" the file system but I am back here again. Is this the command that you are suggesting that I run again?

Hello Helpful People, About two weeks ago I looked the the Main tab of the Unraid dashboard and found that Data Disk 1 had no supported file type and we could not write to that disk. The disk has been part of my array for years and had a majority of our data on it. I stopped the array and ran fsx_repair from Disk 1 Settings > File System Check and it repaired the partition. We were up and running. Now two weeks later I am getting some of the same warnings (although the file system is not preventing from writing to the disk at this point.) I don't see any Smart errors but does anyone know any tests or diagnostics I can run to determine if this is a hardware problem with this drive before I "jump down the rabbit hole" too far? Unraid 6.12.6 ciserver-smart-20240122-0853.zip ciserver-diagnostics-20240122-1149.zip

I had the same exact behavior as listed in the beginning of this thread. I was able to Stop the array Start the array in Maintenance mode click on the problem disk in the UI and then run the "Check File System" tool from the dashboard. I did have to use the "-L" argument to drop the log and proceed. Fixed the problem. Unraid truly is awesome.

Do I need to remove any previous entries in authorized_keys?

Persistent SSH is still a no go. I have created ed25519 keys for both servers (Unraid1 & UnraidBackup) Made sure the root users of each server have a copy of the key (I can see the key listed under the root user.) SSHed from Unraid1 to UnraidBackup by terminal and run the command Said "Yes" to add the SSH user to the authoized_users list I removed the entries in the go file that are no longer needed [see above] Each time UnraidBackup is rebooted I am confronted with Am I missing something?

I have a Supermicro X8DT3 with a BMC IPMI. I am running Unraid 6.12.6. Since installing the IPMI Tools plugin (new install from scratch), I keep getting constant "Critical Low" or "Critical High" warning until the log file is 100% full. I had to turn off notifications. I am running a fan wall (x3) of Noctua NF-P12 (with PWM) and 2 NF-R8 fans at the back of the case. My son and I have adjusted the IPMI Tools config file to the closest values the X8DT3 will take for the Noctua fans and yet Unraid log is still getting overwhelmed unless I turn off notifications. Thoughts? IPMI Tools Config below:

I am still not getting any syslog entries on Uraid2. I here is what I have done. Set Unraid1 "Remote syslog server" to the IP of Unraid2 with UDP 514 Set Unraid2 "Local syslog server" to Enable and set the Local syslog folder to a new share I created called "Logs". (Ignore the entry in the picture above.) This "Logs" share is set to use the cache drive only. I went ahead and port forwarded 514 in Unraid2's network just in case it is needed. Can anyone think of something I am missing?

So I have set the above settings on the two servers but when I look on Unraid2 I don't see anything. Am I doing something wrong?