Recordings stuck as Active Recordings

[Fratopolis 62]

Well, It looks like Server 3.1.0 update fixed on my moms server by adding the feature "Preserve original video when converting recordings". I found that even though I had Emby using her tuners transcode feature her server was still converting the video while "Automatically convert recordings to a streaming friendly format" was selected even though the video was already in H.264 format.

 

Thank you so much for adding this. Been wanting it for a while now but decided not to bother you all as you are always working hard. I saw it possibly coming in the dev builds later on and it was like you knew what I was thinking.

 

Not sure why it was getting stuck in active recordings still but my issue for my mom is no longer. Unless I am speaking too soon lol.

Edited December 21, 2016 by Fratopolis

[Luke 37118]

Thanks for reporting back !

[hokey1 0]

Put me down for also having the recordings having a file size of 0 bytes.  

 

 

server.txt

[Luke 37118]

Put me down for also having the recordings having a file size of 0 bytes.  

 

Hi @@hokey1, your issue is different, although I found it by testing your url directly. It is resolved for the next release of Emby server. Thanks !

[earthtorob 5]

I wish I had more time to devote to looking at this problem.  The log files are very detailed.  I'm a novice to this software.   Anyway, I have a very similar problem.   Tv Show never drop from the active recording screen and the recordings never show up in the recording folder.  I'll attach a log file and screen shot.

 

 

server-63625305600.txt

[earthtorob 5]

Just an update.  I just recorded two back to back tv shows on the same channel with a 2 minute overlap on the start and finish.  No problems so far.  I thought that the problem might have had something to do with two streams on the same tuner at the same time. 

 

So then I ran two recordings at the same time on different tuners.  And those got stuck.

[Erik 120]

@@earthtorob

 

What does the log from the HDhomerun show?

 

For me every time I had a stuck recording in Emby, I also had a reset occur on the HDhomerun that Emby wasn't recovering from.

[earthtorob 5]

Where do I find that log?

[Luke 37118]

hi @@earthtorob, you can learn how to do that here:

 

https://emby.media/community/index.php?/topic/739-how-to-report-a-problem/

 

Thanks !

[Erik 120]

@@earthtorob

 

Use a browser to type in the IP address of the HDhomerun unit and from that menu click "system status" then "system log" that has all log details from the HDhomerun unit.

Edited March 19, 2017 by Erik

[earthtorob 5]

Not much here at all.

19700101-00:00:02 System: reset reason = power on19700101-00:00:08 System: network link 100f19700101-00:00:09 System: ip address obtained: 192.168.10.3 / 255.255.255.020170320-05:57:15 System: time changed from Thu Jan  1 00:00:24 1970 to Mon Mar 20 05:57:15 2017

[earthtorob 5]

Is everyone that is having this problem using a HDHomrun device?

[Luke 37118]

You may want to read this:

 

https://emby.media/community/index.php?/topic/43476-hdhomerun-issue/?p=432951

[Erik 120]

That log will look like that whenever the unit looses power (unplugged/power outage). I was looking for "reset reason = application watchdog" which according to the manufacturer is an internal recognized fault, usually associated with overheat protection.

 

Next time you see Emby with a stuck recording then check the log for the HDhomerun unit as well. As Luke linked to, that is the issue I had so see what the logs show and let us know on the next occurnance of a stuck recording.

 

Also just for additional info, what HDhomerun unit do you have? And how is it connected to your internal network?

Edited March 20, 2017 by Erik

[earthtorob 5]

IDK if My HDHomerun is resetting or not.   Here is the latest log.

 

19700101-00:00:02 System: reset reason = power on
19700101-00:00:08 System: network link 100f
19700101-00:00:09 System: ip address obtained: 192.168.10.3 / 255.255.255.0
20170321-08:59:09 System: time changed from Thu Jan 1 00:00:24 1970 to Tue Mar 21 08:59:09 2017

 

I did notice this though:

 

2017-03-20 19:59:00.0107 Info App: Recording timer fired.

2017-03-20 19:59:00.0263 Info HttpClient: Checking for cache file C:\Users\Robert\AppData\Roaming\Emby-Server\cache\httpclient\424b7dfea9b6ab50e233fb24cf5008c0

2017-03-20 19:59:00.0420 Info HttpClient: HttpClientManager GET: http://192.168.10.3:80/lineup.json

2017-03-20 19:59:00.0576 Info HttpClient: Checking for cache file C:\Users\Robert\AppData\Roaming\Emby-Server\cache\httpclient\424b7dfea9b6ab50e233fb24cf5008c0

2017-03-20 19:59:00.0576 Info App: Streaming Channel hdhr_54.1_4db9ee941a85ae1dacb254c5be41810d

2017-03-20 19:59:00.0576 Info App: GetChannelStream: channel id: hdhr_54.1_4db9ee941a85ae1dacb254c5be41810d. stream id: native_0bea1e33c256fc6a25c5e3f7fda9f8f6 profile: native

2017-03-20 19:59:00.0576 Info App: Opening HDHR Live stream from http://192.168.10.3:5004/auto/v54.1

2017-03-20 19:59:00.0576 Info HttpClient: HttpClientManager GET: http://192.168.10.3:5004/auto/v54.1

2017-03-20 19:59:00.3408 Info App: Opened HDHR stream from http://192.168.10.3:5004/auto/v54.1

2017-03-20 19:59:00.3408 Info App: Beginning multicastStream.CopyUntilCancelled

2017-03-20 19:59:00.3408 Info App: Returning mediasource streamId 6928912e7c724327ac2871c397bd1f74native_0bea1e33c256fc6a25c5e3f7fda9f8f6, mediaSource.Id 43bc12707a6647fcb56fbd275b5073f3_native_0bea1e33c256fc6a25c5e3f7fda9f8f6, mediaSource.LiveStreamId 

2017-03-20 19:59:00.3408 Info App: Beginning recording. Will record for 61.9942868483333 minutes.

2017-03-20 19:59:00.3408 Info App: Writing file to path: G:\Recordings\Supergirl\Season 2\Supergirl S02E16 Star-Crossed.ts

2017-03-20 19:59:00.3408 Info App: Opening recording stream from tuner provider

2017-03-20 19:59:00.3408 Info HttpClient: HttpClientManager GET: http://127.0.0.1:8096/LiveTv/LiveStreamFiles/0a3cccc09db3461cbae95ef283bda195/stream.ts

2017-03-20 19:59:00.3408 Info HttpServer: HTTP GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/0a3cccc09db3461cbae95ef283bda195/stream.ts. UserAgent: Emby/3.0

2017-03-20 19:59:00.3994 Info App: Opened recording stream from tuner provider

2017-03-20 19:59:00.5517 Info App: Copying recording stream to file G:\Recordings\Supergirl\Season 2\Supergirl S02E16 Star-Crossed.ts

2017-03-20 19:59:20.3447 Info HttpClient: HttpClientManager POST: http://192.168.10.1:5000

2017-03-20 19:59:20.3447 Info HttpClient: HttpClientManager POST: http://192.168.10.1:5000

2017-03-20 19:59:20.3447 Info HttpClient: HttpClientManager POST: http://192.168.10.1:5000

2017-03-20 19:59:20.3447 Info HttpClient: HttpClientManager POST: http://192.168.10.1:5000

2017-03-20 20:00:00.5654 Info LibraryMonitor: Recordings (G:\Recordings) will be refreshed.

 

Is emby trying to record "Supergirl" on two different channels at the same time and trying to write the same filename twice?

 

I didn't see anything odd in Windows event viewer

[earthtorob 5]

Oh...also.  The "Supergirl" video was 0Mb in size until I restarted the server.  then suddenly it was like 6 Gig.   So maybe the error isnt in the opening of the file, but in the closing of it. 

 

I attached the logs after the reset.

 

server-63625676661.txt

server-63625651200.txt

[Erik 120]

Well, regarding just the HDhomerun log, are you Turning the unit off every night as the log only contains a power on status with DHCP and time change. The log would contain an entry for each request from Emby like this example:

 

20170313-23:59:59 Tuner: tuner0 tuning 4.1 WIVB-HD (8vsb:623MHz-5)

20170313-23:59:59 Tuner: tuner0 streaming http to 192.168.123.50:52198

[earthtorob 5]

Nope....the device stays on 24/7.

 

So it looks like the problem is with my device.   Here is the latest log.

 

19700101-00:00:02 System: reset reason = power on
19700101-00:00:08 System: network link 100f
19700101-00:00:09 System: ip address obtained: 192.168.10.3 / 255.255.255.0
20170321-12:59:21 System: time changed from Thu Jan 1 00:00:24 1970 to Tue Mar 21 12:59:21 2017
20170321-14:57:59 Tuner: tuner0 tuning 24.1 WUTB-HD (8vsb:635MHz-3)
20170321-14:57:59 Tuner: tuner0 streaming http to 192.168.10.4:58964

[earthtorob 5]

I'm thinking I could replace the device or go with something different.   What do you all think?  Do you like your HDHomerun boxes?

[BAlGaInTl 279]

I'm thinking I could replace the device or go with something different.   What do you all think?  Do you like your HDHomerun boxes?

Personally, I really like the Silicondust HDHomerun hardware. I'm using the legacy ones. I've been using them since I "cut the cord" about 4 years ago. I've never had a problem with them really.

 

I think that Emby just needs some refinement in the Live TV area. Given the progress that I've seen in my short time as a premiere member, I'm sure that it will come quickly.

[maegibbons 1267]

Hi

 

Our HDhomerun works very well for our basic OTA Live TV and DVR needs (through emby).  I certainly wouldnt change.

 

For other channels we have IPTV.

 

Krs

 

Mark

[Erik 120]

I'm running 3x HDhomerun extend units (2 of the new fanless and 1 of the old fan ones).They work great with emby, even when tested 6x recording all at once.

 

And when I had an issue with one (old one with fan had problem) and silicondust support was great (takes a little time, but they replaced it with a brand new fanless one).

[earthtorob 5]

So my HDHomerun reboot might be a bad unit.   Anybody using this model?

 

Hardware Model HDHR4-2US

Firmware Version 20161107  

Device ID 104392D2

Edited March 21, 2017 by earthtorob

[earthtorob 5]

I updated the firmware.....I get communications error when I try a channel scan.   I think my until sucks.  And Silicon dust help sucks too.  I might just go with an internal card.   As much as I liked having a simple external unit.

[Erik 120]

I had used the "connect" version before, i now use all HDTC-2US (Transcode models).

 

It seems odd that it would just reboot without any errors being logged. I would expect to see something in the log if the unit was faulty.

 

What about a possible power supply problem? I remember reading about power supply faults on some of the units (don't know how old yours is) and sometimes it only presents itself when actually trying to use the unit (or when the 2nd tuner kicks in, as tuner1 is given priority if there is insufficient power).