Dovy6

I used to get notified by Unraid when my power would drop - "UPS on Battery," etc. I haven't received any such emails recently. Yesterday the power went out, as far as I could tell Unraid shut itself down appropriately, but I didn't receive any notifications. Is there a setting I missed somewhere on the new NUT?

6.12.2

Am I nuts, or am I doing something wrong? I have Docker Folder installed on my server, and FCP's update assistant is telling me to install Folder View instead before updating Unraid. But I can't find Folder View plugin in the CA Appstore. Do I have to uninstall docker folder before folder view appears? Am I doing something else wrong? Thanks

I ended up apparently completely resolving the problem with an unraid reboot. I'd love to know if this was a fluke or if something if failing and it's a matter of time before this happens again

I have a cache pool drive on my unraid server I've been using as a Blue Iris mount point. About 4 or 5 days ago it started spamming errors like "[2023/04/12 20:29:37.262736, 0] ../../source3/smbd/close.c:312(close_remove_share_mode)" followed by "close_remove_share_mode: Could not get share mode lock for file New/Doorbell.20230314_110000.bvr" I'm attaching my diagnostics. Is the drive dead? SMART isn't showing any errors unless I'm reading it wrong. Is the stuff on the drive gone forever? That wouldn't be the end of the world, but obviously I'd prefer not. Please advise if I missed anything, and thanks so much. unraid-diagnostics-20230416-0059.zip

Using Unpackr, it's now refusing to start with error: The template states to leave it blank if you're not using Lidarr. I'm going to see if it will run with a random 32 character string, or if I can delete the mapping from the template, if that will help EDIT: random 32 characters (just copied and API key from Radarr, which I am using) worked and Unpackrr is working again

How critical is this error? Is this "the machine may crash and burn at any moment" critical, or "You need to replace that RAM stick before further issues arise" type critical? Thank you so much for your help

FCP is telling me about a Hardware Problem I apparently have. I've attached Diagnostics as recommended, below. Can anyone help me and tell me if everything is about to die on me? No noticeable symptoms from the machine, other than being flagged for this error. Thank you unraid-diagnostics-20210827-1635.zip

again, the logs filling up are a symptom, not the disease. You can increase the log size to the size of your array, it's nginx crashing that's the problem, not the log generated by that

The actual problem is that nginx keeps crashing, not that the logs get full. Each time nginx crashes, it logs it, and restarts. It then crashes again, logs it, and restarts. this keeps happening, which is why the logs quickly get filled. But the full log itself isn't the problem, and isn't why Unraid slogs down until you reboot. It's the bug causing nginx to crash that's the problem

Damn thank you, I know now which computer caused the issue back then. I've never installed the my servers plugin, though?

I don't and never have had that plug-in installed

Phone?

A stale gui tab means that in some computer, somewhere, there's an unraid tab open that hasn't been used in too long, and is causing this issue for some reason. Restart any open browser you have on any computer

Almost definitely. I use the tabs often, though. I have the same open browser windows on my laptop for months now, both firefox and chrome, each with at least 2 unraid tabs. Recently I've been using my desktop computer more and my laptop less, meaning my laptop tabs have been stale for a while. Probably over a week since I've used them...

I have used the web terminal before. The last time I had this error crop up I was using putty, though. I'm not sure if the web terminal is a potential source. I can open the web terminal and play around and see if I can trigger the bug... Any clues as to what I should do that would potentially cause it? Any help from my logs attached above, when the error happened and when I was able to clear it by restarting web browsers?

Please let me know if there's anything you can suggest I do to try to trigger it to help isolate the bug. Also, be advised, I updated to 6.9.2 today. Again, this only happens occasionally (has happened to me at least 3 separate times,) but I don't know why or when

I am using the stand alone app, putty, to acess my server. I have not yet determined how to intentionally trigger this happening, unfortunately, so I can't explore and figure out exactly where the bug gets triggered. I access Unraid with both Firefox and Chrome, and yeah, I'm the guy with 3 browser windows and 30 tabs open in each. I am unsure, but to the best of my recollection, it was Chrome that I restarted to fix the problem. I can't promise that I'm correct, though, unfortunately.

Haven't updated to .2 yet, but I did have this error occur on 6.9.1, yes

I've done that. User "mover stop" in the terminal. Unfortunately millions of tiny files will take forever to move no matter how you do it.

pulled linuxserver/papermerge:v1.5.5-ls26 and that starts right up with no problem. It seems there may be an issue with v2.

Just installed this, fresh, and it doesn't work - ```[uwsgi-daemons] throttling "/usr/bin/python3 ./manage.py worker" for 32 seconds``` seems to be the main error. I'll try a previous tag version. But it seems like there's a problem with the default linuxserver/papermerge

I went and restarted the browsers on my laptop, while I had putty open in several windows running 'tail -f /var/log/syslog' and 'tail -f /var/log/nginx/error.log' The errors stopped after restarting the browsers. I am attaching an updated diagnostics.zip file from after in the hope that it can help. unraid-diagnostics-20210315-1541.zip

I take that back. I just went and restarted the entire browser and, for now, the errors appear to have stopped.

I've submitted a bug report - however, Iv'e gone and closed all open Unraid GUI tabs on all my browsers and it didn't seem to fix the problem... So I think it may be something other than the stale tab...