Late in Yesterday's NASCAR Race I elected to extend the recording time by 20 minutes by using the web app and clicking on the in-process NASCAR recording item on the Scheduler page. The dialog was produced and I entered in a new post-padding time of 20 minutes. When I clicked Save, the item disappeared from the Scheduler list and appeared no where else even thought the race continued to record. The DCR-3250 web page showed a tuner for the race as still active. I elected to stop recording about 10 minutes into the 20 minute extension, but found no way to do it from the web app. I needed to use the desktop app to do the cancel. The recording extended as expected and stopped 10 minutes after the scheduled end time.

Logs attached. Where did the web app recording item go?

Attached Files

  logs-20200607-1910.zip (Size: 573.78 KB / Downloads: 3)

Hi all,

I've just started using NextPVR and am loving the features. Currently using it for iptv services & recording so purely web based console (using m3u file and xml feed for epg).
I am running the latest version 5.x.x which was downloaded via the nextpvr website (download based link).

Over the past few days the Application is crashing and I hope to find a solution. 
When this occur the NextPVR tray icon goes grey and the web page cannot be loaded (page cannot be found); http://127.0.0.1:8866/index.html

PC is running patched Windows 10 Pro x64 1909.
I have EPG running automatically daily at 6am.
PC is running Trend Micro Internet Security (no exclusions).
PC also has a DVB Tuner card with ARGUS TV Recorder, but there is no recording conflicts (recording same time as NextPVR).
I have disabled this detected card in NextPVR but will look at moving it over soon once the app is stable.


For now, The quick fix is to restart the computer, OR Restart the NextPVR Windows Service.

I have gone thorugh the nrecord.log file and all seems normal (I can see web requests 127.0.0.1 up until a certain point then it stops as per the crash logs below)

So far in application log I can see when the crashes occur and there seems to be some pattern, has anyone experienced this before?
https://imgur.com/a/0haKmX4
(The highlighted lines in the above picture are the NextPVR service crashing).

When the crash occurs, I get 2x errors pop up in the application event log, they are:

First one is .NET Runtime error

Log Name:      Application
Source:        .NET Runtime
Date:          8/06/2020 10:39:02 AM
Event ID:      1026
Task Category: None
Level:        Error
Keywords:      Classic
User:          N/A
Computer:      HTPC
Description:
Application: NextPVRServer.exe
CoreCLR Version: 4.700.19.60701
.NET Core Version: 3.1.1
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException: Object reference not set to an instance of an object.
  at NShared.IPTVRecorder.CheckTSUrl(String url, String& reason, String& location)
  at NShared.IPTVRecorder.StartStream(ChannelMapping channelMapping, String target, String& reason)
  at NShared.RecordingService.WorkerThread()
  at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
  at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
  at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
  at System.Threading.ThreadHelper.ThreadStart()



Followed by

2. Application Error

Log Name:      Application
Source:        Application Error
Date:          8/06/2020 10:39:02 AM
Event ID:      1000
Task Category: (100)
Level:        Error
Keywords:      Classic
User:          N/A
Computer:      HTPC
Description:
Faulting application name: NextPVRServer.exe, version: 1.0.0.0, time stamp: 0x5dedc13b
Faulting module name: KERNELBASE.dll, version: 10.0.18362.815, time stamp: 0xb89efff3
Exception code: 0xe0434352
Fault offset: 0x000000000003a799
Faulting process id: 0x2414
Faulting application start time: 0x01d63d224aed2c6d
Faulting application path: C:\Program Files\NextPVR\NextPVRServer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: ce17f28a-2d29-4e24-b4be-4eea7643ed4e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

As per the thread https://forums.nextpvr.com/showthread.php?tid=59499 I have set up an extras device that calls a batch script to encode raw video from a capture card using VLC. This has all been working fine, however since upgrading to the most recent version of NPVR, I cannot get a stream to play. The blaster part of my code is still functioning fine, however my VLC commands are no longer being called. I have a quick look through the logs and I kept seeing references to FFMPEG. 

The logs can be found here:

 https://filebin.ca/5PGRWjdWojRu

My batch file looks like this:

I can't start at the beginning of a recording in V5. I often record races on Sundays and start watching while in progress in V4 but in V5 I always wind up at the the live point of the race, it on't let me start at the beginning unless the recording is over.

I just installed NPVR v5 on an Ubuntu 20.x machine.  I use a HDHomeRun Prime as my tuner and an RPi.

I think that I have everything installed correctly.  I installed the HDHomeRun application and I can see the device and tuners and all of the channels via the HDHomeRun GUI.  NPVR scanned in the channels just fine.  I can see the channels just fine within the application, I can load the channels just in in RPi, but I just can't play anything.

From what I can tell, everything is installed correctly and functioning correctly.  I just can't stream any live TV.  Please see attached log files.

Thanks

Daryl

[attachment=undefined][attachment=1692]

I have 3 different client systems and experience hangs on all of them periodically. Seems to occur in the same location of a recording if I restart the recording (Fortunately Resume skips past the hang location).
Clients and server are all Windows 7. Latest V4 NextPVR. Gigabit network.
I've had 2 hangs this morning from one client system and repeated one of them for a 3rd hang by restarting the recording playback. Logs attached.
  logs-20200607-0958.zip (Size: 98.74 KB / Downloads: 2)

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name: AppHangB1
  Application Name: NextPVR.exe
  Application Version: 1.0.0.0
  Application Timestamp: 5d93888e
  Hang Signature: dd97
  Hang Type: 1
  OS Version: 6.1.7601.2.1.0.256.1
  Locale ID: 1033
  Additional Hang Signature 1: dd97d4b16afeda79fd609cfd84d6733f
  Additional Hang Signature 2: 013f
  Additional Hang Signature 3: 013f50fccd9e981c89f463ea6faebcd3
  Additional Hang Signature 4: 62c6
  Additional Hang Signature 5: 62c6c3274fad98609c91337cafb8f2f2
  Additional Hang Signature 6: 48bc
  Additional Hang Signature 7: 48bc82c8cb7e3339b197694c489b253e

Previously I had a batch script like this:

Over the last few days I have noticed that a number of scheduled recordings have been missed, not failed but they continue to be in a 'Pending' state. A couple of these have been automatically rescheduled (?) to another time - Emmerdale and Coronation St to today, Sunday June 7th, at 09:00 (ITV3) and 07:30 (ITV3) respectively. However, in the case of Coronation St the pending start time has passed and it is still showing as 'Pending', Emmerdale has not yet reached its rescheduled start time but I kind of expect the same to happen.

On checking the logs I can see that from 2020-06-07 02:46:37.244 the database is being reported as locked, this continues to be reported until 2020-06-07 06:59:33.682. My SD update starts at 02:45 each day. I have recently started putting my NAS to sleep, unless disk activity is detected, from 22:00 to 07:00 each day. My recordings are held on a NAS NFS share but all the rest of my my NPVR setup, including the database, is held on the RPI4 local micro SD card I use to run NPVR and this does not sleep. 

It seems a bit of a coincidence that the NAS recordings share might be asleep when this problem starts to occur but should it be being used during a guide refresh from SD ? I would expect the PI to be able to refresh its guide / database when the NAS share is asleep. I could see it as a problem when recordings are due but the share would have been available well before Coronation St should have started recording and it doesn't account for the continued 'Pending' state of these recordings. The NAS share would NOT have been asleep when the previous recordings failed to start, and subsequently ended up in a 'Pending' state, last Friday (from 13:45 to 20:00) and which first alerted me to something being not right but which I haven't had time to investigate until just now.

I have attached the logs so you can see what appears to be happening.

Thanks as always for any help or advice you can provide, hopefully this ins't soemthing of my own making.

Chris


  logs-20200607-0843.zip (Size: 1.48 MB / Downloads: 5)

Please consider adding a download link to grab the media file inside the app, like the web interface

In the Android client, when you select a new channel group drop-down in settings then switch back over to the channels tab, the list doesn't update.

You have to exit and reload the app with every channel group change.