I have problems with client synchronization

I am was trying to sync a local folder on the same machine my seafile-server is running on with the seafile-cli client. I used the following command:

seaf-cli sync -l “xxxxx” -s “http://127.0.0.1:8000” -d xxx -u “xxxx”

The client itself generates the error:

Traceback (most recent call last):
File “/usr/bin/seaf-cli”, line 845, in
main()
File “/usr/bin/seaf-cli”, line 841, in main
args.func(args)
File “/usr/bin/seaf-cli”, line 542, in seaf_sync
token = get_token(url, username, password, conf_dir)
File “/usr/bin/seaf-cli”, line 235, in get_token
token_json = urlopen("%s/api2/auth-token/" % url, data=data)
File “/usr/bin/seaf-cli”, line 208, in urlopen
resp = urllib2.urlopen(req)
File “/usr/lib/python2.7/urllib2.py”, line 154, in urlopen
return opener.open(url, data, timeout)
File “/usr/lib/python2.7/urllib2.py”, line 437, in open
response = meth(req, response)
File “/usr/lib/python2.7/urllib2.py”, line 550, in http_response
‘http’, request, response, code, msg, hdrs)
File “/usr/lib/python2.7/urllib2.py”, line 475, in error
return self._call_chain(*args)
File “/usr/lib/python2.7/urllib2.py”, line 409, in _call_chain
result = func(*args)
File “/usr/lib/python2.7/urllib2.py”, line 558, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 500: INTERNAL SERVER ERROR

Could you solve the problem?

I’ve just reported something very similar under https://github.com/haiwen/seafile-client/issues/1348 - but iny my case only syncing on the seafile server works.

@Jonathan As you requested…

You can post this issue on our forum. There should be something wrong on the server side. This is not a bug. Usage problems belongs to the forum.

…in https://github.com/haiwen/seafile-client/issues/1348#issuecomment-801652347 I wanted to add my error report with the issue title…

“seaf-cli sync” reports “urllib2.HTTPError: HTTP Error 500: Internal Server Error”

…here.

Unfortunately my report https://github.com/haiwen/seafile-client/issues/1348 seems to be deleted. May I ask if you have a mail copy of the content (issue 1348)? I think I made a quite elaborated report there and I’m barely in mood to reproduce all steps again.

You should check seahub.log on the server.