NPVR 2.2.6 Recording Service Crash
|
2011-10-31, 02:08 AM
This just happened again today. I haven't had a chance to try the CollectEIT config change but note that I never had any lockups before (when using 2.2.6, R1 patches). Now having upgraded to R2 patches I have already had two lockups in less than a week so it seems like some change in R2 has caused this issue. I really hope this can be resolved because missing recordings is a big problem.
My Plugins: PhotoFilter, MusicMonkey, Windows Desktop Gadget
2011-10-31, 02:16 AM
Post the logs so we can see if it is the same thing - then try the CollectEIT setting to see if helps. The more data points I have the better.
The same problem has occurred off and on for people for years with GBPVR and more recently with NextPVR. It has certainly become more common recently, though I cant think of any reason why. I'm still unable to reproduce it here, and I haven't received any useful info from users that has pinpointed the problem, so it's difficult to fix. I've had an attempt at a work around for the next release.
2011-10-31, 02:22 PM
sub Wrote:Post the logs so we can see if it is the same thing - then try the CollectEIT setting to see if helps. The more data points I have the better. Sorry, this happened right before I went to watch Live TV last night so I just restarted the service quickly and when I finally looked at the logs today they all start past the occurrence. The previous time it got stuck at "Graph stopping..." so I assume it was the same this time. I have added the CollectEIT setting so I will see how it goes.
My Plugins: PhotoFilter, MusicMonkey, Windows Desktop Gadget
cncb Wrote:I have added the CollectEIT setting so I will see how it goes. Unfortunately, the CollectEIT setting had no effect because I just had another lockup last night. As you can see from the attached pertinent part of the log, it got stuck on "Graph stopping..." again but was able to update the EPG later on even though the service was "locked up" otherwise.
My Plugins: PhotoFilter, MusicMonkey, Windows Desktop Gadget
2011-11-02, 01:48 PM
Can we expect the new release with the "workaround" pretty soon? This suddenly is happening almost daily for me now and having to check manually before all my recordings start to make sure the service isn't locked up isn't very feasible. Thanks.
My Plugins: PhotoFilter, MusicMonkey, Windows Desktop Gadget
2011-11-02, 04:44 PM
cncb Wrote:Can we expect the new release with the "workaround" pretty soon?I wasnt anticipating doing a release this soon, and I've got a lot of broken half done stuff at this stage, so not great timing for me.
2011-11-02, 06:48 PM
Cncb, What is your setup/country? From my experience it is usually something in the stream that isn't handled properly so usually it is a certain Frequency that has the problem.
So if you have multiple recordings you should test to see which one is causing it. Also if you aren't using DVB/ATSC EPG. Make sure all your channels are NOT set to DVB/ATSC EPG. also uncheck Update DVB epg during live tv under the misc tab.
Intel i5 3.2Ghz Quad Core, Windows 10 Pro 64Bit
12 GB RAM, Gigabit LAN,3TB SATA HD 8MB Cache Dedicated Recording Drive SiliconDust Prime, PCH A-100 & C-200, Chromecast, FireTV Raspberry Pi 3 Running OSMC, Samsung Smart TV UN32H5201AF Cable Provider: Comcast in Oregon, USA
2011-11-02, 07:22 PM
BrainStormer Wrote:Cncb, What is your setup/country? From my experience it is usually something in the stream that isn't handled properly so usually it is a certain Frequency that has the problem. I am in the US with ATSC and all the channels are set up to use XMLTV. It doesn't appear to be just one channel or program causing it. Also, I never had any lockups until I updated to 2.2.6 R2 so it seems likely some change between R1 and R2 is causing this for me.
My Plugins: PhotoFilter, MusicMonkey, Windows Desktop Gadget
2011-11-02, 07:35 PM
I cant think of any specific patch that is likely to be the cause of this.
R1 or R2 is just a collection of patches that Johnsonx42 has compiled from the individual patches I've posted. You might need to go through the individual patches to see if you can narrow it down to a specific patch introduced. ie, apply the R1 collection, then selectively apply the later patches to see if you can identify when this problem started happening. This would give me some good clues on where to look. |
|
|
