sd getting hammered

techpro2004 · 2025-01-14, 07:45 PM

Apparently Schedules direct is getting hammered with requests as they put a 24 hr hold on my account. I do not use jellyfin. the only thing connecting to sd should be 2 instances of npvr on separate machines, on the same lan. I just updated from the November build to the current one so I am not sure in which the problem lies. Any help would be apprecieated. I just filed a ticket with sd. logs attached.

techpro2004 · 2025-01-14, 07:47 PM

I also just heard from sd that my lineup has been deleted so maybe that has to do with something?

mvallevand · 2025-01-14, 08:31 PM

Your account started failing in November before the Jellyfin ban so yes look for something else. SD should have sent you an email about lineups being pulled.

Martin

***sub*** · 2025-01-14, 09:47 PM

How many SD lineups do you have on your Settings->Guide page?

techpro2004 · 2025-01-14, 09:48 PM

The only thing I did in November sd wise was update npvr. I just got the email today that said my lineup was deleted. It has to be a bug with having 2 npvr servers up and running 24/7 that was introduced with the November update. thanks.

techpro2004 · (This post was last modified: 2025-01-14, 09:53 PM by techpro2004.)

currently it only shows "DVB/ATSC EPG" normally I also have one for directv stream but that is not showing up.

edit: keep in mind I have 2 systems running npvr.

mvallevand · 2025-01-14, 09:58 PM

Unless you have v4 running it isn't an issue, as I said these logs don't show a connection in Nov.

Did you add a VPN?

Martin

***sub*** · 2025-01-14, 10:04 PM

Quote:the only thing connecting to sd should be 2 instances of npvr on separate machines, on the same lan

Are the using separate SD accounts? I seem to remember there some weird SD scheme, where if you're use a valid token from one machine, and then get a new token from another machine, it invalidates the other one.

mvallevand · (This post was last modified: 2025-01-14, 10:32 PM by mvallevand.)

I run 4 on on SD account and 1 on another. Definitely scheduling both updates at the same time is a no-no it will generate a lot of these on each machine

2024-12-11 02:45:05.573 [ERROR][85] Invalid token. Will get new token...

But that can also come from the VPN or from Internet provders that change external addresses.

If you have a fixed WAN IP (at least for the day) fix the lineup and change the EPG update time on one machine by an hour and see if things improve.

Martin

***sub*** · 2025-01-15, 12:42 AM

I did end up fixing one possible cause, for the case your token might have been invalidated (for whatever external reason), while the EPG update was already underway, and it not manages to recover until that chunk of EPG channels finished (unsuccessfully).