Error attempt

[mvallevand]

Does NextPVR attempt to reread a directory on error? For the first time I can recall NextPVR failed to record a show and it might simple have been because my NAS was waking up slowly too.

Code:

2012-12-13 12:57:36.835 [DEBUG][4] Resuming... 2012-12-13 12:57:37.018 [DEBUG][7] Recording service noted the system was resuming... 2012-12-13 12:57:37.020 [DEBUG][7] Starting: C:\Users\Public\NPVR\Scripts\Wakeup.bat 2012-12-13 12:57:38.710 [DEBUG][5] cycling MVP servers 2012-12-13 12:57:38.710 [DEBUG][5] Starting MVP server 0 2012-12-13 12:57:44.651 [DEBUG][7] C:\Users\Public\NPVR\Scripts\Wakeup.bat has exited 2012-12-13 12:59:19.003 [DEBUG][7] Unexpected error in GetTargetName: System.IO.IOException: The specified network name is no longer available. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity) at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity) at NShared.RecordingService.GetTargetName(ScheduledRecording scheduledRecording) at NShared.RecordingService.WorkerThread() . but it sleeps and works fine afterwards. 2012-12-13 13:57:35.252 [DEBUG][4] Resuming... 2012-12-13 13:57:35.283 [DEBUG][7] Recording service noted the system was resuming... 2012-12-13 13:57:35.358 [DEBUG][7] Starting: C:\Users\Public\NPVR\Scripts\Wakeup.bat 2012-12-13 13:57:36.918 [DEBUG][5] cycling MVP servers 2012-12-13 13:57:36.919 [DEBUG][5] Starting MVP server 0 2012-12-13 13:57:41.232 [DEBUG][7] C:\Users\Public\NPVR\Scripts\Wakeup.bat has exited 2012-12-13 13:59:07.151 [DEBUG][7] allocating recording target filename: K:\Homeland\Homeland_20121213_14001500.ts 2012-12-13 13:59:07.153 [DEBUG][7] About to start recording (2775 on 1524): K:\Homeland\Homeland_20121213_14001500.ts... 2012-12-13 13:59:07.158 [DEBUG][7] Free space 587198365696 (K:\)

Martin

[sub]

Does NextPVR attempt to reread a directory on error?

No - it relies on the file system being in a functioning state when it attempts to use it.

To be honest, I've never recommended recording to a network drive. Too much stuff like this that can go wrong.

[mvallevand]

Ok, but it's a shame. I've recorded 100's of times fine, and I expect that a simply retry could right a lot of those things that you say go wrong being networked. Besides it seems better than lost recordings.

I now prefer that my backend is powered off except when I record/watch live tv and as that is only 10-20 hours a week, playing files from the share is the logical way to do this.

Martin

[sub]

How long do you think it would take your NAS to wake or reappear in this sort of scenario?

[mvallevand]

That reminds me I need to send a post on my findings on my client side testing being slow

2012-11-28 17:07:53.830 [DEBUG][1] LoadList@0
2012-11-28 17:08:06.188 [DEBUG][1] ACTIVATE_PLUGIN: Recordings
2012-11-28 17:08:06.188 [DEBUG][1] ACTIVATE_PLUGIN
2012-11-28 17:08:06.191 [DEBUG][1] OnKeyDown() done. Took 12360.70703125 ms

Martin

[whurlston]

Use your wakeup.bat to stall for a few seconds. You can use either

Code:

Choice /CS /C:T /D:T /N /T:5

where /T: is the number of seconds to delay. Or

Code:

ping 1.1.1.1 /w 1000 /n 3 > null

where /n is roughly half the number of seconds to delay. Choice is more accurate.

[mvallevand]

I think it could be my NAS drive spinning down and after not being accessed for 12+ hours and I might need to do DIR on it and not just ping the NIC I don't do too many mid-day recordings. However I still think a server should be a bit more tolerant of errors than a client who has a a chance to retry.

Martin

[johnsonx42]

then have your wakeup.bat write something to the nas, a log line or something, that will make sure it's awake and ready.

(not that I'm disagreeing with the idea that NRecord could do a retry)