2022-03-30, 04:18 PM
Since v5, I have been having problems with missed recordings or short recordings. Attached is an example of short recordings.
2022-03-30, 04:18 PM
Since v5, I have been having problems with missed recordings or short recordings. Attached is an example of short recordings.
2022-03-30, 04:35 PM
This post is really confusing. So, I'm not going to spend any more time looking at it.
Your examples say they were recorded "Today", but you don't tell us what date "Today" was. And your log zip file indicates that it is from 2022-03-26, but the log files inside it show activity from 2022-03-29. So it would appear that you have not simply exported the logs from the web app and posted them. Further, presuming that "Today" is supposed to be 2022-03-29, Your logs show that the server wasn't even running at the times that your "problem" recordings were supposedly made since it was shutdown at 13:37 and not started back up until 18:26.
2022-03-31, 02:58 AM
(This post was last modified: 2022-03-31, 03:01 AM by Dale Dewing.)
Today was 03/29. That logfile was from the web app that evening. I just double checked and the zip file was generated at 22:20:09 that evening. And can the server not be running when it recorded those shows, just not to the end of the shows.
2022-03-31, 03:05 AM
The logs seem ok to me, but it looks like NextPVR is stealing the in-use tuner for new recordings.
When you upgraded from V4 to V5 did you copy npvr.db3? Martin
2022-03-31, 12:43 PM
(2022-03-31, 03:05 AM)mvallevand Wrote: The logs seem ok to me, but it looks like NextPVR is stealing the in-use tuner for new recordings. Martin: Did you notice this error? Code: 2022-03-29 17:30:01.984 [ERROR][9] Unexpected error on LocalRecorder.StartStream(): System.Net.WebException: An error occurred while sending the request. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
2022-03-31, 12:57 PM
Yes that is the error that sub might need to look into. When a new recording starts it kills the connection on the previous recorded socket. I haven't seen this before which is why I asked if this could have been from a manual copy of npvr.db3.
Martin
2022-03-31, 03:35 PM
Dale, it's not that clear from your logs. I might need to see another example, so I can compare what's happening in both.
2022-03-31, 04:59 PM
(This post was last modified: 2022-03-31, 05:08 PM by Dale Dewing.)
Don't remember about the db3 file. Will post the next error. I do seem to only get the error when I am recording a series of the same show. In this case I recorded 4 Tales of Wells Fargo one right after the other. I have also had problem of it not recording some of the shows on Friday which run all day, one after another. Although of course I have to select them singly, which is probably another problem. Where I record just a single show it seems to work fine.
|
|