Deleting recordings from PC clients

[sub]

Haven't tried scheduling a recording but it is always after I have watched the recording so it should have communicated with server by then.

Actually, watching a recording uses a different mechanism for communicating with the server, so has exercised the interface in question.

[sub]

Since you are streaming from the T:\ drive, maybe the C: drive on the server holding the database is spinning down and it just needs time to open up.

Admittedly because of the clock differences between his client and server, I cant tell whether the big delay is after or before the delete happening on the server. I had been thinking "after", but you're right that it could be "before". I dont think it relates to loading from the database though, since the database accesses happen further on in the code, inside the areas that show as happening quickly in the logs.

It could be some slow connection to the server though. Maybe because of name resolution, or possibly firewall related.

[cncb]

Since you are streaming from the T:\ drive, maybe the C: drive on the server holding the database is spinning down and it just needs time to open up.

I have the drives on my server set to never spin down and I had watched a few seconds of the program before the delete so it had accessed the database right before that.

[cncb]

Actually, watching a recording uses a different mechanism for communicating with the server, so has exercised the interface in question.

Did you mean it "hasn't exercised the interface in question" such that I should still try this out?

[sub]

Yes, meant 'hasnt'.

Yes, I'd try starting NPVR and scheduling a new recording, then try deleting one. I'm curious if the delay will shift to the scheduling activity instead.

[BrettB]

You might want to check out this thread:

So, unless I'm missing something, NPVR should have just "touched" each of the recordings to verify its existence. So, it should not be a problem with one of the drives being spun down.

I had Windows set to not ever spin down the drives, but it appeared to be happening anyway--or something similar. They were Seagate 1TB drives. I ended up switching to different drives, and I don't believe that I've seen the problem with a long delay for the "1st delete".

[martint123]

I had Windows set to not ever spin down the drives, but it appeared to be happening anyway--or something similar

My Samsung drives will spin down of their own accord no matter what Windows tells them and I have always put down my occasional 10 second delays, if any, to this "feature".

[imilne]

Yeah, my Samsung 2TB drive was a nightmare, even spinning down *during* playback of HD recordings, which then caused an annoying hang for 30 seconds or so. I ended up writing a little program to do nothing but write a few random bytes to it every 3 seconds which keeps the bugger awake.

Iain

[BrettB]

You might want to check the firmware on your harddrive and see if there is a newer version. I've seen some report of these types of drive problems that were fixed with firmware upgrades.

Also, some drives (especially the "green" drives) that will spin themselves down by default can be configured with software from the drive manufacturer to disable that feature. You might want to check that, too.

[cncb]

Maybe because of name resolution, or possibly firewall related.

I think I have figured it out thanks to this suggestion. For some reason, using computer "names" on my network is very slow and sometimes doesn't work at all (I have no idea why). I saw in another thread where you can specify the "serverName" in the configuration file so I changed this to the server's IP address and now the first delete seems to be very quick like all the rest. Thanks for your help.