what to do when remote service hangs?

[Robert]

I was running multiple profiles doing binary comparison on network drives using MD5 checksums.

One of the profiles got stuck waiting for the remote service to provide an MD5.

I tried without success:
- pausing and un-pausing the stuck profile
- stopping and restarting the stuck profile
- deleting the *$$$.* request files on the stuck drive

I did not want to reboot the server because several profiles were midway on 12+ hour jobs.

Is there anything I can do to fix a stuck remote service other than rebooting the server?

[tobias]

Hello,
yes, you can stop and restart the service from the service control panel.

However if it is busy and still successfully processing other requests, I would probably prefer to wait until these other jobs are finished.

[Robert]

Thank you.

Is the occasional stuck remote service a known problem or do you think I did something wrong to cause it?

[tobias]

Hi,
no, it's not a known problem. Do you have the latest remote service v10.06?

In general I wouldn't run too many jobs simultaneously if they use remotely generated MD5s. That's quite a task to accomplish. Try to keep the load low.

Also make sure Syncovery "Remembers Results". The checkmark is chosen by default. It will prevent re-comparing the same files over and over.

[Robert]

Thanks, I am running 10.06.

My strategy is to back up my data daily with profiles that do not do a binary comparison.

About twice a year I run profiles that do binary comparisons to confirm there are no hardware problems with my drives. I don't use the remember option because I want every file to be read.

I'll try running fewer profiles simultaneously in the future.