[RELEASE - BETA] service.datasync

Awesome, now you can start work on storing a copy on Google Drive }=)

I am not able to get this working. I installed the addon on two of my machines. My desktop is a Win7 machine using local Thumbnails with no symlink or pathsubstitution and I set that one up as the server sharing only Thumbnails. The second machine is running openelec with no shared thumbs (just an empty local Thumbnails fodler) and the addon is configured as a client with the IP set the same as my server's IP. The port is set to 8090 which is what the server computer has set in settings>network>services>allow control of XBMC via HTTP>port. I have the Data to Sync set to Thumbnaiils same as the server and the schedule is set to hourly and II set the starting hour and minute to the next closest time and nothing ever seems to happen. One thing that seems a bit odd, is the the Next Run is greyed and only ever reads "Friday, 01 Jan 1971 00:00:00". I'm not sure if that matter.

Nothing shows in a XBMC debug log. Should there be a progress/running indicator or a notification when it starts? Any ideas what's wrong?


I am really looking forward to this addon. Thanks for doing this.

This is a service addon, which are not enabled when installed, you need to reboot both machines before the service will start. I should have put that in the first post, sorry.

Can you try rebooting both (server first) and see what happens.
The first thing that should happen is on the client as soon as you reboot, the next run should be updated to the correct time and date based on the setting you have entered. 1/1/71 is my default date, which will be updated as soon as the add-on runs. The fact that it is still 1/1/71 suggests that the add-on isn't yet running (at least on the client side).

If it still isn't working, please post a debug log from both machines.

I rebooted both machines and now the client PC gives an error on start up saying the script failed. Here are the logs:

Server PC log: http://pastebin.com/Rgqzd9Np

Client PC log: http://pastebin.com/MsMv5HTV

Just wanted to let you know that I think this is great, very useful indeed.

After a quick fix to the error referred to above, the whole thing seems to work without problem.
One thing I've noticed is that shutdown of xbmc seems to take quite a bit of time since I've started using this, but i've not yet tried to figure out why.

Anyway, thanks!

(2012-04-29 21:19)bosel Wrote:  After a quick fix to the error referred to above, the whole thing seems to work without problem.

Are you talking about the error I mentioned? If so, what was the quick fix?

(2012-04-29 21:19)bosel Wrote:  Just wanted to let you know that I think this is great, very useful indeed.

After a quick fix to the error referred to above, the whole thing seems to work without problem.
One thing I've noticed is that shutdown of xbmc seems to take quite a bit of time since I've started using this, but i've not yet tried to figure out why.

Anyway, thanks!

This is probably due to the service sleeping. For some reason, XBMC won't forcibly kill a sleeping thread when it exits. It will wait for the thread to wake, finish and then exit

@RockDawg

I think it was, yes.

Just get the current version:
https://github.com/declankenny/XBMC_datasync

That should stop the script failing

The newer version stops the error message, but now the log says:


I double-checked the config and the IP address is the correct address for my server PC. I have the port number the same as it's set in settings>network>services>allow control of XBMC via HTTP>port on the server PC. That's the correct port number, right?

(2012-04-29 23:28)Bstrdsmkr Wrote:  

(2012-04-29 21:19)bosel Wrote:  Just wanted to let you know that I think this is great, very useful indeed.

After a quick fix to the error referred to above, the whole thing seems to work without problem.
One thing I've noticed is that shutdown of xbmc seems to take quite a bit of time since I've started using this, but i've not yet tried to figure out why.

Anyway, thanks!

This is probably due to the service sleeping. For some reason, XBMC won't forcibly kill a sleeping thread when it exits. It will wait for the thread to wake, finish and then exit

Not sure of the inner workings here, but reducing the amount of a time a thread is sleeping will allow it to check for the xbmc.abortRequested command a lot faster. Many services have the thread sleep time set to 10 seconds or less to avoid hangs when trying to exit. it is especially troublesome when you want to close XBMC and then try to open it but the process hasn't exited yet.

There may be some tweaking that can be done with the sleep times as long as it doesn't disrupt the workings of the script. Based on my quick look it won't affect the clients since they check for a sync time inside of the loop. The server though may be trying to parse the file list each time so there may need to be an extra check in there (similar to the client) if the thread time is decreased to avoid a lot of file IO for no reason. Overall this addon is coming along really well, been working in the few tests I've done.