OHAI dearest of mozilla devs, I lift my hat for your sheer existence. :) I have this weird behavior @ ff syncserver 1.5. Just installed it on my gentoo machine via a dockerfile on a gentoo docker container. The Dockerfile itself is pretty straightforward:
####################################################################### FROM doertedev/www # (just a plain nginx installation) MAINTAINER doerteDev <[email protected]> RUN eselect python set python2.7 && \ echo "PYTHON_TARGETS=\"python2_7\"" >> /etc/portage/make.conf RUN emerge --ask=n -q -j2 dev-python/virtualenv \ dev-db/sqlite \ net-misc/memcached RUN echo ">=dev-lang/python-2.7.5 sqlite" >> /etc/portage/package.use && \ emerge --ask=n -q -j2 =dev-lang/python-2.7.6 RUN git clone https://github.com/mozilla-services/syncserver /root/syncserver RUN cd /root/syncserver/ && make build COPY ./syncserver.ini /root/syncserver/syncserver.ini RUN ln -s /etc/nginx/sites-available/syncserver.conf /etc/nginx/sites-enabled/syncserver.conf VOLUME ["/root/syncserver/share"] EXPOSE 443 ###################################################################### As you can see, nothing special. As is the syncserver.ini: [app:main] use = egg:syncserver [syncserver] public_url = http://127.0.0.1:5000/ secret=asdfsecurestringtrolololTGIF sqlurl = sqlite:////root/syncserver/syncserver.db allow_new_users = true [server:main] use = egg:gunicorn host = 127.0.0.1 port = 5000 workers = 2 timeout = 60 I picked this syncserver.db file because you already delivered it with the required schema. Now I updated the services.sync.tokenServerURI accordingly, didn't forget to add a /token/1.0/sync/1.5 to the URl, which gave me following strange behaviour: Manually opening a tab with this exact url gives me the following string on the browser: {"status": "error", "errors": [{"location": "body", "name": "", "description": "Unauthorized"}]} And sadly the schema stays the only thing existing in the syncserver.db file. The URl GET call is being logged @ STDOUT: INFO:mozsvc.metrics:{"code": 200, "request_time": 0.0006010532379150391, "remoteAddressChain": ["10.8.0.1", "127.0.0.1"], "agent": "Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0", "path": "https://url:port/token/1.0/sync/1.5";, "method": "GET"} But then nothing happens, when I manually start syncing. I asked in irc://irc.mozilla.org/#sync and a nice guy called "callahad" told me to :%s,INFO,DEBUG, line 80 in __INIT__.py, which only changed the output of the inital make serve command, but nothing more, nothing less. Since the GET calls land @ STDOUT I don't think this is an issue of the nginx but rather the syncserver.ini. Since I copied the nginx config from https://docs.services.mozilla.com/howtos/run-sync-1.5.html ... Could it be that the sync proccess can somehow ... have a problem with self signed SSL Certificates? Or is there some way to get any debug messages from the syncing client? Thanks in advance, any response is appreciated, since my python mojo is close to non-existing and I'd like to know where I failed :) Greetings from southern Germany. -- Mit freundlichen Grüßen Com - Systems - Internet Stefan Staudenmeyer Hauptstraße 40 74248 Ellhofen Tel: 07134/915973 Fax: 07134/915974 E- Mail: [email protected] http://www.csiweb.de _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
