Posts posted by jbuszkie
6 hours ago, xthursdayx said:
Any ideas? For some reason, I'm currently unable to download my diagnostics, but any advice or ideas would be much appreciated. Cheers!
You posted the space available for your cache and others.. But how much space do you have left in /var? Was it full?
The first thing I do is delete the syslog.1 to make some space so it can write the log, then I restart nginx. Then I tail the syslog to see if the writes stop. My syslog.1 is usually huge and frees up a lot of space so it can write to the syslog
The time before last time, I still had some of those errors in the syslog after the restart.. So I was going to stop my dockers one by one and see if it stopped. And well it did with my first one.
Two days ago when then happened to me.. I didn't have to do that. the restart was all I needed...
2 hours ago, Flemming said:
I have the same problem and /etc/rc.d/rc.nginx don't fix anything, not even temporarily
strange that /etc/rc.d/rc.nginx restart didn't fix it.
I assume you made room in /var/log for more messages to come through?
After the restart did you still have stuff spewing in the log file?
I do recall a time where I had to do a restart to fix it completely.
No.. I never did...
This happened again to me last night. I've been really good about not leaving web terminal windows open. Well.. I didn't have any last night open or for a while.
What I did have different was I had set my grafana window to auto refresh every 10s. I wonder if that had anything to do with this problem?
Also.. The restart command didn't completely fix it this time. I was still getting a bunch of these...
Aug 23 09:09:49 Tower nginx: 2021/08/23 09:09:49 [alert] 25382#25382: worker process 1014 exited on signal 6 Aug 23 09:09:50 Tower nginx: 2021/08/23 09:09:50 [alert] 25382#25382: worker process 1044 exited on signal 6 Aug 23 09:09:51 Tower nginx: 2021/08/23 09:09:51 [alert] 25382#25382: worker process 1202 exited on signal 6 Aug 23 09:09:53 Tower nginx: 2021/08/23 09:09:53 [alert] 25382#25382: worker process 1243 exited on signal 6 Aug 23 09:09:54 Tower nginx: 2021/08/23 09:09:54 [alert] 25382#25382: worker process 1275 exited on signal 6 Aug 23 09:09:55 Tower nginx: 2021/08/23 09:09:55 [alert] 25382#25382: worker process 1311 exited on signal 6 Aug 23 09:09:56 Tower nginx: 2021/08/23 09:09:56 [alert] 25382#25382: worker process 1342 exited on signal 6 Aug 23 09:09:57 Tower nginx: 2021/08/23 09:09:57 [alert] 25382#25382: worker process 1390 exited on signal 6 Aug 23 09:09:58 Tower nginx: 2021/08/23 09:09:58 [alert] 25382#25382: worker process 1424 exited on signal 6 Aug 23 09:09:59 Tower nginx: 2021/08/23 09:09:59 [alert] 25382#25382: worker process 1455 exited on signal 6
I started to kill my dockers and after I stopped the HASSIO group, That message stopped. I restarted the docker group and it hasn't comeback.
I really wish we could get to the bottom of this!!
FYI.. I'm now on 6.9.2
On 8/11/2021 at 7:38 PM, ljm42 said:
Would you please try this again? It should work now.
This form updates DDNS for your server and we recently made a server-side change to the DDNS script that caused problems here. Sorry about that
Yeah.. It works fine now!
Can't wait for it to be able to send encrypted flash images!
I have to upgrade my flash drive though! It's only one Gig.... And maybe 11 years old! Might be time anyway!! lol
15 hours ago, ljm42 said:
The ping will fail but what we are checking is whether it is able to resolve the IP address. If you see this then DNS rebinding is properly disabled:
Pinging rebindtest.unraid.net [192.168.42.42] with 32 bytes of data:
Yup.. That works fine.
7 minutes ago, ljm42 said:
This sounds like a client-side problem. What browser are you using?
Try doing this in private/incognito mode as that disables most browser extensions.
I tried that with the same result.Quote
Also, please upload your diagnostics (from Tools -> Diagnostics)
Sure.. I looked in the logs and saw nothing. This is the only spot were I get this. If I change the "Use SSL/TLS" to No.. That change happens just fine.. It's only if I muck with the "My servers" section.
Not sure what the update DNS is supposed to do? (generate a new certificate?) But that seems to not come back either.
3 minutes ago, ljm42 said:
DNS rebinding protection prevents "yourpersonalhash.unraid.net" from resolving to a LAN IP. So in order to enable SSL for Local Access you must permanently disable DNS rebinding protection.
Yeah.. I figured that out. I was able to setup a DNSMASQ setting to allow unraid.net in my tomato config
I do get the spinning circle every time I try to apply when I change something in my servers area.
If I disable remote access... I get the spinning circle.
But when I go back to something else or refresh, I see the new setting. Same thing if I enable .. I get the spinning applying that never goes away.. But if I refresh, it sticks.
However... If I try to change the port, it never sticks. I always see the 443 port. Double however... if I actually try the remote
access, I see the new port being used and it works fine even though the webpage settings still says port 443.
I do have the flash backup disabled if that has anything to do with this...
Bug? Something with my setup?
Trying to updated the WAN port on myservers and I just get the spinning circle on "applying" button.
If I go to another page and then come back.. I still see the default port of 443.
Second question.. Do I have to keep "prevent DNS rebind attacks" unchecked on my router once I provisioned?
21 minutes ago, sage2050 said:
I applied hyperv's fix but im still getting "not available" on all my dockers. Do I need to do anything after I edit the file?
I had the same thing yesterday.. But when I checked it this AM.. It was now working... So it just took some time for me.. I don't know why.. Maybe someone with more knowledge can explain it or show how to get the fix to work immediately ..
I tried the manual fix... But it isn't working. I still get the "not available"..
Is there some sort of service I have to restart?
preg_match('@Docker-Content-Digest:\s*(.*)@i', $reply, $matches);
That's what's in my file...
I've manually changed the Influxdb to 1.8 That fixed my auth issues. But a could days ago or so I have a notice that there is an update to influxdb. If I set the version for 1.8, why is it still saying there is an update available?
The only correlation I have figured out might have something to do with using the web browser terminals. I've tried to avoid using them and I haven't had an instance in a while now. I've also made sure they were all closed down right after I used them. Before I was using them and possibly leaving them open on different machines.
Not sure if that's it, but that's the only thing I can think of that might slightly correlate.
Ha.. I had to refresh my browser to see there was an OS update! When I wrote the first message the update OS thing only showed 6.8.3
I still prefer to wait to a while before upgrading. So I guess I don't update this plugin until I switch. Oh Well... Thanks for the great plugin though!
On 3/3/2021 at 8:44 AM, olehj said:
- Commit #161 - FEATURE: Formatting of the comment field has been added, read "Help" for more information under the "Tray Allocations" tab. @shEiD
- Commit #158 - BUG: NVME drives not detected with Unraid 6.9 because of changes in the output of lsscsi. From now on only Unraid 6.9 and above is supported. Older releases has to use the developer build without nvme support or previous Disk Location version. @Woutch @lovingHDTV
is 6.9 released or is it still beta? I can't update because it was restricted to 6.9?
I try not to upgrade until the next unraid version is stable for a while... I guess supporting something in the beta version breaks the current released version?
I'm on 6.8.3 ... Which I thought was the latest stable?? Are you saying we should try the latest beta?
My terminal is all messed up when in this state as well... I have to use a putty window to talk to unraid.
Ok.. it happened again today! grrr....
I'm posting this here to try for next time so I don't have to reboot..Quote
To restart nginx i've been having to use both
and /etc/rc.d/rc.nginx stop
Quite often checking its status will show its still running. So make sure it's really closed. It doesn't want to close gracefully
I'll have to see if this resolves the out of memory issue without a reboot...
I'd still like to know what's causing this or how to permanently avoid this...
Mine just happened again today... @limetech, any thoughts on this? It seems like there are several of us that have this issue?
Mine just happened again. Is there a way to fix this without re-booting the system?
1 hour ago, Skylord123 said:
There aren't really "Best Practices" as it all depends on what you need logged and your use case. I'm using MQTT for my home automation so I really only care about logging what devices connect and error messages. This is what I have my log options in mosquitto.conf set to:
log_dest stderr log_type error connection_messages true log_timestamp true
If you really want to add log rotating it is an option you can pass to the container. Here is a post that describes it very well:
Thanks for the info. so it was really just as easy as purging the log! I wanted to make sure. Thanks! I'll have to look into the log rotate if I want to do that.
52 minutes ago, spants said:
Which file is that size? Can you post your mosquitto.conf file?
I was logging the default which was everything, I believe.. I've recently changed it to just errors and warnings. But I can't figure out how to purge it.. Or, potentially, how to use log rotate to keep it manageable. How do other folks handle the mqtt logging? Do they log everything but put it in appdata area?
What are best practices?
nginx running out of shared memory
in General Support
@limetech Is there any way you guys can start looking at this? There are more and more folks that are seeing this.
For the rest of us... Maybe we should start listing our active dockers to see if one of them is triggering the bug. Maybe there is one common to us that's the cause. If we can give limetech a place to start so to more frequently trigger this condition, it would probably help them..
For me I have
I have no running VMs
My last two fails did not have any web terms open at all. I may have had a putty terminal, but I don't think that would cause it?
I do have the dashboard open on several machines (randomly powered on) at the same time..