WebUI repeatedly unresponsive.


10 posts in this topic Last Reply

Recommended Posts

Hello. I am new to Unraid.  I had a windows based plex server / file server that I decided was time to protect with parity or raid.  After doing some research, I determined that Unraid would best suit my needs. I am using the latest version of the Unraid trial (I really like it so far and want to purchase a license, but only if I can resolve the issues below). 

I am having some very intermittent issues with the WebUI and all of my dockers becoming unresponsive.  This might happen multiple times a day at random times, or it might skip a day and happen multiple times afterward.

My symptoms are as follows. I might try to access something from plex, krusader or just the array on windows file explorer.  One of two things happens.  Either it works for a minute and stops working, or it doesn't work at all. Then I try to access the WebUI and it won't respond.  This happens on all browsers from multiple computers.  All the dockers also become unresponsive. I can telnet into the server, but for some reason the webui seems to have crashed and I can't bring it back online without doing a power cycle.  Not only is this not ideal, its not safe to power cycle the device multiple times a day.

This shouldn't be a ram issue. I have 32gb of ram, completed memtest without errors.  I don't think the CPU would overload either because I have a Ryzen 1700 in my server.  I realize there might be some architecture incompatibilities or something there, however.

Anyways, if someone could point me in the right direction it would be greatly appreciated. I'm happy to post diagnostics files but I don't know how to obtain them.

 

Thanks,

Harry

Edited by harryt04
Accidentally submitted first post too early
Link to post

First thing to getting intelligent help from the group is to post up a diagnostics file.   9_9    There are two ways to get this file:    'Tools'  >>>>  'Diagnostics'   which will download the file to the Download folder/directory on your PC.  If the GUI is unresponsive (as you said it was),  telnet (or SSH) in and type    diagnostics   on the command line.  That will write the file to either the root of the Flash Drive or to the logs directory.  (I can't remember which...)  You can then upload with your next post.  Obviously , it is best to get the diagnostics file after you have had problems. 

Link to post
5 hours ago, burtjr said:

I would also look at this thread

as I see your using the new AMD Ryzen. Paul and everyone else have been doing extensive testing with freezing issues and have made some headway with the problem.

Thank you for linking this thread.  I have been searching for days for other ryzen early adopters for unraid but couldn't find anything useful.  It seems (referring to page 11 of the linked thread) there are some bios options for the zen architecture regarding low power states that the linux kernal doesn't know what to do with and crashes.  Disabling those low power states seems to bring the ryzen unraid rigs to stability.

 

I will try this and post back to confirm that it worked or not.

 

 

 

20 hours ago, trurl said:

Tools - Diagnostics, post complete zip.

I'm currently at work and can't post those files in this post. But if I try the above bios changes and still continue to experience issues, I will post diagnostics files.  Otherwise I will confirm that the issue is resolved and the thread can be closed.  Thank you for your prompt replies everyone!!

Link to post
5 hours ago, derMeister said:

 

No, it seems your issue is different from mine.  According to your post it will take 30+ seconds for the page to respond.  Mine wouldn't respond at all, and eventually time out.  This was happening on multiple computers (with or without antivirus) and every browser under the sun.

However, referring back to my earlier post, my issue seems to be resolved after disabling Global C-state Control in the bios.  This is a known workaround for ryzen instability issues with unraid.

This thread can be closed as I'm pretty sure my issue is resolved.  Kind of early to tell for sure, but approaching 24 hours of up time which is a first for this server. Thanks for the help guys.

Link to post

If this solves your problem, could you please provide a link to the post in the Ryzen thread that details what you had to do to correct your issues.  Doing this will be a big help to anyone else who runs into the same problem and finds this thread. 

Link to post

I am not running a Ryzen processor but experiencing the same thing. Im am using an AMD 7860K. I pulled the Log file from the Krusader app  and copied the part that keeps repeating.

Thanks in advance

System diagnostics are attached as well.

 


Fatal server error:
Couldn't add screen


Backtrace:
0: X11rdp (0x400000+0x1801f) [0x41801f]
1: X11rdp (0x400000+0xcf39) [0x40cf39]
2: /lib/x86_64-linux-gnu/libc.so.6 (0x2b334ef49000+0x36d40) [0x2b334ef7fd40]
3: X11rdp (0x400000+0xd390) [0x40d390]
4: X11rdp (0x400000+0x151e3) [0x4151e3]
5: X11rdp (0x400000+0x15655) [0x415655]
6: X11rdp (0x400000+0x6a0aa) [0x46a0aa]
7: X11rdp (0x400000+0x8536) [0x408536]
8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x2b334ef6aec5]
9: X11rdp (0x400000+0x899e) [0x40899e]
Segmentation fault at address (nil)

FatalError re-entered, aborting
Caught signal 11 (Segmentation fault). Server aborting

Error: Can't open display: :1
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
InitOutput:

X11rdp, an X server for xrdp
Version 0.9.0
Copyright (C) 2005-2015 Jay Sorg
See http://www.xrdp.org for information on xrdp.
Underlying X server release 10903000, The X.Org Foundation
Screen width 1420 height 720 depth 16 bpp 16
dpix 100 dpiy 100
buffer size 2044800
rdpup_init: g_tcp_local_bind failed
rdpScreenInit: rdpup_init failed
pRRScrPriv 0x7efca0
rdpScreenInit: ret 0

Fatal server error:
Couldn't add screen


Backtrace:
0: X11rdp (0x400000+0x1801f) [0x41801f]
1: X11rdp (0x400000+0xcf39) [0x40cf39]
2: /lib/x86_64-linux-gnu/libc.so.6 (0x2b6df60b1000+0x36d40) [0x2b6df60e7d40]
3: X11rdp (0x400000+0xd390) [0x40d390]
4: X11rdp (0x400000+0x151e3) [0x4151e3]
5: X11rdp (0x400000+0x15655) [0x415655]
6: X11rdp (0x400000+0x6a0aa) [0x46a0aa]
7: X11rdp (0x400000+0x8536) [0x408536]
8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x2b6df60d2ec5]
9: X11rdp (0x400000+0x899e) [0x40899e]
Segmentation fault at address (nil)

FatalError re-entered, aborting
Caught signal 11 (Segmentation fault). Server aborting

Error: Can't open display: :1
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
InitOutput:

X11rdp, an X server for xrdp
Version 0.9.0
Copyright (C) 2005-2015 Jay Sorg
See http://www.xrdp.org for information on xrdp.
Underlying X server release 10903000, The X.Org Foundation
Screen width 1420 height 720 depth 16 bpp 16
dpix 100 dpiy 100
buffer size 2044800
rdpup_init: g_tcp_local_bind failed
rdpScreenInit: rdpup_init failed
pRRScrPriv 0x7efca0
rdpScreenInit: ret 0

 

tower-diagnostics-20170420-1714.zip

Edited by shanelovell
added diagnostics
Link to post

@shanelovell, I would suggest that you copy your post and paste that text (with your diagnostics file) into a new thread on this sub-forum.  The reason being that these types of problems often have different causes and solutions and, in addition, the real gurus will already be skipping over this thread since the OP's problem has been solved. 

 

 

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.