jcreynoldsii Posted December 14, 2017 Share Posted December 14, 2017 I have been having issues for the past several months where I will try to access unraid via the web gui and I can't, its non-existent on my network. This forces me to restart my server. Its becoming quite annoying so I figured I would ask if anyone has ran into this problem. The only thing that I can think of that may be causing some grief is updating dockers every week. When I can get home and restart unraid I will post logs. In the meantime, does anyone have information that may link web gui/network failures to updating docker containers? Link to comment
Frank1940 Posted December 14, 2017 Share Posted December 14, 2017 A few questions. First, how much memory do you have installed in your server? Second, how often do you access the GUI? Third, provide us with a list of the Plugins, Dockers and VM's installed on your system? Fourth, upload the diagnostics file--- Tools >>> Diagnostics Link to comment
jcreynoldsii Posted December 15, 2017 Author Share Posted December 15, 2017 8GB I use the GUI almost exclusively Plugins (All Versions Latest) CA Auto Update Applications CA Backup / Restore Appdata CA Cleanup Appdata Community Applications Dynamix webGui unRAID Server OS Docker Containers Couch Potato DuckDNS Headphones Home-Assistant LazyLibrarian LetsEncrypt MQTT Mylar NGINX NodeRed Ombi Organizr Plex PlexPY Radarr SABNZBd Sonarr Transmission Unifi VMs Windows 7, Used for BlueIris Attached! Thanks! bennysrv-diagnostics-20171214-2028.zip Link to comment
Frank1940 Posted December 15, 2017 Share Posted December 15, 2017 I am a bit surprised that someone else hasn't jumped in here yet. I am not a real Guru in the area of VM's and multiple Docker usage. But since that hasn't been a response, here goes... You might be a little light in the RAM area. While 8GB might seem like a lot of RAM, that is one problem--- The process that runs the GUI can not be restarted if it gets 'bumped' from memory which can happen as unRAID runs entirely in RAM. (No HD usage for a disk cache to stuff a stale process rather than 'killing' it when more RAM is required by a running process.) If you don't get any other input, I would consider going to 16GB of RAM to see if that helps. Link to comment
tdallen Posted December 15, 2017 Share Posted December 15, 2017 55 minutes ago, Frank1940 said: You might be a little light in the RAM area. +1 Link to comment
jcreynoldsii Posted December 19, 2017 Author Share Posted December 19, 2017 On 12/15/2017 at 6:21 AM, Frank1940 said: I am a bit surprised that someone else hasn't jumped in here yet. I am not a real Guru in the area of VM's and multiple Docker usage. But since that hasn't been a response, here goes... You might be a little light in the RAM area. While 8GB might seem like a lot of RAM, that is one problem--- The process that runs the GUI can not be restarted if it gets 'bumped' from memory which can happen as unRAID runs entirely in RAM. (No HD usage for a disk cache to stuff a stale process rather than 'killing' it when more RAM is required by a running process.) If you don't get any other input, I would consider going to 16GB of RAM to see if that helps. I'll give that a shot. It was on the list to add more RAM and add a cache drive. Perhaps is the time to give my system an upgrade. Link to comment
jcreynoldsii Posted July 19, 2019 Author Share Posted July 19, 2019 I've upgraded to 16gb a while back., and I have had the issue happen 2-3x since. I'll get any where between 45-60 days of uptime when I start getting my issue. Its always exclusively happened when I start up a stream from Plex docker. Iwas using Fix Common Problems per another suggestion to capture log, i just realized since 6.7 its no longer apart of the plugin and now a native feature. With that said I need to configure my syslog server so that I can have some history for my logs in the event I get another crash in this similar manner. Link to comment
jcreynoldsii Posted July 19, 2019 Author Share Posted July 19, 2019 Just stumbled upon: Seems to be same issue as me. I'm going to upgrade my BIOS and check for this setting. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.