Faspina

I have a CyberPower LX1500GU3 It reports 0 Load with my unraid plugged into it, and 7 min 30 for remaining batter , I know this is not correct here is my config , any thoughts [upsunraid] driver = usbhid-ups port = auto vendorid = "0764" productid = "0601" bus = "009"

how do you install the mosquito client tools (Mosquitto_pub/sub on unraid. I don't see it in nerd tools

I build this in the spring of 2020. A pandemic project I want to upgrade to get an AVX/AVX2 CPU, a GPU to play with AI, and continue to run my many home automation and applications in dockers. I don't do much media server/transcoding. Here is what I have now Case: Cool Master N400 - I want to keep this ATX case PSU: EVGA 650W - I want to keep this CPU (DUAL): |Intel Xeon X5670 - Replace Supermicro X8DTL-IF ATX DUAL - Replace 4x16GB DDR3 PC3-8500 ECC REG - Keep if possible I am seeing a lot of single CPU configurations on websites like serverbuild.net, but confused as why I would switch from dual to single config. I am running unraid with 4x2GB Array drive, 1x2gb Parity drive , 1X1GB SSD for cache. I have another Unassigned SSD that I use for playing with VM Docker is configured to utilize a NVIDIA GT 1030, but I need something bolder like maybe a Tesla P40 What MB/CPU combo should I drop in that can use the 64GB memory? Then I will worry about the NVIDIA card

I have been using UNRAID for a long time. I found it to be solid with up time of 30+ days or before I have to tinker with it. In other words when I reboot its usually me. My power went out the other day. The server is on a UPS so it went down nicely as I do have NUT hooked up to it. I see the shutdown about 2:49 AM with these logs 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420152 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420160 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420168 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420176 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420184 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420192 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420208 Jun 1 02:49:41 SERVER kernel: md: recovery thread: P corrected, sector=1129420216 I have attached my diagnosis server-diagnostics-20240601-0552.zip

I had a problem with the latest release, updated the docker this morning and lost my unraid ui. Took me about 30 minute to figure out what was going on. Doing this in the cli brought it back but only temporary. /etc/rc.d/rc.php-fpm restart it kept stopping. All the docker were fine. All my hosted apps fine. Only the UI that kept stopping So I finally stop the unraid-api docker. And the problem went away. I think the docker was hammering the unraid server. Found a bunch of these in the logs and overloaded the UI Oct 1 07:30:18 SERVER nginx: 2023/10/01 07:30:18 [error] 9491#9491: *125230 limiting requests, excess: 20.002 by zone "authlimit", client: 172.17.0.13, server: , request: "GET /login HTTP/1.1", host: "192.168.7.11" They went away when I stopped the unraid-ap docker and the UI came back for good. I confirmed the issue by restarting the container eventually the UI was unresponsive. Not sure what is going on, passing along the info. Let me know if you need anything. Heading out on business tomorrow so i will be unresponsive during the week.

Brand new install from the template. New database . Getting this The `20210703194509_added_balance_to_account` migration started at 2022-11-06 00:51:23.824673 UTC failed I see the tables created in the deb, but the container fails to start. migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve The `20210703194509_added_balance_to_account` migration started at 2022-11-06 00:51:23.824673 UTC failed error Command failed with exit code 1. error Command failed with exit code 1. yarn run v1.22.19 $ yarn database:migrate && yarn database:seed && node main $ prisma migrate deploy Prisma schema loaded from prisma/schema.prisma Datasource "db": PostgreSQL database "ghostfolio", schema "public" at "192.168.7.11:5432" 52 migrations found in prisma/migrations Applying migration `20210604190809_initial_migration` Applying migration `20210605161257_added_symbol_profile` Applying migration `20210612110542_added_auth_device` Applying migration `20210616075245_added_sectors_to_symbol_profile` Applying migration `20210703194509_added_balance_to_account` info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. yarn run v1.22.19 $ yarn database:migrate && yarn database:seed && node main $ prisma migrate deploy Prisma schema loaded from prisma/schema.prisma Datasource "db": PostgreSQL database "ghostfolio", schema "public" at "my-ip:5432" 52 migrations found in prisma/migrations info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Getting for the 1st time today. I have a few new dockers running, but nothing that I can figure out. Help appreciated. "Your server has run out of memory, and processes (potentially required) are being killed off." Diagnostics attached. What exactly should I be looking for. server-diagnostics-20221017-0534.zip

CPU Look normal, My 20+ Dockers an VM seem to be running fine but the UI (remotely via ip address) is very very slow. It used to be instant. Any ideas. Working on getting a diagnostic as soon as I can server-diagnostics-20220622-1747.zip Went back to 6.10.2 rebooted a few times and seems to have done the trick, kind of scared to go to 6.10.3 again

Been using the container for a while with object detection. I did a fresh install. I noticed object detection was not working. Dropped into the container command line to execute bash zm_event_start.sh 834 2 from /var/lib/bash zm_event_start.sh 834 2 and go no permission had to do chmod +x *.* then it started working . WHen I updated to the new version yesterday I had to do the same thing. HOw can I make sure this get executed when I download the new image

Using a IOS phone I am having the same problem. Port forwarding seems to working as my windows client is working. Its just the phone that has problems

A series of unfortunate events, both USB drives i have are pretty sizable, meaning the stick out from the front of the tower server. The both of them have been bumped by me or the dog several times, he's a big dog. The first one took first hit and became unusable (to answer your question yes I back up religiously) , the 2nd one got bump months ago but has been usable since I am only now seeing problem. I will try out the chkdsk as soon as I have a chance , ideally though I have a lower form factor USB one that I can but in there and feel a little more confident about it being hit should I have to replace it. I did email support so we will see what they say.,

This is my 2nd flash drive since moving to Unraid and now I am getting a read only error on flash drive when it boots, in need to backup and copy to a new flash drive but will trouble copying the license again with the online tool. How many times can I replace the USB drive with the licensing tool?

It seems to be working well and doesn't require as much CPU as some of the other object detect solutions I have seen with home assistant. I will be playing with face recognition later. I will keep you posted. Thanks for putting the framework in place!!!

I finally got object detection working on my under powered Unraid server. It actually works pretty good pass the detected:car message in MQTT as part of the alarm. I have not played with the filitering in objectdetect.ini I had to make modifications to the userscript.sh in the OP to get it to work. It was missing some components that I discovered dropping into the container and running "bash /user/bin/detect_wrapper.sh EID MID where EID is event ID and MID is the monitor ID. #!/bin/sh # Python modules needed for hook processing apt-get -y install python-pip cmake apt-get -y install libsm6 libxext6 libxrender1 libfontconfig1 pip install numpy opencv-python imutils configparser Shapely future python setup.py install # Install for face recognition pip install face_recognition

I think I got it I had several problems. it was not picking up the script variable. I copied and pasted from here maybe something was wonky, then they script filed was not saved in a good linux format deleted it and rebuilt in in nano on the host. that seem to work.