Getting constant message "An instance of autorestic is already running for this config file" about autorestic HOT 3 CLOSED

Thanks for reporting 😃
I messed up the locking in the last version. Should be fixed in 0.27. Maybe try to delete the .autorestic.lock file in the same folder of your config.

About the notifications:
can you check the path of notify-send? something like which notify-send. And make sure it's included in your cron file?
You already included PATH=/sbin:/bin:/usr/sbin:/usr/bin, but it might be worth a look :)

from autorestic.

Ok, great! I see two .autorestic.lock in my system, one inside my home folder and another in / (/.autorestick.lock), deleting the root one allowed me to run autorestic through anacron. My notify-send is located on /usr/bin and it is already in the PATH settings of anacron. Autorestic is on my /usr/bin path too but I needed to call it from the full path for it to run through anacron. I'll try setting the hook settings in autorestic.yml to the fullpath of notify-send to see if it runs. Thank you!

from autorestic.

Yes, that was another bug in a prior version. It should always take the .atuorestic.yml file next to the actual config.

from autorestic.