-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After Dockerimage rebuild Syncserver is no longer sync #200
Comments
Nobody has any ideas? ... |
I seem to have the same issue using Docker, Sync does not work anymore. According to the Docker logs maybe the database structure of an existing installation is not compatible with the recent commits?
|
Sorry, a bunch of us were unavailable last week. The problem is that there was a change to the database and the migration didn't fire for docker. |
No problem, thanks for providing the hint. My instance is running again :) |
I use mariaDB, can this be implemented in the same way? The fix says something about sqlite. Thanks... |
I am also using mariadb, and have run the commands to update linked above to |
Yes, the linked queries should work fine on mariaDB as well as sqlite. |
Well I added the columns and still got the keys_changed error. |
I've added the columns and the syncserver is functioning again, but I still periodically get a related error so I think that adding the columns alone doesn't appear to resolve this entirely. Error below, it may be related to me changing the database password. I'm running via docker so I did try deleting the image outright and re-downloading, but the issue persists: `ERROR:mozsvc:Uncaught exception while processing request: [2020-02-12 20:36:06 +0000] [11] [ERROR] Error handling request /token/1.0/sync/1.5 |
I believe this is the connection between your app and MySQL timing out; you could try upping the connection timeout on the MySQL side and see if that helps. I'm surprised the app doesn't recover from this automatically by taking a fresh connection, but perhaps we don't encounter these under load in production so it's never come up. |
@rfk thanks I took a look and my wait_timeout was set to 600, I set it to the default value for mariadb of 28800. I'll report back if that appears to have resolved it. |
With sqlalchemy you have to specify that you want to have connections recycled after a specific period of time through the connection_pool_recycle parameter during engine creation. |
Sorry, but how can I turn that information into a working sync server? |
I just rebuilt my docker image from Syncserver. But I have to notice that it doesn't sync anymore on my fxa-selfhosting after the rebuild. Anyone have an idea where this could be stuck? It's probably related to the recent commits, I think.
Start I do the image starts like this.
docker run --detach --rm --name sync
--env "SYNCSERVER_PUBLIC_URL=https://fxa.localhorst.home:5000"
--env "SYNCSERVER_SECRET=xxxxxxxxxxxxxxxxxxxx"
--env "SYNCSERVER_SQLURI=pymysql://fxa:[email protected]/syncserver"
--env "SYNCSERVER_IDENTITY_PROVIDER=https://fxa.localhorst.home:3030"
--env "SYNCSERVER_BROWSERID_VERIFIER=https://fxa.localhorst.home:5050/v2"
--env "SYNCSERVER_BATCH_UPLOAD_ENABLED=true"
--env "SYNCSERVER_ALLOW_NEW_USERS=true"
--env "SYNCSERVER_FORCE_WSGI_ENVIRON=true"
--env "REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt"
--add-host="hsp2.localhorst.home:192.168.0.2"
--add-host="fxa.localhorst.home:192.168.0.17"
syncserver:latest
Thanks in advance
The text was updated successfully, but these errors were encountered: