Sage keeps finding 42 tuners, most don't exist?

[btrcp2000]

Had to switch TV providers forcing me to go back to Colossus 2 cards hosted by a Win10 VM inside UNRAID (sage via docker). Forgot how much fun these were.

Lots of problems, but the one making it most difficult right now is that Sage continues to find tuners that were long removed from the properties file and aren't even in my house anymore. There should be 8 (4 HDHR Quatro via OpenDCT, 2 r5000HD and 2 Colossus2 cards via networked Sage instance on the win10 VM). Sage finds no fewer than 42, many of which are connected to an old HDHR Dual that hasn't been plugged in for a year, and a HDHR Connect that went back to Best Buy). Even after shutting down both docker and the networked sage instance, and painstakingly deleting all but the real tuners from properties of both, they all come back upon restart. Some reference a domain from a VM that hasn't been booted in over a year.

Where is it finding these old data points to treat as tuners? How do I eliminate them permanently so I can know which ones to work on?

[btrcp2000]

No one else has seen this? I don;t understand where it could be finding all these extra tuners if they've been removed from PROPERTIES of both the docker instance as well as the networked encoder. Could it be finding them in the backup file? I didn't think that would matter since the properties file is otherwise intact, why would it bother with the backup. Is there a log somewhere else that it references, maybe from the router or something? There's is nothing physically out there that could be reporting the existence of most of these things

[btrcp2000]

Saw something that sheds a little more light, although it still doesn't make sense. I have just setup a Server 2012 VM on UNRAID to deal with hauppauge tuners. In the process of setting up sage as a networked encoder, the docker began finding the COlossus tuners that looked like this:

NeighborKidsiPhone.localdomain:6969

Neighbor kid moved two years ago and hasn't been in the house in months, so this has to be coming from my Unifi router seeing stuff coming in on IPs or ports or whatever that it has used before, and just using the old label.

HDHomerun-HDTC-2US Tuner 1058AD96 on unifi:9000

This tuner went back to the store months ago.

Plenty of others, but is this something like UPNP discovering things over and over again? The way these things read, it seems like there are several unique "discoverers" out there finding things and reporting them as tuners to Sagetv, with many being discovered multiple times by different sources.

Or I have no idea what I'm talking about. Thoughts?

[KryptoNyte]

Yes, I see this all the time on an aging SageTV server. Tuners that I retired 5 or 6 years ago still show up when going into the properties file, and even after deleting them from the properties file, they magically reappear. I assumed these tuners were permanently buried somewhere in the operating system registry upon their first discovery.

[btrcp2000]

haven't done it yet, but my next attempt was going to be to shut down both sage instances, clean up the props files, then delete the backups as well. Maybe it pulls them from there. I'm up to 50 now.

[KryptoNyte]

50... wow.

Just to be clear, every tuner that I've seen in the properties file is one that I did actually own and use at one time. There aren't any ghost tuners in there that I'm aware of.

[wnjj]

They are most likely in the registry. I know that was causing issues with hanging on some systems when no longer installed cards were still being “pinged” by directshow.

[btrcp2000]

Just following up on this in case someone else runs across it. I'm now down to 12 tuners. In reality, I have 6 active (2 Colossus, 4 from a single HDHR Quatro via OpenDCT). There are also two r5000 tuners I have disabled but left in properties in case I want them again, and the 4 Quatro tuners broadcasting themselves outside OpenDCT. I'm guessing that last part doesn't hurt anything, so I'm leaving it alone. The answer was that I had 3 sources seeking networked encoders between the Sage docker, OpenDCT docker, and a networked instance of Sage on a WinServer 2012 R2 VM that hosts the Colossus cards. Each of these was finding each other's tuners and presenting them as available to the Sage docker, which was also discovering on its own. Solution weas to edit properties for each instance and turn off discovery (except the sage docker), and tell them what tuners to ignore.

I cannot figure out the NeighborKidiPhone thing, but I know where it's coming from. Last Halloween, NeighborKid visited and used our wifi. Per the router logs, the Unifi router at some point used the same IP address he was assigned that day for the VM when I set it up. The unifi router makes no mention of NeighborKidiPhone as a hostname, it shows the VM as I would expect. I only find it deep in the logs, so sage picked it up somewhere else. This VM did not exist a month ago, so it cant be from the registry file. In any case, it doesn't seem to affect functionality, just weird to see.