At random moments when I am working on the WebGUI it suddenly becomes unresponsive. By simply waiting a few minutes it automatically comes back by continuing to refresh the page. Often I do not immediately notice when this happens, only when I try to perform an action or want to go to another page, then ones in a while it does not want to respond anymore. Everything except the WebGUI continues to function normally, docker containers, ssh, smb, etc.

 

I have been experiencing this for a few days now. A server restart makes no difference. It has also happened without starting the array.

 

Edited November 25, 20241 yr by PokéDax

Would be worthwhile to reseat the cabling to disk 6 & disk 4 -> they keep resetting off and on

@Squid Thanks for the reply, I reseated disk 6 and disk 4.

Could you let me know where you noticed this in the logs so I can verify if this issue occurs more frequently?

WebGUI was again unresponsive for about 5 minutes before I was able to connect to it again.

 

Edited December 11, 20241 yr by PokéDax

1 hour ago, PokéDax said:

WebGUI was again unresponsive for about 5 minutes before I was able to connect to it again.

 

At what time roughly?

 

1 hour ago, PokéDax said:

where you noticed this in the logs

Nov 21 02:46:34 ScorpionClaw kernel: sd 6:0:6:0: attempting task abort!scmd(0x0000000001303621), outstanding for 7027 ms & timeout 7000 ms
Nov 21 02:46:34 ScorpionClaw kernel: sd 6:0:6:0: [sdi] tag#8877 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00
Nov 21 02:46:34 ScorpionClaw kernel: scsi target6:0:6: handle(0x0010), sas_address(0x500056b35aa732c6), phy(6)
Nov 21 02:46:34 ScorpionClaw kernel: scsi target6:0:6: enclosure logical id(0x500056b31234abff), slot(6) 
Nov 21 02:46:34 ScorpionClaw kernel: scsi target6:0:6: enclosure level(0x0001), connector name(     )
Nov 21 02:46:34 ScorpionClaw kernel: sd 6:0:6:0: device_block, handle(0x0010)
Nov 21 02:46:36 ScorpionClaw kernel: sd 6:0:6:0: task abort: SUCCESS scmd(0x0000000001303621)
Nov 21 02:46:36 ScorpionClaw kernel: sd 6:0:6:0: device_unblock and setting to running, handle(0x0010)
Nov 21 02:46:36 ScorpionClaw emhttpd: read SMART /dev/sdi
Nov 21 02:46:38 ScorpionClaw emhttpd: spinning down /dev/sdc
Nov 21 02:47:03 ScorpionClaw kernel: sd 6:0:7:0: attempting task abort!scmd(0x0000000050a47542), outstanding for 7048 ms & timeout 7000 ms
Nov 21 02:47:03 ScorpionClaw kernel: sd 6:0:7:0: [sdj] tag#8887 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00
Nov 21 02:47:03 ScorpionClaw kernel: scsi target6:0:7: handle(0x0011), sas_address(0x500056b35aa732c7), phy(7)
Nov 21 02:47:03 ScorpionClaw kernel: scsi target6:0:7: enclosure logical id(0x500056b31234abff), slot(7) 
Nov 21 02:47:03 ScorpionClaw kernel: scsi target6:0:7: enclosure level(0x0001), connector name(     )
Nov 21 02:47:03 ScorpionClaw kernel: sd 6:0:7:0: device_block, handle(0x0011)
Nov 21 02:47:05 ScorpionClaw kernel: sd 6:0:7:0: task abort: SUCCESS scmd(0x0000000050a47542)
Nov 21 02:47:05 ScorpionClaw kernel: sd 6:0:7:0: device_unblock and setting to running, handle(0x0011)

 

On 11/23/2024 at 5:20 PM, Squid said:

At what time roughly?

I created a new diagnostics right after became available again, so about 5 to 6 minutes ago.

After installing the latest stable update 6.12.14 that became available to me last night, I am still experiencing the issue.

 

I discovered something else! When I can't access the WebGUI on one computer, I can still reach it from another device without any problems. The server itself remains fully operational and accessible across all devices, ping works fine, as do other container web ports. The issue seems to only affect the Unraid WebGUI on the initial device for a certain period.

This specific occurrence happened while I was editing a script using the User Scripts plugin. After saving the script, the webpage reloaded as expected, and everything seemed fine initially. However, when I attempted to perform another action, nothing responded. Upon refreshing the page to check, the WebGUI failed to load entirely.

 

Has anyone else experienced similar behavior, or does anyone know what might cause this selective unavailability of the WebGUI for a specific session?

Edited November 29, 20241 yr by PokéDax

On 11/29/2024 at 7:50 AM, PokéDax said:

When I can't access the WebGUI on one computer, I can still reach it from another device without any problems.

Try a different browser on the problem computer.

Thanks for the response, I have already tried it, unfortunately it does not work. Deleting the cache does not work either. I do not think it is the computer. If I use another device, such as a laptop, tablet, etc, it also happens. The first device I am working on at that moment and perform certain actions, at a certain point the WebGUI no longer accessible for x number of minutes.