Package Details: mozilla-firefox-sync-server-git 1.8.0.r32.gbebd2f3-1

Git Clone URL: https://aur.archlinux.org/mozilla-firefox-sync-server-git.git (read-only, click to copy)
Package Base: mozilla-firefox-sync-server-git
Description: Mozilla Sync Server for built-in Firefox Sync - 1.5+ version for Firefox 29+
Upstream URL: http://docs.services.mozilla.com/howtos/run-sync-1.5.html
Keywords: firefox mozilla sync
Licenses: GPL
Conflicts: mozilla-firefox-sync-server-hg
Submitter: Siosm
Maintainer: None
Last Packager: oi_wtf
Votes: 8
Popularity: 0.000502
First Submitted: 2014-09-08 20:03
Last Updated: 2019-02-07 14:12

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

HLFH commented on 2015-10-25 23:29

Isn't fxa-local-dev the best available package? https://github.com/mozilla/fxa-local-dev

http://math.rousse.me/2015/07/30/how-to-set-up-firefox-sync-self-hosted/

Siosm commented on 2015-07-15 16:40

@simonsd: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

simonsd commented on 2015-07-15 09:11

missing build-depends: binutils make gcc fakeroot

xamindar commented on 2015-07-06 14:58

I can't get this to run as any other user, it will only work as root. Anyone know what I am doing wrong?

xamindar commented on 2015-07-06 07:54

I am getting an error on package installation:

/tmp/alpm_hLLufc/.INSTALL: line 7: systemd-tmpfiles: command not found
error: command failed to execute correctly

Anyone else getting this?

Siosm commented on 2015-06-17 21:13

No, the files in /opt/mozilla-firefox-sync-server should not be owned by the ffsync user.
The error you have here is the result of running it as root in the first place. When run as root, it created those .pyc files that are not part of the package and it cannot use/delete/change them now that you have switched back to running with another user.
I suggest that you delete those files, either by reinstalling the package clean or by hand.
May this serve as a reminder that running something as root is never the solution when something fails.

miscsstic commented on 2015-06-17 20:41

I'm cheking the output of strace ('strace ./local/bin/gunicorn --paste syncserver.ini'), and I see denied permissions on unlink() calls like:

unlink("/opt/mozilla-firefox-sync-server/local/lib/python2.7/site.pyc") = -1 EACCES (Permission denied)

Should the /opt/mozilla-firefox-sync-server be owned by the ffsync user?

miscsstic commented on 2015-06-17 20:01

Here I am (wasn't able to use the same account for AUR4).

So, even with this package (from ARU4), the 'sudo systemctl start ffsync' doesn't work.

Here is the detail of 'systemctl status ffsync' :

* ffsync.service - Gunicorn server running Mozilla's Firefox Sync Server - Version 1.5
Loaded: loaded (/usr/lib/systemd/system/ffsync.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2015-06-17 21:54:36 CEST; 5min ago
Process: 9918 ExecStart=/opt/mozilla-firefox-sync-server/local/bin/gunicorn --paste /opt/mozilla-firefox-sync-server/syncserver.ini (code=exited, status=3)
Main PID: 9918 (code=exited, status=3)

Jun 17 21:54:30 alarm systemd[1]: Started Gunicorn server running Mozilla's Firefox Sync Server - Version 1.5.
Jun 17 21:54:30 alarm systemd[1]: Starting Gunicorn server running Mozilla's Firefox Sync Server - Version 1.5...
Jun 17 21:54:36 alarm systemd[1]: ffsync.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Jun 17 21:54:36 alarm systemd[1]: Unit ffsync.service entered failed state.
Jun 17 21:54:36 alarm systemd[1]: ffsync.service failed.

Is it an hint for you ?

gu1ll0me commented on 2015-01-19 14:37

Thanks for your tip, i will try to find why it connot be run by the ffsync user.

For virtualenv, maybe you could change the Makefile line in prepare()?

VIRTUALENV = virtualenv2 --python=$(SYSTEMPYTHON)

Siosm commented on 2015-01-19 10:47

I'll have a look at the exact python version and depedencies required to run ffsync. I can't just replace python-virtualenv by python-virtualenv2 because the Makefile explicitly calls python-virtualenv. Maybe I should had python2 as deps.

Running ffsync as root as you suggest in your second comment is really bad idea. You should try to understand what problem in your setup is preventing ffsync to work before blindly running it as root.