akaufman 2 Posted October 16, 2024 Posted October 16, 2024 For new series I have scheduled, I have been having a problem where the recording will happen, but after the recording is finished the file is automatically removed. In the log I see Triggering refresh, then Refreshing recording parent, followed by Removing item from database. It's almost like the auto retention is faulty. But I have my auto retention set to as many as possible.
Luke 42077 Posted October 16, 2024 Posted October 16, 2024 Hi there, can we please look at a specific example: How to Report a Problem Thanks.
akaufman 2 Posted October 17, 2024 Author Posted October 17, 2024 Attached is my log from the time. If you search for removing item from database you will see what I am referencing. Additionally I noticed an error in the log that is for another show that failed to record. I am not sure if these are separate issues as one is a failed recording and one is a case of emby removing the completed recording embyserver-63864547200.txt
akaufman 2 Posted October 17, 2024 Author Posted October 17, 2024 No all recordings are failing. Here is my log from last night. embyserver-63864720000.txt
Luke 42077 Posted October 17, 2024 Posted October 17, 2024 4 hours ago, akaufman said: No all recordings are failing. Here is my log from last night. embyserver-63864720000.txt 623.57 kB · 0 downloads See: Quote System.IO.IOException: System.IO.IOException: The process cannot access the file 'F:\TV\Survivor (2000)\Season 47\Survivor S47E05 The Scales Be Tippin - 1.ts' because it is being used by another process. Any idea what other process could be touching the file? For one I would make sure that you haven't somehow managed to have two instances of embyserver.exe running.
akaufman 2 Posted October 18, 2024 Author Posted October 18, 2024 There is only one instance of emby running. And now I see that some recodings for series previously scheduled from last season are working. But some some are not here are the logs from today with a successful recording and a failure. I am seeing ffprobe errors but I am not sure what that means. embyserver.txt
akaufman 2 Posted October 21, 2024 Author Posted October 21, 2024 I added additional exceptions to the windows defender scan just in case that was the cause. But I am still getting the error: "Error SessionManager: Error sending message" any help would be appreciated. embyserver-63865065600.txt
Luke 42077 Posted October 21, 2024 Posted October 21, 2024 On 10/17/2024 at 11:23 PM, akaufman said: There is only one instance of emby running. And now I see that some recodings for series previously scheduled from last season are working. But some some are not here are the logs from today with a successful recording and a failure. I am seeing ffprobe errors but I am not sure what that means. embyserver.txt 535.63 kB · 0 downloads HI, are you saying something didn't record?
akaufman 2 Posted October 21, 2024 Author Posted October 21, 2024 Well I guess technically it did record but was then promptly removed after if finished if I am reading the log correctly.
Luke 42077 Posted October 21, 2024 Posted October 21, 2024 2 minutes ago, akaufman said: Well I guess technically it did record but was then promptly removed after if finished if I am reading the log correctly. Well what do you see in your library?
akaufman 2 Posted October 21, 2024 Author Posted October 21, 2024 Nothing is in the library. But in the file folder I see the .info files created but no .ts files.
akaufman 2 Posted October 23, 2024 Author Posted October 23, 2024 One thing I noticed today is it seems that all of these instances of recordings being removed immediately are from the same channel.
Carlo 4560 Posted October 23, 2024 Posted October 23, 2024 Hi, Below is from your log file. This is showing Emby failing to probe the stream. This would explain why you see something written, but then deleted. Is drive M: a local or network share? Have you check the signal & quality of the channel you're trying to record on the tuner? Quote 2024-10-20 20:30:02.320 Info LiveTV: Getting media sources for recording from channel 2693496 9.1 WUSA-HD to record to F:\TV\Tracker (2024)\Season 2\Tracker S02E02 Ontological Shock.ts 2024-10-20 20:30:02.349 Info LiveTV: Opening live stream for recording from channel 2693496 9.1 WUSA-HD to F:\TV\Tracker (2024)\Season 2\Tracker S02E02 Ontological Shock.ts 2024-10-20 20:30:02.361 Info LiveTvManager: Opening channel stream, external channel Id: hauppauge_7 2024-10-20 20:30:02.361 Info LiveTV: Streaming Channel hauppauge_7, with streamId: native_4dc934a7046e466c67fea57758c5b6f6 2024-10-20 20:30:02.377 Info HauppaugeTunerWindows: GetChannelStream: channel id: 7. mediaSourceId: native_4dc934a7046e466c67fea57758c5b6f6 2024-10-20 20:30:02.377 Info HauppaugeTunerWindows: Hauppauge GetChannelStream. Args: "GetChannelStream" "1" "7" "native_4dc934a7046e466c67fea57758c5b6f6" 2024-10-20 20:30:02.377 Info HauppaugeTunerWindows: ProcessRun 'HauppaugeChannel 7' Execute: C:\Users\MediaServer\AppData\Roaming\Emby-Server\system\HauppaugeWindowsProvider.exe "GetChannelStream" "1" "7" "native_4dc934a7046e466c67fea57758c5b6f6" 2024-10-20 20:30:19.320 Info HauppaugeTunerWindows: Hauppauge GetChannelStream response: M:\Transcode\Pause Buffer\livetv-3068.ts 2024-10-20 20:30:22.371 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: C:\Users\MediaServer\AppData\Roaming\Emby-Server\system\ffprobe.exe -analyzeduration 3000000 -i "http://127.0.0.1:8096/LiveTv/LiveStreamFiles/cf7bc6de0f39437b81e241b8d03cb2ee/stream.ts" -threads 0 -v info -print_format json -show_streams -show_format -show_data 2024-10-20 20:30:23.210 Info Server: http/1.1 GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/cf7bc6de0f39437b81e241b8d03cb2ee/stream.ts. Source Ip: 127.0.0.1, Accept=*/*, Connection=close, Host=host6, User-Agent=Lavf/59.27.100, Range=bytes=0-, Icy-MetaData=1 2024-10-20 20:31:23.114 Error MediaProbeManager: Timeout while running Ffprobe -analyzeduration 3000000 -i "http://127.0.0.1:8096/LiveTv/LiveStreamFiles/cf7bc6de0f39437b81e241b8d03cb2ee/stream.ts" -threads 0 -v info -print_format json -show_streams -show_format -show_data 2024-10-20 20:31:23.631 Info Server: http/1.1 Response 500 to 127.0.0.1. Time: 60421ms. GET http://127.0.0.1:8096/LiveTv/LiveStreamFiles/cf7bc6de0f39437b81e241b8d03cb2ee/stream.ts 2024-10-20 20:31:23.636 Info MediaProbeManager: ProcessRun 'ffprobe' Process exited with code -1 - Failed 2024-10-20 20:31:23.636 Error MediaProbeManager: ProcessRun 'ffprobe' Error Output: ffprobe version 5.1-emby_2023_06_25 Copyright (c) 2007-2022 the FFmpeg developers and softworkz for Emby LLC built with gcc 12.2.0 (Rev10, Built by MSYS2 project) 2024-10-20 20:31:23.698 Error MediaSourceManager: Error probing live tv stream
akaufman 2 Posted October 29, 2024 Author Posted October 29, 2024 The drive is local. So it seems I was having a signal issue and I am still not sure why. I was able to view the channel in wintv10 but not emby. The weather was clear and nothing changed in terms of antenna position. So failure in probing the stream means that emby cannot find a signal? I reset the server and reattached the tuners and now it works.
Carlo 4560 Posted October 31, 2024 Posted October 31, 2024 Did you try it a couple of times to see if it would work? Does this happen often or just that one time?
akaufman 2 Posted October 31, 2024 Author Posted October 31, 2024 It was happening every time for one channel. But removing the tuners and reattached the tuners seemed to fix it. It has been recording as normal for the last few days. 1
Luke 42077 Posted November 1, 2024 Posted November 1, 2024 2 hours ago, akaufman said: It was happening every time for one channel. But removing the tuners and reattached the tuners seemed to fix it. It has been recording as normal for the last few days. Thanks for following up. Please let us know if you see it again. Thanks.
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