kimocal

Have you been able to get the IPMI working yet?

Fan control is the next thing I need to work on. I was able to get the fan speeds to get reported finally.

Created and moved all 3 files to the appropriate locations. Tried doing the Install Plugin and was getting an error saying the XML does not exist or xml parse error: I then rebooted unraid and the plugin disappeared from the /boot/config/plugins/ folder. Re-copied join-agent.plg to the plugins folder. Tried to re-install the plugin and get the same error as above. I even tried copying the XML to /usr/local/emhttp/plugins/dynamix/agents/Join.xml Nothing appears to exist at /var/log/notify_Join No worries on trying to get this to work. I've transitioned over to Telegram to centralize and organize my unraid and related notifications better. If you want me to keep testing though I can. Thanks for trying to help.

I have the Asus Pro WS Z890-ACE SE running 7.2.0 and I don't see any errors like that in my my syslog. I only see these: Nov 5 19:21:47 Megamind root: error log : /var/log/graphql-api.log Nov 5 19:22:09 Megamind kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.RP01.PXSX._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184) As a side note how are you liking the w880? That was one was my second choice but wanted the 10G NIC.

It was located under the Settings --> Notifications like all the other modes. Where would I find the JOIN xml? Doing a quick search of my flash backup I did find this bash script, join.sh. Copy and pasted below as it's pretty basic. I've removed my API key. #!/bin/bash ########## API_KEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" TITLE="$SUBJECT" MESSAGE="$DESCRIPTION" ########## TITLE=$(echo -e "$TITLE") MESSAGE=$(echo -e "$MESSAGE") curl -s -k -G \ -d "apikey=$API_KEY" \ --data-urlencode "title=$TITLE" \ --data-urlencode "text=$MESSAGE" \ -d "deviceId=group.all" \ https://joinjoaomgcd.appspot.com/_ah/api/messaging/v1/sendPush 2>&1 Join.sh

I too am missing the JOIN notification agent I had previously on 6.12. I upgraded to 7.2.

Did you merge these systems? Im about to do the same.

Oh nice. Have fun with it

What repo are you using? I am using this one as I have a Tesla P4. Post a pic of your container config to compare.

Access your CP AI IP and Port Then click the appropriate INSTALL for the module you want. Be patient as it takes time.

No. The inference times of the LPR on CPU are pretty quick. YOLO uses the GPU. It's working at the moment as is so I haven't tinkered with it since. Currently on 2.6.5.

I'm currently running this container with Repository: codeproject/ai-server:cuda12_2 I have a Tesla P4 installed. Object Detection (YOLOv5 6.2) 1.9.1 is running great with the GPU. Does anybody know how to or if the License Plate Reader module can use the GPU? Every time I try enabling GPU it reverts back to CPU. Also if I update YOLOv5 6.2 to 1.9.2 it seems to break GPU functionality.

My wife and I are the only users for our nextcloud instance. We recently started having an issue where the connection will die and I will have to restart the container. Attached is my syslog I am getting from the syslog server. Any ideas based upon the syslog? Apr 11 15:11:14 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="23380" x-info="https://www.rsyslog.com"] start Apr 11 15:14:33 tower ool www[30194]: /usr/local/emhttp/plugins/dynamix/scripts/rsyslog_config Apr 11 15:14:35 tower rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="30614" x-info="https://www.rsyslog.com"] start Apr 11 16:35:02 tower kernel: docker0: port 2(veth048550e) entered disabled state Apr 11 16:35:02 tower kernel: veth4f0e390: renamed from eth0 Apr 11 16:35:02 tower kernel: docker0: port 2(veth048550e) entered disabled state Apr 11 16:35:02 tower kernel: device veth048550e left promiscuous mode Apr 11 16:35:02 tower kernel: docker0: port 2(veth048550e) entered disabled state Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered blocking state Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered disabled state Apr 11 16:35:02 tower kernel: device veth4583332 entered promiscuous mode Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered blocking state Apr 11 16:35:02 tower kernel: docker0: port 2(veth4583332) entered forwarding state Apr 11 16:35:02 tower kernel: eth0: renamed from veth4daad3b Apr 11 16:35:02 tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4583332: link becomes ready Apr 11 16:35:02 tower kernel: docker0: port 9(vethdcf57da) entered disabled state Apr 11 16:35:02 tower kernel: veth0389db9: renamed from eth0 Apr 11 16:35:03 tower kernel: docker0: port 9(vethdcf57da) entered disabled state Apr 11 16:35:03 tower kernel: device vethdcf57da left promiscuous mode Apr 11 16:35:03 tower kernel: docker0: port 9(vethdcf57da) entered disabled state Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered blocking state Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered disabled state Apr 11 16:35:03 tower kernel: device vethd8cddd5 entered promiscuous mode Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered blocking state Apr 11 16:35:03 tower kernel: docker0: port 9(vethd8cddd5) entered forwarding state Apr 11 16:35:03 tower kernel: eth0: renamed from veth976f3a7 Apr 11 16:35:03 tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd8cddd5: link becomes ready Apr 11 17:15:04 tower kernel: veth2e3f8cd: renamed from eth0 Apr 11 17:15:04 tower kernel: eth0: renamed from veth79ca70e