Dovy6
Members
-
Joined
-
Last visited
Everything posted by 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?
-
-
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
-
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 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...
-
There appears to be a bug with nchan as seen in this link: https://github.com/slact/nchan/issues/534 It would seem to me that this is related to the issues I am having. This is the second or third time this has happened to me. Out of nowhere, with no apparent, obvious trigger, my syslog gets filled with hundreds of messages like this one: root@unraid:~# tail /var/log/syslog Mar 15 00:45:47 unraid nginx: 2021/03/15 00:45:47 [alert] 3161#3161: worker process 4945 exited on signal 6 Mar 15 00:45:49 unraid nginx: 2021/03/15 00:45:49 [alert] 3161#3161: worker process 4964 exited on signal 6 Mar 15 00:45:51 unraid nginx: 2021/03/15 00:45:51 [alert] 3161#3161: worker process 4985 exited on signal 6 Mar 15 00:45:53 unraid nginx: 2021/03/15 00:45:53 [alert] 3161#3161: worker process 5003 exited on signal 6 Mar 15 00:45:55 unraid nginx: 2021/03/15 00:45:55 [alert] 3161#3161: worker process 5023 exited on signal 6 This repeats forever until the logs fill up, and while this is happening Unraid grinds slowly to a halt. tail /var/log/nginx/error.log shows this root@unraid:~# tail -n 50 /var/log/nginx/error.log 2021/03/15 00:45:20 [alert] 3161#3161: worker process 4358 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:22 [alert] 3161#3161: worker process 4427 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:22 [alert] 3161#3161: worker process 4454 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:24 [alert] 3161#3161: worker process 4461 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:26 [alert] 3161#3161: worker process 4514 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:27 [alert] 3161#3161: worker process 4584 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:28 [alert] 3161#3161: worker process 4599 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:29 [alert] 3161#3161: worker process 4607 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:30 [alert] 3161#3161: worker process 4659 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:31 [alert] 3161#3161: worker process 4712 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:32 [alert] 3161#3161: worker process 4747 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:34 [alert] 3161#3161: worker process 4776 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:36 [alert] 3161#3161: worker process 4795 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:38 [alert] 3161#3161: worker process 4816 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:40 [alert] 3161#3161: worker process 4850 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:41 [alert] 3161#3161: worker process 4872 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:43 [alert] 3161#3161: worker process 4886 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:45 [alert] 3161#3161: worker process 4908 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:47 [alert] 3161#3161: worker process 4945 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:49 [alert] 3161#3161: worker process 4964 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:51 [alert] 3161#3161: worker process 4985 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:45:53 [alert] 3161#3161: worker process 5003 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. I happened to be using my server, logged in via ssh, when this happened this time, and I was able to run '/etc/rc.d/rc.nginx stop', and this terminates nginx (and obviously means I cannot use the Unraid GUI) but appears to stop the system from crashing to a halt. Please see where some others have noted that this may be related to an old, stale Unraid tab open in a browser somewhere. I will try to track down any open tabs. I only have one other computer that may possibly have a tab open but don't have access to it at this exact moment, so can't test that theory right now. I am unfortunately unable to trigger this bug on demand. I was able to generate a diagnostics.zip, but I'm having trouble uploading it right now. I think its a permissions issue. I'll attach it once I figure that out. Thanks for your help everyone
-
Quick search - it appears there's possibly a known bug in nchan. I'm not a developer but perhaps can one of you more code proficient people take a look please? https://github.com/slact/nchan/issues/534
-
This is happening to me again. Mar 15 00:18:04 unraid nginx: 2021/03/15 00:18:04 [alert] 32727#32727: worker process 13749 exited on signal 6 and until I stopped nginx with /etc/rc.d/rc.nginx stop, there's this: root@unraid:~# tail -f /var/log/nginx/error.log ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:18:30 [alert] 32727#32727: worker process 14062 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:18:32 [alert] 32727#32727: worker process 14100 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:18:34 [alert] 32727#32727: worker process 14132 exited on signal 6 ker process: ./nchan-1.2.7/src/store/spool.c:479: spool_fetch_msg: Assertion `spool->msg_status == MSG_INVALID' failed. 2021/03/15 00:18:36 [alert] 32727#32727: worker process 14179 exited on signal 6 2021/03/15 00:18:37 [alert] 14205#14205: *24668 open socket #3 left in connection 7 2021/03/15 00:18:37 [alert] 14205#14205: aborting I'm not quite sure where I have a stale tab open. This seems like a pretty bad bug. Any word on fixing it?
-
Getting this error recently My server has 2 nics (well 3 if you count the IPMI nic) and they're both plugged into the same switch. Is this not the way most people have it set up? Is there something wrong with doing it this way?
-
This did indeed fix the problem, thanks a lot
