Login at Kodi Home

Meindert · (This post was last modified: 2015-05-14, 10:17 by Meindert.)

My system is debian testing with the Kodi 15.0 Isengard – Beta 1 and tvh addon version 2.1.8

17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 3
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 2
17:48:29 T:139850886903552 DEBUG: Previous line repeats 5 times.
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 3
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 1
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 3
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 1
17:48:29 T:139850886903552 DEBUG: Previous line repeats 1 times.
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 3
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 1
17:48:29 T:139850886903552 DEBUG: Previous line repeats 4 times.
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 3
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 1
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 3
17:48:29 T:139850886903552 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Dropped packet with unknown stream index 1

**negge** · 2015-05-12, 18:31

Please post the full log to xbmclogs.com and link it here.

Meindert · 2015-05-12, 20:33

It can be that I'm using an unsupported version as you mentioned in another thread (http://forum.kodi.tv/showthread.php?tid=225980), does this mean that issues based on that are also unsupported Smile

Sorry I'm strugling with getting the log into xbmclogs.com, I can't find an upload posibility.

I can't reproduce the same as above, but now I don't get a signal at all on some channels. Recordings on those particular channels is no problem.

I got the following message in the log file:
19:49:10 T:139785448437504 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - demux read nothing
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [signalStatus]
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signalStatus:
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - status : GOOD
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - snr : 114
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - ber : 0
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - unc : 0
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signal : 48424
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [timeshiftStatus]
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - timeshiftStatus:
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - full : 0
19:49:11 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - shift : 0
19:49:11 T:139785448437504 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - demux read nothing
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [signalStatus]
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signalStatus:
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - status : GOOD
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - snr : 115
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - ber : 0
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - unc : 0
19:49:12 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signal : 48424
19:49:12 T:139785448437504 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - demux read nothing
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [signalStatus]
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signalStatus:
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - status : GOOD
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - snr : 113
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - ber : 0
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - unc : 0
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signal : 48424
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [dvrEntryUpdate]
19:49:13 T:139785440044800 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - sending message [getDiskSpace : 50]
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - received response [50]
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [timeshiftStatus]
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - timeshiftStatus:
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - full : 0
19:49:13 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - shift : 0
19:49:13 T:139785448437504 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - demux read nothing
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - receive message [signalStatus]
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signalStatus:
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - status : GOOD
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - snr : 114
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - ber : 0
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - unc : 0
19:49:14 T:139786055272192 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - signal : 48524
19:49:14 T:139785448437504 DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - demux read nothing

**Prof Yaffle** · (This post was last modified: 2015-05-12, 20:41 by Prof Yaffle.)

Use cut-and-paste to get the whole log... they're called paste sites for a reason ;-)

EDIT

Or, since you're on Debian, you'll probably have pastebinit installed:

cat <file> | pastebinit

==> uploads it and gives you the link.

Meindert · 2015-05-12, 20:56

cat $HOME/.kodi/temp/kodi.log | pastebinit
results in: http://paste.debian.net/
Don't find the informatiob there

cat $HOME/.kodi/temp/kodi.log | pastebinit -b http://pastebin.com/
results in: Bad API request, invalid api_dev_key
I can't find the option to provide my api_dev_key

wc $HOME/.kodi/temp/kodi.log
results in: 29452 436951 3388808 $HOME/.kodi/temp/kodi.log
Not easy to copy/paste

**negge** · 2015-05-14, 10:59

Try sprunge.us.

Meindert · 2015-05-14, 12:28

At the moment can't reproduce the issue, all seems to work fine with kodi + addon from deb-multimedia/experimental

Meindert · 2015-05-14, 12:34

Hereby a previous log: http://sprunge.us/ODYN

In de log are at particular channels "demux read nothing" messages

As described above, could not reproduce this today

Meindert · 2015-05-14, 18:16

The sound is OK in the situation that the picture freeze

**negge** · 2015-05-15, 13:57

Demux read nothing shouldn't be a problem, it happens when the tuner takes longer than expected to start producing data. It's the "dropped packet with unknown" I'm interested in mostly.

Meindert · 2015-05-15, 15:30

It seems that at tvheadend server site is some activity conserning issues on descrambling, i have no idea if this has to do with my issue!?

If I can help, please tell me.

**negge** · 2015-05-15, 17:29

I doubt that's related to the issue.

mhoogenbosch · (This post was last modified: 2015-06-04, 23:39 by mhoogenbosch.)

Got the same crash. Have been experiencing this for a while now but since it only happens once a week at maximum i didn't give it much attention. Now i have enabled debugging and gathered the logs:

http://sprunge.us/habO

This is with openelec 5, so kodi 14.2

**negge** · 2015-06-05, 01:09

Doesn't look like a crash to me, just a standard exit:

Quote:23:30:17 T:140063238825728 INFO: Received SIGTERM...

The addon could definitely react to the OnQuit announcement and cancel all subscriptions, that way the log wouldn't get spammed.

mhoogenbosch · 2015-06-05, 10:51

(2015-06-05, 01:09)negge Wrote: Doesn't look like a crash to me, just a standard exit:

Quote:23:30:17 T:140063238825728 INFO: Received SIGTERM...

The addon could definitely react to the OnQuit announcement and cancel all subscriptions, that way the log wouldn't get spammed.

yes I forecebly rebooted the machine because the image was frozen. I still could connect with SSH. After the reboot i uploaded the kodi.log.old to pastebin.

Is there a better way to upload the logs? Or does this answer give a different perspective?