Jump to content
sombersalt

Page Unresponsive

11 posts in this topic Last Reply

Recommended Posts

This started before and continued after I upgraded to 6.6.6. It takes about a minute to become responsive after any action is selected. Initially, it seemed to be associated with the unassigned devices but having removed that device I still get to wait a minute between actions. Any thoughts? 

image.thumb.png.2fb052144aaee53f8c9c8ef55b30eddf.png

 

Thanks in advance,

Ken

Share this post


Link to post

Hard to say without you grabbing the diagnostics

Share this post


Link to post

Hello, I have the same issue for about a week now.

 

The problem only occurred on Chrome for me (Firefox worked fine). Today, I installed another browser (Vivaldi) and the problem was present there as well, so I looked here to find if someone has the same issue.

 

Seeing as you use Chrome as well I was about to write that it seems to be a Chrome problem. But before that, I tried with a private session of the browser (without extensions) and voila, the UI was responsive again.

 

So I compared out extensions and we only had one in common, Grammarly! After removing it from Vivaldi the UI became responsive again! Would be cool if someone could figure out what the problem is.

Share this post


Link to post
10 hours ago, sombersalt said:

Probably this

Jan 11 11:41:40 Tower emhttpd: shcmd (401): /usr/local/sbin/mover &> /dev/null &
Jan 11 11:42:18 Tower kernel: dotnet[24934]: segfault at 0 ip 000015543e343c00 sp 00001553c1f37398 error 4 in libc-2.27.so[15543e2cd000+1b3000]
Jan 11 11:42:18 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:43:21 Tower kernel: dotnet[29865]: segfault at 0 ip 0000145a122b6c00 sp 0000145995ca9398 error 4 in libc-2.27.so[145a12240000+1b3000]
Jan 11 11:43:21 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:43:44 Tower autofan: Highest disk temp is 89F, adjusting fan speed from: 25 (9% @ 1472rpm) to: OFF (0% @ 1493rpm)
Jan 11 11:44:25 Tower kernel: dotnet[2640]: segfault at 0 ip 000014678468dc00 sp 00001466e39f7398 error 4 in libc-2.27.so[146784617000+1b3000]
Jan 11 11:44:25 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:45:28 Tower kernel: dotnet[7630]: segfault at 0 ip 0000149c55276c00 sp 0000149bb3588398 error 4 in libc-2.27.so[149c55200000+1b3000]
Jan 11 11:45:28 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:46:32 Tower kernel: dotnet[12352]: segfault at 0 ip 0000153ccaff8c00 sp 0000153c2a605398 error 4 in libc-2.27.so[153ccaf82000+1b3000]
Jan 11 11:46:32 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:47:35 Tower kernel: dotnet[17359]: segfault at 0 ip 0000147916045c00 sp 000014789a34c398 error 4 in libc-2.27.so[147915fcf000+1b3000]
Jan 11 11:47:35 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:48:39 Tower kernel: dotnet[22084]: segfault at 0 ip 0000149237630c00 sp 0000149197870398 error 4 in libc-2.27.so[1492375ba000+1b3000]

Continues on and on and on

 

I would start by running MemTest from the boot menu for minimum 1 pass (ideally more) and go from there.

Share this post


Link to post
9 hours ago, Squid said:

Probably this


Jan 11 11:41:40 Tower emhttpd: shcmd (401): /usr/local/sbin/mover &> /dev/null &
Jan 11 11:42:18 Tower kernel: dotnet[24934]: segfault at 0 ip 000015543e343c00 sp 00001553c1f37398 error 4 in libc-2.27.so[15543e2cd000+1b3000]
Jan 11 11:42:18 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:43:21 Tower kernel: dotnet[29865]: segfault at 0 ip 0000145a122b6c00 sp 0000145995ca9398 error 4 in libc-2.27.so[145a12240000+1b3000]
Jan 11 11:43:21 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:43:44 Tower autofan: Highest disk temp is 89F, adjusting fan speed from: 25 (9% @ 1472rpm) to: OFF (0% @ 1493rpm)
Jan 11 11:44:25 Tower kernel: dotnet[2640]: segfault at 0 ip 000014678468dc00 sp 00001466e39f7398 error 4 in libc-2.27.so[146784617000+1b3000]
Jan 11 11:44:25 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:45:28 Tower kernel: dotnet[7630]: segfault at 0 ip 0000149c55276c00 sp 0000149bb3588398 error 4 in libc-2.27.so[149c55200000+1b3000]
Jan 11 11:45:28 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:46:32 Tower kernel: dotnet[12352]: segfault at 0 ip 0000153ccaff8c00 sp 0000153c2a605398 error 4 in libc-2.27.so[153ccaf82000+1b3000]
Jan 11 11:46:32 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:47:35 Tower kernel: dotnet[17359]: segfault at 0 ip 0000147916045c00 sp 000014789a34c398 error 4 in libc-2.27.so[147915fcf000+1b3000]
Jan 11 11:47:35 Tower kernel: Code: 1f 00 c1 e8 05 83 e0 01 89 c2 89 d0 c3 0f 1f 44 00 00 c1 e8 05 41 8b 48 04 83 e0 01 89 c2 eb a4 83 c1 01 41 89 48 04 eb e1 90 <f7> 07 00 20 00 00 74 08 8b 47 70 85 c0 78 01 c3 48 8b 05 19 f2 33 
Jan 11 11:48:39 Tower kernel: dotnet[22084]: segfault at 0 ip 0000149237630c00 sp 0000149197870398 error 4 in libc-2.27.so[1492375ba000+1b3000]

Continues on and on and on

 

I would start by running MemTest from the boot menu for minimum 1 pass (ideally more) and go from there.

Is there a way to run Memtest in a headless configuration? 

Share this post


Link to post

Will need to make some time for this unless there is a way to run Memtest in a headless configuration? The slow loading  "page unresponsive" resolved by turning off the Grammarly extension.  Probably does not resolve all these errors.

Share this post


Link to post
44 minutes ago, sombersalt said:

Is there a way to run Memtest in a headless configuration? 

Yes.

 

Edit syslinux>syslinux.cfg on your flash drive and make it look like this (move "menu default" from unRAID OS section to Memtest86+):

 

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  kernel /bzimage
  append initrd=/bzroot
label unRAID OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label unRAID OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+

  menu default
  kernel /memtest

 

After editing, be sure to save and then reboot the server.

 

I have never tried to SSH/telnet into the server while running a memtest, but, that would be the only way to see what is going on as your server is headless.

Share this post


Link to post
3 hours ago, Hoopster said:

I have never tried to SSH/telnet into the server while running a memtest, but, that would be the only way to see what is going on as your server is headless.

I don't think memtest exposes a remote connection of any sort, so you would have to have a local console to see the results. Either physical monitor or IPMI.

Share this post


Link to post
15 hours ago, jonathanm said:
I don't think memtest exposes a remote connection of any sort, so you would have to have a local console to see the results. Either physical monitor or IPMI.


Yeah, I did not know if it did or not. Looks like he needs a monitor. My servers have either a monitor or IPMI.


Sent from my iPhone using Tapatalk

Edited by Hoopster

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now