Client Scheduling Failure

[jcole998]

It seems that when I try to schedule a recurring program from a client, the operation never ends and I end up using the Task Manager to end the task. Or maybe I'm just being impatient. The server is a wired desktop and the client is a WiFi laptop.

On which machine do I examine logs to try and figure out what's happening? The server or the client? And which log file?

Thanks.

[sub]

Reproduce the problem, then zip and attach both the client and server logs and I'll take a look.

[jcole998]

Attached are client and server logs from "Not Responding" client window state while trying to use Search with the word "Outpost." I ended the task after waiting for four minutes. It's not the same scenario as originally posted but the symptoms are identical. I'm hoping you may see something.

Action took place about 1:47pm on 7/26/18.

[sub]

If you restart the client and try searching for Outpost again, does it do the same thing? If so, you go away and come back later, does it eventually complete? I know searching can be crappy from the client, due to the way database access is done, and I'm trying to determine if this is what you're seeing.

[jcole998]

Here are the logs of what you asked...if I got it right.

Started the search for "outpost" on the client at 10:23:50am client time on the 27th. After four minutes, killed it with Task Manager. Immediately re-launched NextPVR and again started the same search for "outpost." Walked away and returned at 10:41 to see, for the first time ever(!), a "NextPVR" screen saver! Program was responsive and indeed showed the results of the search. So...

Seems it takes quite a while to search. Can you tell me from the logs how long it took? Which begs the question: Is the search query performed on the client side which means the entire .db3 file needs to be sent from the server? If that's case, maybe a widget of some kind can be shown that helps indicate that NextPVR is alive and kickin' and to be patient.

Thanks for your help on this, sub. Maybe I can return the favor with some client-server SQL work.

(Server logs zip file was too big to upload at 2.39MB. I can post it elsewhere if required.)

[mvallevand]

The Searchlite plugin does use client-server approach for searching and scheduling if you are looking for existing solutions.

Martin

[sub]

Is the search query performed on the client side which means the entire .db3 file needs to be sent from the server?

Yeah, that's pretty much the case. The client queries the database directly. For most stuff this works great, using indexes to quickly find the data it needs. Unfortunately when you're doing searches, that is not the case. SQLite isn't a client/server database, so you're left sitting there for a long time as performs a huge number of slow network file operations as it searches for the matching shows.

I've been meaning to do something about this for a long time though, so try the attached updates. You need to install these on both the client and the server.

[jcole998]

Um...Can I assume that trying these files won't break anything? If it doesn't work, I can just go back to the original files?

[sub]

Sure you can backup those files if you want. It was a pretty isolated change though, so I don't think you'd have unrelated problems.

[JavaWiz]

If the client is a windows machine, another option may be to use NLite rather than NextPVR running in client mode. The search will only be done on the server, the client only displays the UI...