flixxx

I have a cyberpower UPS, and my syslog fills up with usbhid-ups[1654118]: nut_libusb_get_report: Input/Output Error. the UPS is working fine, the dashboard is updating key attributes so i just want to suppress the log file. I have tried updating the ups.conf with pollonly, pollfrequency = 15 but the log keeps filling up every 15 seconds or so. I turned on enabled rule based syslog filters updated the xnut-nospam.conf with :msg, regex, "nut_libusb.*rror" stop :msg, regex, "nut_libusb_get.*Input/Output Error" -/var/log/nut-spam :msg, regex, "nut_libusb_get.*Input/Output Error" stop restarted syslog and they are still flooding my syslog with the error. Any help would be appreciated.

Thanks, i already had the syslog server enabled and storing it in the appdata folder, with 3 local syslog files. When I checked though, i noticed there are no syslog files. I thought that would be enough to store the files locally, i didn't realize i had to input the ip address of the server also (I was under the impression that setting was only to be filled in if i wanted to store the file on an external server). I do believe it's the power supply though, it's a 650 watt and i think it was borderline with all the hardware i had running.

Over the last several weeks, i noticed parity check randomly starts. A quick look at the logs seems like it had an ungraceful shutdown, i have it plugged into an APC UPS and we have not had any power outages so i'm not sure what's causing this. Any help with this please? kenny-diagnostics-20260404-1609.zip

The unclean shutdown concerns me, my UPS has ample time to shutdown the server and is configured to do so. I'm going to test it and ensure the battery is still in google health, and then it may indicate that maybe the power supply (?) The LSI overheating - All the fans are still spinning in the case. I'll remove the cover from the case and monitor the next few days, although i've had it running just fine during heat waves. Worth a look though.

Thanks, based on the errors, does that mean that my LSI is failing, or cables? (There are two breakout cables)... Could it be the port on the motherboard? looking for the best way to eliminate the possible issues one by one. I found it bizarre that it stated there was a power failure when we didn't have one.

Thanks, i've attached it. kenny-diagnostics-20260113-1740.zip

Hello, on January 10th, i got a disk 3 disabled drive error and none of the files were accessible. The logs (attached) were showing disk read errors across all disks. I shut down the server, replugged all SATA cables, rebooted and did not see any additional errors. I removed Disk 3 --> Readded it and rebuilt the drive. Everything seems to have worked fine, Today, i noticed similar errors (in log). I noticed this when i got a UPS error with "power failure" although we didn't have a power outage and for some reason a parity check kicked in. (don't worry auto correct is not enabled) There is no apparent issue with the server right now, all drives are green, files seem to be accessible. I suspect may be this is related to my LSI 9207-8i PCIe card but i have to check if those hard drives are connected to it or whether they are connected straight to the motherboard. Any advise on how to proceed? kenny-syslog-192.168.1.110-20260113-2127.zip kenny-syslog-20260113-2131.zip

I might have found a solution but I'm open to suggestions.. My approach: in the docker console, I would run any one of these commands depending on the folder structure and by process of elimination i would; du -hs | sort -h du -h | sort -h du -ha | sort -h Excluding my mapped volumes (in my case, /app/modules & /etc/codeproject/ai), I would go into each directory and run the same command until i pinpoint the biggest directories that are not mapped to a volume. it seems like my /.cache/pip folder might be the cause, i recorded the sizes and will check again in a couple of days. If there is an easier or more standardized method, i am open to suggestions.

Hello, my docker container has been growing in size. I installed doku and monitored it over the last week. Codeproject.AI_server has grown by over 3 GB in the last week. I checked the configuration and confirmed the two volumes are mapped correctly as per their instructions here. How can i monitor this over the next couple of days to identify which folders in the docker container are growing in size?

Hi, are you recommending that this is how I should treat unraid going forward? This will not be possible, if 6.13 is so fragile that leaving a tab open will cause the entire OS collapse, then this should be investigated and fixed at the source. In all my years running unraid and prior to upgrading to 6.13 this was NEVER an issue.

It just happened again, May 2nd 7:22 am. This is the start of the errors. i attached the full log May 2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: shpool alloc failed May 2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: nchan: Out of shared memory while allocating message of size 8717. Increase nchan_max_reserved_memory. May 2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: *6796183 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" May 2 07:22:26 kenny nginx: 2024/05/02 07:22:26 [error] 9348#9348: MEMSTORE:00: can't create shared message for channel /disks May 2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [crit] 9348#9348: ngx_slab_alloc() failed: no memory May 2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: shpool alloc failed May 2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: nchan: Out of shared memory while allocating message of size 8717. Increase nchan_max_reserved_memory. May 2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: *6796189 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" May 2 07:22:27 kenny nginx: 2024/05/02 07:22:27 [error] 9348#9348: MEMSTORE:00: can't create shared message for channel /disks syslog-192.168.1.110.log syslog-192.168.1.110.log

Anyone can offer any suggestions?

I noticed on the bootup log the following line Apr 9 05:42:02 kenny kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Is that a concern? What does it mean?

Since I upgraded to version 6.12 i have random crashes, difficult to replicate causing the server to be completely unresponsive remotely and physically there (the screen won't even turn on or keyboard respond) forcing me to reboot. Things I have tried; - Ensured Docker is set to IPVLAN - Upgraded from 6.12.6 to 6.12.9 - Enabled the syslog server I have another crashed on April 9th, what seems to be at around 3:32 am, the logs don't seem to provide anything of help. I have attached my diagnostics and the syslog, any help or input would be appreciated. Previous to yesterdays crash, the 2 times before that, I do know what the last thing i did was before it crashed: I have a windows VM running Blueiris and i logged into it to check the cameras. Yesterdays though, i did not perform that action. kenny-diagnostics-20240409-0554.zip syslog-192.168.1.110.log

I have not, i will try that the moment the parity ends. I do have a silly issue, since i run this headless. The last time i plugged my monitor in, it works when it's booted up, but during boot up (BIOS, POST, etc...) the screen doesn't work so i never see the menu to run memtest. I never bothered to try to fix it - any recommendation on what to look for?