simonselmer 21 Posted November 29, 2019 Share Posted November 29, 2019 Hi Recording a 60 minutes Live TV program stopped approx 26 minutes after starting recording. The errors in the emby log starting from 2019-11-29 19:25:33.384. We were watching the program, a few minutes delayed, while recording. HDHomerun Extended Synology 918+ Nvidia shield client embyserver.txt Link to comment Share on other sites More sharing options...
simonselmer 21 Posted November 29, 2019 Author Share Posted November 29, 2019 So, the TV program I described in the first post, was a scheduled series. To night, just few minutes ago, I had another second scheduled series TV program that should also record, it started and failed 3 minutes after. Because I have had this issue for quite some time now, and had hoped the new server 4.3 had solved it, I also started the recording of the same TV program, using my Shield. 8 minutes after Emby stopped the recording by error, the Shield was still recording. See new emby log attached. I believe this is the error that starts it: 2019-11-29 20:02:05.599 Error SharedHttpPipelineSource: Give up retries copying live stream http://192.168.1.102:5004/auto/v2 *** Error Report *** Version: 4.3.0.30 Command line: /volume1/@appstore/EmbyServer/releases/4.3.0.30/EmbyServer.dll -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -ffdetect /var/packages/EmbyServer/target/ffmpeg/bin/ffdetect -restartexitcode 121 Operating system: Unix 4.4.59.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Runtime: file:///volume1/@appstore/EmbyServer/3rdparty/netcore/2.2.1/runtime/System.Private.CoreLib.dll Processor count: 4 Program data path: /var/packages/EmbyServer/target/var Application directory: /volume1/@appstore/EmbyServer/releases/4.3.0.30 System.IO.IOException: System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. ---> System.Net.Sockets.SocketException: Connection reset by peer --- End of inner exception stack trace --- at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error) in /source/corefx/src/System.Net.Sockets/src/System/Net/Sockets/Socket.Tasks.cs:line 1088 at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token) in /source/corefx/src/System.Net.Sockets/src/System/Net/Sockets/Socket.Tasks.cs:line 1062 at System.Net.Http.HttpConnection.ReadAsync(Memory`1 destination) in /source/corefx/src/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/HttpConnection.cs:line 1368 at System.Net.Http.HttpConnection.ConnectionCloseReadStream.ReadAsync(Memory`1 buffer, CancellationToken cancellationToken) in /source/corefx/src/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/ConnectionCloseReadStream.cs:line 40 at System.IO.Pipelines.PipeWriter.CopyFromAsync(Stream source, CancellationToken cancellationToken) at Emby.LiveTV.TunerHosts.SharedHttpPipelineSource.<>c__DisplayClass7_0.<<StartStreaming>b__0>d.MoveNext() Source: System.Net.Sockets TargetSite: Void ThrowException(System.Net.Sockets.SocketError) InnerException: System.Net.Sockets.SocketException: Connection reset by peer Source: TargetSite: embyserver v2.txt Link to comment Share on other sites More sharing options...
Luke 36988 Posted December 24, 2019 Share Posted December 24, 2019 @@simonselmer are you still running into this with Emby Server 4.3.1? Link to comment Share on other sites More sharing options...
simonselmer 21 Posted December 30, 2019 Author Share Posted December 30, 2019 Hi Luke I got to test it yesterday, and unfortunately it failed. I had scheduled one program to record, which stopped about 13 minutes after, and I started a recording of another program manually, which stopped recording 11 minutes later I attach the log, and I have copy pasted here some of the timeline I found which relates to the recordings. ----------------------------------------------------------------------------------------------------------- 1st program - This was scheduled the day before to be recorded. 2019-12-29 21:18:04 - Start scheduled recording 2019-12-29 21:18:04.551 Info LiveTV: Will record to /volume1/NAS1_Film_Serier/Optaget TV/Borgen 2019 Lars, Mette og magten/Borgen 2019 Lars, Mette og magten 2019_12_29_21_20_00.ts for 76.9241352716667 minutes. 2019-12-29 21:31:36.106 - MANY ERRORS OCCOURS 2019-12-29 21:31:36.116 Info LiveTV: Recording stopped: /volume1/NAS1_Film_Serier/Optaget TV/Borgen 2019 Lars, Mette og magten/Borgen 2019 Lars, Mette og magten 2019_12_29_21_20_00.ts ----------------------------------------------------------------------------------------------------------- 2nd program - I started recording this program after it had started. We then started watching it some minutes after I started the recording. The recording only lasted 11 minutes and 4 seconds, so we had to start Live TV. 2019-12-29 21:19:23.694 Info LiveTV: Recording timer fired for Ã…ret der gak. 2019-12-29 21:19:26.415 Info LiveTV: Will record to /volume1/NAS1_Film_Serier/Optaget TV/Ã…ret der gak (2019)/Ã…ret der gak 2019_12_29_21_05_00.ts for 110.559737556667 minutes. 2019-12-29 21:21:19.846 Info SessionManager: Playback stopped reported by app AndroidTv 1.7.54g playing Ã…ret der gak. Stopped at 48947 ms 2019-12-29 21:25:14.344 Info SessionManager: Playback start reported by app AndroidTv 1.7.54g playing Ã…ret der gak 2019_12_29_21_05_00. Started at 0 ms 2019-12-29 21:31:36.106 - MANY ERRORS OCCOURS 2019-12-29 21:33:40.448 Info LiveTV: Recording completed to file /volume1/NAS1_Film_Serier/Optaget TV/Ã…ret der gak (2019)/Ã…ret der gak 2019_12_29_21_05_00.ts 2019-12-29 21:33:40.448 Info LiveTV: Triggering refresh on /volume1/NAS1_Film_Serier/Optaget TV/Ã…ret der gak (2019)/Ã…ret der gak 2019_12_29_21_05_00.ts 2019-12-29 21:33:40.449 Info LiveTV: Refreshing recording parent /volume1/NAS1_Film_Serier/Optaget TV/Ã…ret der gak (2019) 2019-12-29 21:33:41.083 Info App: [LinuxMount] Checking we can attempt to mount [/volume1/NAS1_Film_Serier/Optaget TV/Ã…ret der gak (2019)/Ã…ret der gak 2019_12_29_21_05_00.ts], Extension = [.ts], Operating System = [Linux], Executables Available = [True]. Link to comment Share on other sites More sharing options...
Luke 36988 Posted December 31, 2019 Share Posted December 31, 2019 Can you please attach the complete emby server log? thanks. Link to comment Share on other sites More sharing options...
simonselmer 21 Posted December 31, 2019 Author Share Posted December 31, 2019 Sorry, of course, I forgot to click Attach-button embyserver 2019-12-29.txt Link to comment Share on other sites More sharing options...
Luke 36988 Posted January 3, 2020 Share Posted January 3, 2020 Have you checked your HDHomerun logs at there? Could there have been a loss of signal strength on the tuner? Link to comment Share on other sites More sharing options...
simonselmer 21 Posted January 3, 2020 Author Share Posted January 3, 2020 Hi. No, but I have now, and this is a copy paste of the system log from December 29th. It seems the HDHomeRun Log is 1 hour behind, so all these timestamps should be +1H 20191229-18:58:01 Tuner: tuner0 tuning 1 DR 1 (a8qam256-6875:266MHz-12050)20191229-18:58:02 Tuner: tuner0 streaming http to 192.168.1.100:4210420191229-20:14:59 Tuner: tuner0 http stream ended (remote closed)20191229-20:18:02 Tuner: tuner0 tuning 1 DR 1 (a8qam256-6875:266MHz-12050)20191229-20:18:03 Tuner: tuner0 streaming http to 192.168.1.100:4284820191229-20:19:24 Tuner: tuner1 tuning 2 TV 2 (Østjylla (a8qam256-6875:274MHz-200)20191229-20:19:25 Tuner: tuner1 streaming http to 192.168.1.100:3817420191229-20:31:35 Tuner: tuner1 http stream ended (remote closed)20191229-20:31:35 Tuner: tuner0 http stream ended (remote closed)20191229-20:36:49 Tuner: tuner0 tuning 2 TV 2 (Østjylla (a8qam256-6875:274MHz-200)20191229-20:36:50 Tuner: tuner0 streaming http to 192.168.1.100:4446820191229-20:58:02 Tuner: tuner1 tuning 12 DR 2 (a8qam256-6875:250MHz-17548)20191229-20:58:03 Tuner: tuner1 streaming http to 192.168.1.100:4423220191229-21:29:52 Tuner: tuner0 http stream ended (remote closed)20191229-21:29:59 Tuner: tuner0 tuning 2 TV 2 (Østjylla (a8qam256-6875:274MHz-200)20191229-21:30:00 Tuner: tuner0 streaming http to 192.168.1.100:3797820191229-21:44:59 Tuner: tuner1 http stream ended (remote closed)20191229-22:10:00 Tuner: tuner0 http stream ended (remote closed) Link to comment Share on other sites More sharing options...
simonselmer 21 Posted January 3, 2020 Author Share Posted January 3, 2020 Hi Another exampel today of 2 failed recordings within 20:15:57 - Started a recording. It stopped at 21:00, but it should have continued for 15 more minutes after program ended. Emby log shows error at 21:00 20.40 - A scheduled recording started. The program ended at 21.05 and recording should continue to 21.20. But the recording ended already 5 minutes after recording began, at 20.44. Emby log show errors at this time. Here is the HDHomeRun log from that time, NOTE add 1 HOUR to below timestamps to match Emby logs. 20200103-19:15:57 Tuner: tuner0 tuning 2 TV 2 (Østjylla (a8qam256-6875:274MHz-200)20200103-19:15:57 Tuner: tuner0 streaming http to 192.168.1.100:4154820200103-19:38:00 Tuner: tuner1 tuning 29 Disney Channel (a8qam256-6875:546MHz-16275)20200103-19:38:00 Tuner: tuner1 streaming http to 192.168.1.100:3824420200103-19:44:32 Tuner: tuner1 http stream ended (remote closed)20200103-20:00:24 Tuner: tuner0 http stream ended (remote closed) embyserver 2020-01-03.txt Link to comment Share on other sites More sharing options...
simonselmer 21 Posted January 8, 2020 Author Share Posted January 8, 2020 Hi Luke I wanted to do an experiment to try to rule out that the issues is my tuner. So I set up an Emby server on my laptop, and just set up TV and DVR, nothing else. I havethen over the last about 3 days recorded the same programs on both devices, and then afterwards tested if they had recorded the expected length of the TV program, and also noted down from which of the 4 tuners the program had been recorded from. I tested recording 1 program at a time, and also 2 programs at the same time, meaning all 4 tuners would be used. The results is that out the 12 recordings (mostly scheduled), - my laptop recorded all of them in full length - the Synology NAS failed 6 of them. It started the recording but stopped at any time during the show. Some few minutes after start. One TV show was over 5 hours long, where Emby of the NAS stopped after 4 hours. And I can tell from the HDHomeRun log that all 4 tuners have been used by both my laptop and the NAS. The NAS has both failed and succeded on all 4 tuners. So all in all I believe this indicates that the issue is not in the tuner. Should I perhaps enabled advance logging, and get some more data, when Emby on the NAS fails, would that bring any value to debugging? Link to comment Share on other sites More sharing options...
Luke 36988 Posted January 24, 2020 Share Posted January 24, 2020 @@simonselmer are you still running into this? Link to comment Share on other sites More sharing options...
simonselmer 21 Posted January 24, 2020 Author Share Posted January 24, 2020 Actually no, I haven't had the issue for a couple of weeks. We do not watch much TV, so it has mostly for my own testing of recordings, which I have done over that last weeks. After I posted my testing on Jan 8th, I then installed Emby on my second Synology NAS, to test recording the same TV shows on both NAS at the same time, to see if that would show difference. I cannot recall how the first test went, but for the past 1½-2 weeks of testing, my primary NAS has recorded all scheduled shows in full length. It didn't fail once. And right now I just remembered I recorded 8 shows 3 days ago as a test. Just checked them now, and they also recorded all in full length. BUT I also have to say that this issue has appeared perodicaly, so I dont know if the issue could reappear. So I dont know if I dare day it seems to be working now!? But without any updates/changes anywhere that I'm aware of. Regards Simon Link to comment Share on other sites More sharing options...
Luke 36988 Posted February 2, 2020 Share Posted February 2, 2020 Interesting, thanks for the feedback! Link to comment Share on other sites More sharing options...
simonselmer 21 Posted February 3, 2020 Author Share Posted February 3, 2020 Hi again I was too early to make it a success It failed again Friday. So my lately testing has been "just" to do a lot of scheduled recordings (without viewing them at the same time) and they seemed to be OK. But Friday I did what we ususally do, I scehdule a TV program to start record at 8 pm (it begins 2 minutes prior to that). At about 8.05 I then start watching that recording by selecting "start from beginning", and that seems to then stop the recording. I have seen this pattern many times, that it seems that Emby server (on synology at least) has a problem handling viewing and ongoing recording. Not every time, but some times. I need to do more testing on that specific scenario. Regards Simon Link to comment Share on other sites More sharing options...
Luke 36988 Posted February 19, 2020 Share Posted February 19, 2020 Have you seen it again since then? Link to comment Share on other sites More sharing options...
simonselmer 21 Posted May 22, 2020 Author Share Posted May 22, 2020 Hi We dont watch my TV. But same thing happened again. I started a recording at 20:00 (19:58). We started watching that recording from the begining at around 20:50 I think. At around 21:20 the recording stops (should have recorded until 21:30+15 minutes). See the log at 21:18, many errors, if that helps. Besides the recording stops before time, I noticed also that from the time we started watching, regular corruptions started appearing fra that time. So from 20:00 -> around 20:50 the recording was fine, no corruptions. But from around 20:50 and until it stops, there were regular corruptions. I have rewatched the recording on my laptop, and the corruptions are indeed in the recording, meaning it's no a playback issue. So my non-expert-investigations tells me that the Emby/Synology has a problem somewhere, still, with recording to a file, which is also being played at the same time. At least if the recording is long before the playback starts. Link to comment Share on other sites More sharing options...
Luke 36988 Posted May 23, 2020 Share Posted May 23, 2020 Hi We dont watch my TV. But same thing happened again. I started a recording at 20:00 (19:58). We started watching that recording from the begining at around 20:50 I think. At around 21:20 the recording stops (should have recorded until 21:30+15 minutes). See the log at 21:18, many errors, if that helps. Besides the recording stops before time, I noticed also that from the time we started watching, regular corruptions started appearing fra that time. So from 20:00 -> around 20:50 the recording was fine, no corruptions. But from around 20:50 and until it stops, there were regular corruptions. I have rewatched the recording on my laptop, and the corruptions are indeed in the recording, meaning it's no a playback issue. So my non-expert-investigations tells me that the Emby/Synology has a problem somewhere, still, with recording to a file, which is also being played at the same time. At least if the recording is long before the playback starts. Hi there, can you please provide the server log from this time? thanks. Link to comment Share on other sites More sharing options...
simonselmer 21 Posted May 23, 2020 Author Share Posted May 23, 2020 Yes, of course. I probably forgot to click "attach this file". See the log from 2020-05-22 attached. This evening I just recorded part 2 of the same show from yesterday. We did not watch this show while it was being recording. I just check the recording and everything is good. It has recorded everything and no issues. So again, my experience from running Emby server on the synology is, that recording a TV show is not a problem. But it has challenges recoding and then start watching the show from beginning some time after it started, while it is still recording. Another "thing", I noticed my emby server being down today. I had to stop it on the synology and then start it again. I see in the log that the first error is at "2020-05-23 16:06:35.418" and then a LOT of errors appears after that. That last error in the log comes at "2020-05-23 18:05:50", about hours later, so this is where Emby stopped working. embyserver-2020-05-22.txt embyserver-2020-05-23_1.txt Link to comment Share on other sites More sharing options...
Luke 36988 Posted August 4, 2020 Share Posted August 4, 2020 If you'd like to try something new I'm interested to know how this compares: Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now