borland502

I love unraid. It's slick. It's powerful. And it is the only time raid has actually saved my data on consumer grade hardware. But. Well, it's on slackware. And slackware is like your grandpappy coming over and grousing about all these fancy package managers, conveniences, and cruft that other distros tart themselves up with. No, you must EARN your ability to have python: preferably have compiled it from source -- while forging the tools you need to build it from source as well. But like Prometheus brought fire from the Gods at great cost, there are tools that will uh, sorta, make life easier and upgradable: # Download slackpkg to /root (https://slackpkg.org/stable/slackpkg-15.0.10-noarch-1.txz) # Install slackpkg with `installpkg /root/slackpkg.txz` # vi /etc/slackpkg/mirrors and uncomment 1 mirror (https://slackpkg.org/documentation.html) # vi /etc/slackpkg/slackpkg.conf -- DIALOG=off # slackpkg install dialog-1.3_20211214-x86_64-1 # slackpkg install gpgme-1.16.0-x86_64-3 # slackpkg install gnupg-1.4.23-x86_64-4 (This is the package that slackpkg expects for verification) # slackpkg update gpg # slackpkg install python3-3.9.14-x86_64-1_slack15.0 # You can continue using the only training wheels you're going to get on slackware on the cli, or automate with ansible (https://docs.ansible.com/ansible/2.9/modules/slackpkg_module.html). Now the warning. I am but a journeyman linux fellow that loves to proceed disasters with a casually drawled "hold my beer" and slackware (and unraid itself) protect you from world ending disasters for most users while offering a lot of what you could get at a lower level. Tread lightly, and do not look to the Neckbeards for salvation when things go kablooey. This was a speed run, quickly googled together and verified once. You hath been warned. EDIT: slackpkg is limited compared to Nerd/Dev plugins so I ended up installing linuxbrew in a second account. This is even more off the rails, but I've done it before I found the plugins that gave me extra tools in a less janky fashion. You'll need these to get the most flexibility out of homebrew. slackware_common: - zsh-5.8-x86_64-3 # or use existing bash - gcc-11.2.0-x86_64-2 - procps-ng-3.3.17-x86_64-2 - file-5.41-x86_64-1

Figured it out. User error naturally, but the problem was I'd created a bad SSL certificate ... or rather untrusted. But since the UI didn't die until days after with no reboot I didn't make the obvious connection. Anyway, thank you for your patience and questions.

The dh command was done before a reboot, but still no joy on the diagnostics run -- it still freezes. These diags may be of little help, but were taken 9 days ago when I was looking through the /boot/logs dir merel-diagnostics-20220820-1443.zip

Filesystem Size Used Avail Use% Mounted on rootfs 16G 2.5G 14G 16% / tmpfs 32M 1.8M 31M 6% /run /dev/sdh1 15G 1.3G 14G 9% /boot overlay 16G 2.5G 14G 16% /lib/firmware overlay 16G 2.5G 14G 16% /lib/modules devtmpfs 8.0M 0 8.0M 0% /dev tmpfs 16G 8.0K 16G 1% /dev/shm cgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup tmpfs 128M 24M 105M 19% /var/log tmpfs 1.0M 0 1.0M 0% /mnt/disks tmpfs 1.0M 1.0M 0 100% /mnt/remotes tmpfs 1.0M 0 1.0M 0% /mnt/rootshare /dev/md1 233G 31G 203G 14% /mnt/disk1 /dev/md2 3.7T 1.6T 2.1T 44% /mnt/disk2 /dev/md3 3.7T 2.0T 1.7T 55% /mnt/disk3 /dev/md4 5.5T 2.0T 3.6T 36% /mnt/disk4 /dev/md5 4.6T 33G 4.6T 1% /mnt/disk5 /dev/sdi1 932G 88G 843G 10% /mnt/home /dev/sdk1 932G 231G 701G 25% /mnt/media /dev/nvme0n1p1 477G 324G 153G 69% /mnt/nvme_win_cache /dev/sdl1 466G 6.8G 458G 2% /mnt/var shfs 18T 5.6T 12T 32% /mnt/user0 shfs 18T 5.6T 12T 32% /mnt/user /dev/loop2 500G 16G 482G 4% /var/lib/docker /dev/loop3 1.0G 4.5M 904M 1% /etc/libvirt tmpfs 3.2G 0 3.2G 0% /run/user/0

😊 And so it does. I apologize. I missed the line. The script had been hanging on me and I thought it depended on the ui part (/usr/bin/php -q /usr/local/sbin/diagnostics). If it completes in the next few hours I'll post it here, but otherwise I'll assume my problem to be php related as everything else about the system is humming along fine. Php processes are running, including the script, so maybe I'm just underestimating the time. It'd not be the first time impatience has made me act foolish. Edit: I pulled the plug after 6 hours

I would be happy to do so, but I am unable to access the dashboard and the diagnostics script doesn't look like it is cli friendly. The dashboard is the only impacted feature, for me at least. If there's anything I can provide please let me know, but the next step for me is an orderly shutdown and restart. I've already restarted the applicable services. The nginx log had built up 30GB of the above and has done so before. Unfortunately, I truncated the log last night so my reply wasn't expecting much in the way of help -- just that I've seen the problem before as well 2022/08/27 04:33:55 [info] 659#659: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:160 2022/08/27 04:44:01 [info] 16302#16302: Using 131072KiB of shared memory for nchan in /etc/nginx/nginx.conf:160

Yeah, been seeing this problem too recently filling up the log space.

Well call me a necromancer, because this thread's alive! ALIVE! .... to thank the solution's author. Thank you. I know I chose the path of pain despite Unraid being an excellent product, but it was discouraging to have extracted the rom, done this & that, and periodically get stuck with a resolution that would have wowed me only in my childhood.