Error starting a new run after stopping the previous on - Lock is on

[AlainCh2]

No idea why to-day is so error prone.

I stopped the previous run.... excluded a Problematic directory, then launched it again.

No way to get rid of the error
a) stopped then manually delete both files in sending and receiving directory.
b) checked computer date/time

Lost me completely.

Alain

[Plerry]

See the FFS Manual section on Expert Settings for an explanation on the LockDirectoriesDuringSync flag and *.ffs_lock files.
After having completed a sync, FFS removes the *.ffs_lock file it has created.
If you abort an FFS job in an unregular fashion, that FFS instance is not able to remove the *.ffs_lock file it created when starting the job, and keeps the sync location locked.
At least as admin-user you should normally be able to delete any remnant *.ffs_lock files.
You may, after careful consideration, possibly even conclude that for your use case, you can safely set the LockDirectoriesDuringSync flag to False.

[AlainCh2]

Ok, Thanks !!!
---- just a short answer:
If I use (STOP) I expect FFS will delete it's own lock.
That maybe didn't happen, but not sure. see below.

I then deleted manually BOTH locks.
Relaunching the same job will created the two .locks, (correctly I supposed)
then went in "error waiting for locks"
- did three time with same results.

Started testing without a proper clue, but 40 years in IT helps.

Solved using this tecnique (after 4 different unsuccessful tests)

1) Delete manually Both .locks files
-(sending & receiving dir)
2) Deleted all the job in FFS & also current one
- (if you leave them. and do the other steps. it'll never works)
3) Closed FFS & checked no other instances were running
- (never found other instance)
4) Re.launched FFS - it finally started clean with no job
5) opened my .Batch
6) Launched it
- worked as expected

It may be some spurious where creating the .locks and the main finding them stopped.

Hope it help

Alain

[MonicaMarike]

Hello Alain,

We have deleted all .lock files manually but we have no idea how to delete all jobs in FFS. Could you help us with this?

[AlainCh2]

Select one in this area,
hit Canc

Done

Alain

[MonicaMarike]

Hi Alain,

We have tried several times but we can't select anything in that area. The only thing I can do is double click on last session, that gives me an error message. Clicking one time doesn't do anything. How did you select last session?

[xCSxXenon]

Also, that lock is created by SYSTEM, and you definitely aren't running FFS as SYSTEM while in the GUI. Do you have a scheduled task? If that is creating the LOCK files and getting stuck, or taking a long time, or crashing, it will cause what you have described. I'm guessing since you deleted the config files, the task can't actually run, so the LOCK files don't get created, thus no more problem. I would bet your event viewer shows a bunch of failed tasks though.

Monica, click the [Last session] once, then {DEL} on your keyboard. That removes it. It wouldn't solve this problem though

[AlainCh2]

@ Monica

Hahaaha..
I'm still laughing by myself- I usually do "screenShot"
NEVER DONE A "ScreenVid"" hahahaha

(I did it FOR YOU !!!)

Cannot attach it - too large-
Please check the link and report back if it works!!
Thanks
Alain

https://www.dropbox.com/s/kqsqdhxpbp5bjt6/2020-08-02%2017.31.11.mp4?dl=0

@Xenon

Yes, correct
FFs is managed twice a day by a timed event in taskmgr (11:50 - 18:45)

now its 10 days it doesnt run anymore .. need to check why.

There are errors on the PostLog bat file not executing also

no idea Right now.
I'll update later

Alain

[MonicaMarike]

Thanks so much for your video! We managed to delete the last session finally, but after closing the program and opening again the last session is back. We have tried several times. So it doesn't seem to start clear with no job. I guess this means it still won't work?

[AlainCh2]

@monica
hmmm.
do you launch FFs (1)

2020-08-03 00 28 03.jpg (15.3 KiB) Viewed 2130 times

or
do you launch a Batch (2)

2020-08-03 00 28 51.jpg (22.13 KiB) Viewed 2130 times

or a Job???

For me after deleting last job, and closing FFs, when I reopen it there is nothing.(3)

2020-08-03 00 30 00.jpg (79.05 KiB) Viewed 2130 times

Last session as you can see contains las run data

[hermanthemexican]

I apologize but clearly this is way out of my league.
I have encountered problems trying to run a backup that ended with error messages.

The error message I get now is:
Cannot set directory locks for the following folders:

Cannot write file "/Volumes/El 6/sync.ffs_lock".
EACCES: Permission denied [open]

Cannot write file "/Volumes/El ocho/sync.ffs_lock".
EACCES: Permission denied [open]

Please help with any information to understand what I can do to remove the sync.ffs_lock files, I can not find where they live. I am running Catalina on a MacMini.

Many thanks,
Germán

[AlainCh2]

"I am running Catalina on a MacMini."

Hello Herman
can you tell me what is it?

Is that you are trying to run a batch job?

Alain

[hermanthemexican]

Hello Alain,

Good morning. Yes, I am backing up a removable drive to another USB drive.
Here is the capture of the message I get.
Also, my experience as a forum user is very limited so bare with me.
Many thanks.

[Plerry]

The first warning and the errors seem sufficiently clear:
The user under which credentials FFS is trying to run the sync does not have write access to the directories "/Volumes/EI 6" and "/Volumes/EI ocho" involved in the sync.
You need to fix that in one way or another.

If "/Volumes/EI ocho" is still mostly empty, the second warning ("The following folders are significantly different") is correct and may then be safely be ignored.

[MonicaMarike]

Thanks Alain, we managed to get it working again without any problems!

[AlainCh2]

Great news !!

Happy Life !1!

[hermanthemexican]

Thank you for your feedback.

I know Catalina, the new mac OS has added levels of security, creating all kinds of problems.

The user under which credentials FFS is trying to run the sync does not have write access to the directories

I believe I did have access to the drives.
I have granted FFS permissions to access my disk, also made sure drive permissions are correctly set.
When I try to run a new backup job, unsuccessfully, here is what I get.

Any suggestions?
Thank you.

[AlainCh2]

I see a big problem here Herman...
...I know nothing of Apple world.

I run away from them, years ago.
To much ... "do it my way" :-D

So I'm afraid I cannot be myself of any help on this issue,
but may be somebody will be!!

[hermanthemexican]

Thank you Alain, I appreciate your help.

Maybe someone else will comment!

[therube]

Recent mention of "dot" directories, maybe that, Can sync dot-prefixed (invisible) directory, but not files, except inside directory...?