AceBurn90

My log is full, and I know why, because the massive log was deliberately activated for the dry run of my “Mover Tuning” plugin to test it. Now I have deactivated the log for it, but my log is still full. 1. What can I do to empty or rotate the log during operation without having to restart? 2. How can I increase the size of the log? Attached is my anonymized diagnostic and, in addition, my log: root@Alent:~# du -sm /var/log/* 0 /var/log/btmp 0 /var/log/cron 0 /var/log/debug 1 /var/log/dmesg 1 /var/log/docker.log 0 /var/log/faillog 0 /var/log/file.activity 0 /var/log/fileactivity-watcher.log 1 /var/log/fileactivity-watcher.log.1.gz 1 /var/log/fileactivity.log 1 /var/log/gitcount 1 /var/log/gitflash 1 /var/log/gitflash1 1 /var/log/graphql-api.log 0 /var/log/lastlog 0 /var/log/libvirt 0 /var/log/maillog 0 /var/log/messages 0 /var/log/nfsd 1 /var/log/nginx 0 /var/log/packages 1 /var/log/phplog 11 /var/log/pkgtools 0 /var/log/plugins 0 /var/log/pm2 0 /var/log/preclear 0 /var/log/pwfail 0 /var/log/removed_packages 0 /var/log/removed_scripts 0 /var/log/removed_uninstall_scripts 11 /var/log/samba 0 /var/log/scripts 0 /var/log/secure 0 /var/log/setup 0 /var/log/spooler 0 /var/log/swtpm 2 /var/log/syslog 21 /var/log/syslog.1 84 /var/log/syslog.2 2 /var/log/unbalanced.log 0 /var/log/unraid-api 0 /var/log/vfio-pci 0 /var/log/vfio-pci-errors 1 /var/log/wtmp alent-diagnostics-20260125-1430.zip

Sorry for my late reply. Thanks to you, I was able to partially break down the problem to several plugins that were being used for energy efficiency. Apparently, there were incompatibilities. I then removed them and things improved. Unfortunately, my system simply consumes too much energy... I'll keep tracking the problem for a few more months, as I don't want to restart my server too often. I just had two hard drives (1x parity and 1yx array disk) that were deactivated because I unfortunately had to perform a hard reset several times. But after a rebuild, everything looks fine again. Restarting also worked more or less fine. However, I (finally) encountered an inconsistency between my motherboard hardware and the HBS card, which meant that my hard disks sometimes did not boot up and initialize when starting up and got stuck before booting. No matter how long I waited. This can still be reproduced by restarting the server. Sometimes it works the first time, but more often than not, the system simply won't start until I perform a hard reset and hope that it will start the next time, or the time after that, or the time after that... I haven't read up on it enough yet, but I've learned that it's probably due to the BIOS/UEFI and/or the settings of this or the firmware of the HBA card. Mainboard: ASUS ProArt X670E-Creator WIFI (Version 2604; BIOS dated: Friday, 29.11.2024) HBA card: Broadcom SAS 9305-16i, PCIe 3.0 x8 -> How do I check the firmware version?

So far the system has not crashed, but I have noticed that when I want to stop the array, it cannot be stopped properly. The following is displayed at the bottom left of the page: Array Stopping-Retry unmounting disk share(s)... I then performed a forced reboot. I have attached the diagnostics file. I created this after I started the array and then wanted to stop it again. In between, I created a new pool and assigned an SSD to it. How can I fix this? I have also activated logging since 31.05.2025. I can also provide the logs if you tell me exactly where the required files are located. The logs should be saved somewhere on my Unraid USB flashdrive. alent-diagnostics-20250610-2258.zip

I have activated “Mirror Syslog to flash”. As soon as the server hangs the next time, I will post the log with a new diagnostic file. For now, here are the two diagnostics from right after the last two hangs when I had to hard reset the server. Perhaps something can already be read from them or the error can be narrowed down a bit better. alent-diagnostics-20250524-0258.zip alent-diagnostics-20250531-1132.zip

Hello, my Unraid 7.1.2 server seems to hang repeatedly. Most recently today. Now I won't be home until tomorrow to restart the server :( The problem seems to have already happened twice when I was navigating in the dashboard. Before that I had the problem that the network adapter wouldn't connect in a way I couldn't explain. I had to log on to the server locally. After logging on and checking the network adapter, I was able to restart the server and make it accessible from the network. I have a 10Gbit and a 2.5 Gbit Ethernet interface on the mainboard and also WLAN and Bluetooth, but these are deactivated and no antennas are connected. Only the 10Gbit connection is plugged in. Just half an hour ago I was connected via VPN on the road and had the Main tab open, when once again a 404 message appeared in the browser because my VPN tunnel no longer had a connection. My Plex server is also offline and I'm not getting any response via Unraid Connect either. Last time I created a diagnostic file after the reboot but haven't posted it yet. When I get back home tomorrow, I will regenerate this and post it here to have my problem checked. The whole thing is very frustrating because shortly before my USB stick with the system was defective and was replaced and in December my server hardware was partially broken. Anythin other I can tell you to identify the problem or any idia what I can check tomorrow? I hope I can find the problem quickly with your help tomorrow. Best regards Ace

Thanks for your help! I will try it.

Reinstalling didnt help me Can you tell me which setting you mean with bonding? Do you mean the "Network Type:" or bonding two NICs? -> If you mean the later, I only have one NIC in use. Any other guesses, why I cant load the page -> http://localhost:port ???

Yes, I did it for http and https.

When I open the local page via http://x.x.x.x:4743 the page is loading forever but when I open http://x.x.x.x:4743/admin it opens the VaultWarden configuration site. The same happens when a friend opens it from a different network.

When I click my page in NPM it opens the cloudflare error landing page. I have tried both in NPM, HTTP and HTTPS. Both result in the same error. The server time/date is correct.

Hi everyone, I’m encountering an issue with my NGINX Proxy Manager (NPM) setup in combination with Cloudflare and the SSL Handshake Failed error (Error 525). Setup: NGINX Proxy Manager is running in a Docker container on ports 18443 (HTTPS) and 1880 (HTTP) and with the Web UI Port: 7818. The Vaultwarden WebUI port is 4743. I just have changed the default admin credentials and under "General settings" the Domain URL to "http://example.com" (obvious my domain). In my Cloudflare DNS entrys I have added a CNAME with the name "XYZ" and with the target "example.com". Proxy-status is activated und TTL is auto. I have set up the configuration according to the following instructions: Vaultwarden -> https://www.youtube.com/watch?v=vHo9TwSqxaM NPM -> https://www.youtube.com/watch?v=nhacNUxVcy4 I have successfully configured a Let’s Encrypt SSL certificate for my domain through NPM. My domain has also a valid Lets Encrypt certificate on Cloudflare. The SSL/TLS mode in Cloudflare is set to “Full”, and the domain is hosted on Cloudflare. Ports 443 and 80 are correctly forwarded in my router (external 443 to internal 18443, and external 80 to internal 1880). I checked the SSL-certificate successfully with https://www.sslshopper.com/ssl-checker.html. I also testet the DNS successfully with https://dnschecker.org. Problem: When trying to access my domain, I get the “SSL Handshake Failed” error with Error Code 525. I’ve verified that my SSL certificate in NPM is valid and that port 443 is open and reachable externally. Cloudflare settings are correct, but I still can’t establish a successful connection to the server. I have already done a lot of research and ChatGPT also thinks it could be one of these two possibilities: - Cloudflare expects my server to be listening on port 443, but my NPM container is listening on port 18443. - There might be an issue with the port forwarding or SSL certificates. What I’ve already tried: Set the SSL/TLS mode in Cloudflare to “Full”. (also tried to switch for a couple seconds to Flexibel) Tested the Cloudflare proxy (switching to Gray) and tried direct connections. Checked port forwarding and confirmed the SSL certificate status. For a more in-depth assessment, I have attached the anonymized diagnostic. I would appreciate any help or suggestions on how to correctly set up the connection between Cloudflare and my NGINX Proxy Manager so the SSL handshake succeeds. Has anyone had similar experiences or found a solution? Thanks in advance! alent-diagnostics-20250315-0131.zip

The strange thing is that when I stop the container and then start it again, SABnzbs works normally again. Until the next time I want to load something (days later), it doesn't work again??? The file system is ZFS. I have upgraded my server with new MB, RAM, CPU and case. Then I changed the cache from XFS to ZFS. I used 2 NVme's for this. I moved the “system” and “docker” folders from the first (XFS) to the second NVme (ZFS) using a mover job. Then I formatted the first SSD in ZFS and moved the two folders from SSD2 to SSD1 using a mover job. I don't know if this caused the problem or if many other things have caused this problem, because I have changed so much this week.

I must have rejoiced too soon. I'm still getting errors. alent-diagnostics-20250125-2230.zip

My new Server is ready. See my My server is now finished and in use. The hardware components can be found in my signature -> just expand.

I have now put everything in the SABnzbd and the subdirectories as you recommended, because I like the idea of having fewer shares. I now have a “Download” share and in it are e.g. the download folders of “jDownlaoder 2” and “SABnzbd” with subfolders for “# Incomplete ‘ and ’NZB Grabber” in the folder “# Incomplete”. Now everything works. Thanks for the neat idea.