emby trying to serve an old .ts to a device that is no longer connected

[mastrmind11 722]

I noticed a strange phnomenon happening as of a couple days ago and I'm not sure how to remedy it.  Emby appears to be trying to serve a .ts file from a live tv session that no longer exists to a device (Nvidia Shield) that is no longer connected.  While it's not the the hugest of deals, I'm not a fan of seing the churn on a server that should presumably be idle.  I have restarted the box, restarted emby, reinstalled the emby container, but each time it picks up where it left off.  I would really prefer to not have to do db surgery but if that's what would fix it, so be it.  This is emby server docker latest.   Logs from latest restart attached.  Thanks

embyserver.txt

Edited May 8, 2021 by mastrmind11

[Q-Droid 989]

Have you figured out what 10.0.1.146 is on your network? Whatever device that is it keeps asking for a stream. If it's the Shield then try unplugging it.

User-Agent=Emby/1.7.54g (Linux;Android 9) ExoPlayerLib/2.10.2

2021-05-08 12:06:09.250 Info Server: http/1.1 GET http://10.0.1.152:8096/emby/videos/1869326/hls/F7ADFB/F7ADFB_1004.ts. Connection=Keep-Alive, Accept-Encoding=identity, Host=10.0.1.152:8096, User-Agent=Emby/1.7.54g (Linux;Android 9) ExoPlayerLib/2.10.2
2021-05-08 12:06:09.252 Info Server: http/1.1 Response 404 to 10.0.1.146. Time: 2ms. http://10.0.1.152:8096/emby/videos/1869326/hls/F7ADFB/F7ADFB_1004.ts
 

 

 

 

[mastrmind11 722]

1 hour ago, Q-Droid said:

Have you figured out what 10.0.1.146 is on your network? Whatever device that is it keeps asking for a stream. If it's the Shield then try unplugging it.

User-Agent=Emby/1.7.54g (Linux;Android 9) ExoPlayerLib/2.10.2

2021-05-08 12:06:09.250 Info Server: http/1.1 GET http://10.0.1.152:8096/emby/videos/1869326/hls/F7ADFB/F7ADFB_1004.ts. Connection=Keep-Alive, Accept-Encoding=identity, Host=10.0.1.152:8096, User-Agent=Emby/1.7.54g (Linux;Android 9) ExoPlayerLib/2.10.2
2021-05-08 12:06:09.252 Info Server: http/1.1 Response 404 to 10.0.1.146. Time: 2ms. http://10.0.1.152:8096/emby/videos/1869326/hls/F7ADFB/F7ADFB_1004.ts
 

 

 

 

yeah its the shield in the master bedroom, but it's not powered on.  i'll try unplugging it anyway, maybe theres some weird passive connection?  It just seems weird that it would respond 404 if it were actually actively requesting the stream.

 

edit:  unplugging the shield fixed it, just seems weird since the device itself was asleep and emby dashboard showed no devices connected.   thanks for the suggestion.

Edited May 8, 2021 by mastrmind11

[Q-Droid 989]

It sounds like the Shield wigged out and needed a power cycle. That's also a pretty old version of the app. Do you have updates disabled?

 

[mastrmind11 722]

Not sure if updates are disabled though it sounds like they are?  I rarely use it for anything but background noise at night and rarely use it for that. I'll give the app update a try. I've been trying to figure out why cpu usage stays elevated after it goes to sleep for a few months now. I generally just restart the server container to kill it but maybe it's just old app code. Cheers dude

[Luke 42079]

Let us know how you get on. Thanks.