Bug #4438

service instance is bad, reason: No input detected

Added by Ricardo Rocha 2 months ago. Updated about 1 month ago.

Status:FixedStart date:2017-06-18
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:SAT>IP
Target version:-
Found in version:HTS Tvheadend 4.3-243~gb7fbffb Affected Versions:

Description

2017-06-18 18:37:27.368 subscription: 04EA: service instance is bad, reason: No input detected
2017-06-18 18:37:27.368 mpegts: 722MHz in DVB-T - open PID 0101 (257) failed, dupe sub (owner 0x556c410eb2e0)
2017-06-18 18:37:27.368 mpegts: 722MHz in DVB-T - open PID 1001 (4097) failed, dupe sub (owner 0x556c410eb2e0)
2017-06-18 18:37:27.368 mpegts: 722MHz in DVB-T - open PID 1002 (4098) failed, dupe sub (owner 0x556c410eb2e0)
2017-06-18 18:37:27.368 mpegts: 722MHz in DVB-T - open PID 1004 (4100) failed, dupe sub (owner 0x556c410eb2e0)

today i am getting tons of those is this normal or a bug?

every time that happens all the streams that are comming from the minisatip stop and stay that way for a while...

Associated revisions

Revision 14bd7eb6
Added by Jaroslav Kysela about 1 month ago

subscription: call correctly service stop when instance is bad, fixes #4438

Revision a5f74b60
Added by Jaroslav Kysela about 1 month ago

subscription: call correctly service stop when instance is bad, fixes #4438

History

#1 Updated by Jaroslav Kysela about 1 month ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

#2 Updated by Jaroslav Kysela about 1 month ago

Fixed in v4.3-245-g14bd7eb (dupe sub), but the real culprit was not probably solved (No input detected). Do you use latest minisatip? I've seen issues with minisatip 0.5 (wrong communication). If you like to analyze tvh communication with minisatip, upload '--trace satip,httpc' logs. https://tvheadend.org/projects/tvheadend/wiki/Traces

Also available in: Atom PDF