Unsafe.park - spinning circles

[wnjj]

Originally Posted by wnjj

Have those of you with these issues tried the setting in this post? https://forums.sagetv.com/forums/sho...2&postcount=15

ui/load_images_with_awt_toolkit=false

Anyone try this?

[graywolf]

Originally Posted by wnjj

Anyone try this?

I'll give this a try and see if it decreases the spinning circles.
For the HD300, would it just be Sage.properties or would it also be the HD300 properties in the client folder? What about SageClient.properties?

Sage.properties & SageClient.properties has it true.
The client\<macaddress>.properties does not have the line at all

Guess I'll add to the client\<macaddress>.properties and make both Sage.properties & SageClient.properties as false

[graywolf]

Originally Posted by NetworkGuy

No. I also ran CrystalDiskInfo on my hard-drives and they are fine.

https://crystalmark.info/en/software/crystaldiskinfo/

My SSD shows as 100% Good
My HDD shows as Good.

[NetworkGuy]

Interesting Update.

I have a Netgear MR60 / MS60 WiFi 6 Mesh system. I was working with their Tier 2 support yesterday on a possible firmware bug with port forwarding. Support had me reset my router to factory defaults and then reconfigured it. While I was doing this, I powered off the satellite and forgot to turn it back on. (It did seem to clear the port forwarding problem.)

Here is the interesting part. Last night there were no spinning circles. I am going to power up the satellite today and see what happens.

[graywolf]

With ui/load_images_with_awt_toolkit=false

Log attached

Fri 3/27 8:43:56.814 [AWTThreadWatcher-0023a500012e@60d5efd2] EventThread-0023a500012e Hang Detected - hang time = 5266 UILocker=Thread[EventRouter-0023a500012e,5,main]

Then shows the thread dump info

Hope that helps in someone able to point me in the right direction

[sic0048]

Originally Posted by tvmaster2

Does your system lockup to the point of needing a Task Manager Kill Process of SageTV at that point? That’s what my spinning circles lead to.

I use clients to access my SageTV system, so my experience is coming from this use only.

When the spinning circle appears, it certainly freezes the clients (HD-300s or Shields) and they do not respond to any type of input, remote button presses, etc. However, if I wait long enough, the system will recover and allow me to move on. Usually this wait time can be measured in minutes however.

Many times I will get tired of waiting and power cycle the HD-300. When it comes back and reconnects, I do have normal use of the system. Many times doing this is actually quicker than waiting for the spinning circle.

Again, I am 100% convinced MY problem is related to corrupt files (likely due to a hard drive issues). I say this because the system will work fine unless I navigate to where those suspected corrupt shows are. It is a repeatable event. So anytime I navigate to a suspected corrupted show, I get a spinning circle. If I stay away from the suspected corrupted shows the system works fine.

I realize this isn't the only reason people see the spinning circle and it may not be your issue.

[SHS]

Originally Posted by sic0048

I use clients to access my SageTV system, so my experience is coming from this use only.

When the spinning circle appears, it certainly freezes the clients (HD-300s or Shields) and they do not respond to any type of input, remote button presses, etc. However, if I wait long enough, the system will recover and allow me to move on. Usually this wait time can be measured in minutes however.

Many times I will get tired of waiting and power cycle the HD-300. When it comes back and reconnects, I do have normal use of the system. Many times doing this is actually quicker than waiting for the spinning circle.

Again, I am 100% convinced MY problem is related to corrupt files (likely due to a hard drive issues). I say this because the system will work fine unless I navigate to where those suspected corrupt shows are. It is a repeatable event. So anytime I navigate to a suspected corrupted show, I get a spinning circle. If I stay away from the suspected corrupted shows the system works fine.

I realize this isn't the only reason people see the spinning circle and it may not be your issue.

Install CrystalDiskInfo

[wnjj]

Originally Posted by graywolf

I'll give this a try and see if it decreases the spinning circles.
For the HD300, would it just be Sage.properties or would it also be the HD300 properties in the client folder? What about SageClient.properties?

Sage.properties & SageClient.properties has it true.
The client\<macaddress>.properties does not have the line at all

Guess I'll add to the client\<macaddress>.properties and make both Sage.properties & SageClient.properties as false

Sage.properties is for the server in application mode and for all miniclients (like the HD300). Rendering for those is done on the server. Sageclient.proeprties is for a client on a PC (including the server if using service mode).

When I changed it in my sage.properties I noticed a distinct increase in performance and stopped getting all of the blank images I used to get when browsing photos on the HD300.

[wnjj]

Originally Posted by graywolf

With ui/load_images_with_awt_toolkit=false

Log attached

Fri 3/27 8:43:56.814 [AWTThreadWatcher-0023a500012e@60d5efd2] EventThread-0023a500012e Hang Detected - hang time = 5266 UILocker=Thread[EventRouter-0023a500012e,5,main]

Then shows the thread dump info

Hope that helps in someone able to point me in the right direction

Those thread dumps are helpful. After each “Thread[“ the next set of line shown are the code where the thread is at with the top being the most recent. Most of them are at wait, run, socketlisten, etc. which is normal but one that stood out is:

Fri 3/27 8:43:56.826 [AWTThreadWatcher-0023a500012e@60d5efd2] Thread[Seeker,5,main]
Fri 3/27 8:43:56.826 [AWTThreadWatcher-0023a500012e@60d5efd2] 	java.io.WinNTFileSystem.getBooleanAttributes(Native Method)

It’s the “verify files” thread checking for file existence. It could be a coincidence that this activity happens often enough that it may always show up, or it could indicate a bad file or bad disk.

[sic0048]

Originally Posted by SHS

Install CrystalDiskInfo

Thanks. I do have a bunch of "relocated sector counts" on one of my drives I save my recordings to. It just confirms my suspicion that one of them was going bad. At least now I know which one.

[graywolf]

Originally Posted by wnjj

Most of them are at wait, run, socketlisten, etc. which is normal but one that stood out is:

Fri 3/27 8:43:56.826 [AWTThreadWatcher-0023a500012e@60d5efd2] Thread[Seeker,5,main]
Fri 3/27 8:43:56.826 [AWTThreadWatcher-0023a500012e@60d5efd2] 	java.io.WinNTFileSystem.getBooleanAttributes(Native Method)

It’s the “verify files” thread checking for file existence. It could be a coincidence that this activity happens often enough that it may always show up, or it could indicate a bad file or bad disk.

How would I figure out which file it is checking for?
Is it the recording (mpg) file it is checking for? in which case it is having to reach out to the NAS, or is it a SageTV file which would then be on the PC's SSD.

[wnjj]

Originally Posted by graywolf

How would I figure out which file it is checking for?
Is it the recording (mpg) file it is checking for? in which case it is having to reach out to the NAS, or is it a SageTV file which would then be on the PC's SSD.

Yeah. "verifyFiles" is a process that scans for recording files as part of the disk space check. You would see something like this in the log file when it starts:

Verifying existence of all TV media files in database

For the code types, verifyFiles is in Seeker.Java.

Again, this may not be the issue since file scanning tends to run a lot. It just means that something what wasn't idle during the hang. There are other things and I'm taking a closer look now that I'm not on a tablet.

[wnjj]

Originally Posted by graywolf

With ui/load_images_with_awt_toolkit=false

Log attached

Fri 3/27 8:43:56.814 [AWTThreadWatcher-0023a500012e@60d5efd2] EventThread-0023a500012e Hang Detected - hang time = 5266 UILocker=Thread[EventRouter-0023a500012e,5,main]

Then shows the thread dump info

Hope that helps in someone able to point me in the right direction

Actually, right before a different hang I see this:

Fri 3/27 8:44:21.938 [EventRouter-0023a500012e@1459bddd] Seeker.finishWatch(UIManager:localhost@@0023a500012e-2ca8a20e)

Then during the dumped threads is this;

Fri 3/27 8:44:27.642 [AWTThreadWatcher-0023a500012e@60d5efd2] Thread[EventRouter-0023a500012e,5,main]
Fri 3/27 8:44:27.642 [AWTThreadWatcher-0023a500012e@60d5efd2] 	sage.Seeker.finishWatch(Seeker.java:4934)

Did you just complete watching a recording when it hung that time?

After further review, I think the only thing in common on the various hangs is the verifyfiles process.

[NetworkGuy]

Originally Posted by NetworkGuy

Interesting Update.

I have a Netgear MR60 / MS60 WiFi 6 Mesh system. I was working with their Tier 2 support yesterday on a possible firmware bug with port forwarding. Support had me reset my router to factory defaults and then reconfigured it. While I was doing this, I powered off the satellite and forgot to turn it back on. (It did seem to clear the port forwarding problem.)

Here is the interesting part. Last night there were no spinning circles. I am going to power up the satellite today and see what happens.

I powered up my satellite and there were no spinning circles. But I have a theory on what happened. I think I accidentally created a network loop on a LAN.

Take a look at the attached simple network diagram.

SageTV server used the 3-2-1 path to get to the Internet.

While setting up the router, I removed cable 2. But SageTV server still had internet connectivity. It found a new path using 3-4-5-6-1.

When I re-attached cable 2, it found a 2nd path. It created a loop for SageTV server that caused the spinning circles.

[graywolf]

Originally Posted by wnjj

Those thread dumps are helpful. After each “Thread[“ the next set of line shown are the code where the thread is at with the top being the most recent. Most of them are at wait, run, socketlisten, etc. which is normal but one that stood out is:

Fri 3/27 8:43:56.826 [AWTThreadWatcher-0023a500012e@60d5efd2] Thread[Seeker,5,main]
Fri 3/27 8:43:56.826 [AWTThreadWatcher-0023a500012e@60d5efd2] 	java.io.WinNTFileSystem.getBooleanAttributes(Native Method)

It’s the “verify files” thread checking for file existence. It could be a coincidence that this activity happens often enough that it may always show up, or it could indicate a bad file or bad disk.

Still trying to track down spinning circles.
You mentioned another potential could be a bad file.
Any ideas how I might track/identify a potentially bad file(s)?

[BigSwifty]

In my experience as well, spinning circles are often caused by network issues. Perhaps the router, switch, NAS cable or ethernet port on one of the machines is flaky. My issue was the ethernet adapter on my file-server machine. I had already ruled-out a HD issue.

[tvmaster2]

Originally Posted by BigSwifty

In my experience as well, spinning circles are often caused by network issues. Perhaps the router, switch, NAS cable or ethernet port on one of the machines is flaky. My issue was the ethernet adapter on my file-server machine. I had already ruled-out a HD issue.

The only thing I haven’t done yet is reload my server’s network drivers, so maybe it’s time.

[NetworkGuy]

Originally Posted by BigSwifty

In my experience as well, spinning circles are often caused by network issues. Perhaps the router, switch, NAS cable or ethernet port on one of the machines is flaky. My issue was the ethernet adapter on my file-server machine. I had already ruled-out a HD issue.

I started experiencing spinning circles again after I installed a new Mesh router. I have not had time to track it down yet.

[tvmaster2]

Originally Posted by NetworkGuy

I started experiencing spinning circles again after I installed a new Mesh router. I have not had time to track it down yet.

I’m also suffering from HD300 network problems.

[NetworkGuy]

Originally Posted by tvmaster2

I’m also suffering from HD300 network problems.

My problem also happens when using the mini-client, so I am pretty sure it is server related. Also payback is not affected.

One thought, I never upgraded to the 64 bit version. During the pandemic, I downloaded and imported hundreds of old TV shows and movies. The files are spread across three drives and a couple of Gig on a NAS. I am wondering if the spinning circles are caused by the amount of files that need to scanned when browsing the directory or opening a file.