gphotos-sync: Unable to sync photos

Hello, Thank you very much for your plugin which is exactly what I was looking for. Sorry, I am a novice, but I can’t get the sync to work.

I’m using a Synlogy NAS and I did manage to install the container on Docker which is working. The application is well created on the Google side and is published. Unfortunately, I can’t synchronize.

I run the commands in SSH from my Mac. 1st error when I try to synchronize using the command line: a message said “Database is locked”.

I then deleted the gphotos.lock file in /storage and ran the command line again.

Here is the second error: 02-20 19:33:30 WARNING gphotos-sync 3.0.3 2023-02-20 19:33:30.699715 02-20 19:33:30 ERROR Process failed. Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/gphotos_sync/Main.py", line 496, in main self.setup(args, db_path) File "/usr/lib/python3.9/site-packages/gphotos_sync/Main.py", line 345, in setup self.auth.authorize() File "/usr/lib/python3.9/site-packages/gphotos_sync/authorize.py", line 96, in authorize flow.run_local_server(open_browser=False, host=self.host, port=self.port) File "/usr/lib/python3.9/site-packages/google_auth_oauthlib/flow.py", line 425, in run_local_server local_server = wsgiref.simple_server.make_server( File "/usr/lib/python3.9/wsgiref/simple_server.py", line 154, in make_server server = server_class((host, port), handler_class) File "/usr/lib/python3.9/socketserver.py", line 452, in __init__ self.server_bind() File "/usr/lib/python3.9/wsgiref/simple_server.py", line 50, in server_bind HTTPServer.server_bind(self) File "/usr/lib/python3.9/http/server.py", line 137, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/lib/python3.9/socketserver.py", line 466, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address in use 02-20 19:33:30 WARNING Done.

Could you tell me what I can do to fix this?

Many thanks for your work, F.

About this issue

Original URL
State: closed
Created a year ago
Comments: 20 (11 by maintainers)

Most upvoted comments

Good question!

flush index deletes the index completely and rebuilds it
rescan just resets the last scanned date to the beginning of time. Normal scans only ask Google to tell them about files added since the last scan and therefore can be pretty quick on large libraries.

The differences are:

rescan will not delete any existing files from the DB that have been deleted in your library. Flush index will because the DB is started again from scratch.
therefore you need to use --flush-index with --do-delete AFAIR

gilesknap on Aug 29, 2023