Skip to content
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

CRITICAL] Exception (Code: 200, Reason: OK) while syncing profile #91

Open
unhammer opened this issue Jan 16, 2016 · 8 comments
Open

CRITICAL] Exception (Code: 200, Reason: OK) while syncing profile #91

unhammer opened this issue Jan 16, 2016 · 8 comments

Comments

@unhammer
Copy link

I'm getting a crash with this at the end of my logs:

INFO:root:=====================================================
[22:03:14.388     INFO] =====================================================
INFO:root:   Synching Deleted bb entries to cd
[22:03:14.388     INFO]    Synching Deleted bb entries to cd
INFO:root:=====================================================
[22:03:14.388     INFO] =====================================================
INFO:root:No deleted entries that need to be synched.
[22:03:14.388     INFO] No deleted entries that need to be synched.
INFO:root:=====================================================
[22:03:14.388     INFO] =====================================================
INFO:root:   Sending New cd entries to bb
[22:03:14.388     INFO]    Sending New cd entries to bb
INFO:root:=====================================================
[22:03:14.389     INFO] =====================================================
INFO:root:2 new entries to be synched.
[22:03:14.389     INFO] 2 new entries to be synched.
DEBUG:root:Sending Request URL: /owncloud/remote.php/carddav/addressbooks/unhammer/contacts/    Method: REPORT
DEBUG:root:Received Response: HTTP/1.1 200 OK

CRITICAL:root:Exception (Code: 200, Reason: OK) while syncing profile bbown
[22:03:14.744 CRITICAL] Exception (Code: 200, Reason: OK) while syncing profile bbown
CRITICAL:root:Traceback (most recent call last):
  File "/home/unhammer/src/ASynK/asynk/asynk_core.py", line 397, in op_sync
    result = sync.sync(self.get_sync_dir())
  File "/home/unhammer/src/ASynK/asynk/sync.py", line 300, in sync
    ret2 = sl2.sync_to_folder(self.get_f1())
  File "/home/unhammer/src/ASynK/asynk/sync.py", line 498, in sync_to_folder
    res1 = self.send_news_to_folder(df)
  File "/home/unhammer/src/ASynK/asynk/sync.py", line 444, in send_news_to_folder
    items = self.fold.find_items(self.get_news())
  File "/home/unhammer/src/ASynK/asynk/folder_cd.py", line 173, in find_items
    (davxml.getetag, carddavxml.address_data))
  File "/home/unhammer/src/ASynK/lib/caldavclientlibrary/client/clientsession.py", line 630, in multiGet
    self.handleHTTPError(request)
  File "/home/unhammer/src/ASynK/lib/caldavclientlibrary/client/clientsession.py", line 959, in handleHTTPError
    request.getStatusReason()))
HTTPError: Code: 200, Reason: OK

[22:03:14.764 CRITICAL] Traceback (most recent call last):
  File "/home/unhammer/src/ASynK/asynk/asynk_core.py", line 397, in op_sync
    result = sync.sync(self.get_sync_dir())
  File "/home/unhammer/src/ASynK/asynk/sync.py", line 300, in sync
    ret2 = sl2.sync_to_folder(self.get_f1())
  File "/home/unhammer/src/ASynK/asynk/sync.py", line 498, in sync_to_folder
    res1 = self.send_news_to_folder(df)
  File "/home/unhammer/src/ASynK/asynk/sync.py", line 444, in send_news_to_folder
    items = self.fold.find_items(self.get_news())
  File "/home/unhammer/src/ASynK/asynk/folder_cd.py", line 173, in find_items
    (davxml.getetag, carddavxml.address_data))
  File "/home/unhammer/src/ASynK/lib/caldavclientlibrary/client/clientsession.py", line 630, in multiGet
    self.handleHTTPError(request)
  File "/home/unhammer/src/ASynK/lib/caldavclientlibrary/client/clientsession.py", line 959, in handleHTTPError
    request.getStatusReason()))
HTTPError: Code: 200, Reason: OK

A 200 response giving a crash seems a bit confusing.

Also, it seems like there are two loggers going at once.

This is at 39a684c, syncing bbdb towards owncloud.

@skarra
Copy link
Owner

skarra commented Feb 22, 2016

Sorry about the problem, and the delay in my response. Were you able to make any headway or are you still facing this issue?

Exception with 200 status is weird indeed; unfortunately it's in one of the underlying libraries (from Apple, no less) that has this code. If you are still stuck, I will take a look. I will need more detailed logs that can be turned on by setting config['db_config']['cd']['log'] = True in your ~/.asynk/config.py

@unhammer
Copy link
Author

that was a lot of output … http://sprunge.us/BXhJ is a slightly sanitised version of the end of it; do you want me to email you the whole thing?

@unhammer
Copy link
Author

Also, it seems to sync in the bbdb→carddav direction (but not other way), but tries to sync the same entries each time, as if it forgot that it did it last time.

@skarra
Copy link
Owner

skarra commented Mar 23, 2016

The full dump would be helpful. Please email it to me.

@unhammer
Copy link
Author

did you get the email?

@skarra
Copy link
Owner

skarra commented Apr 2, 2016

Yes, I got it; but I am traveling on work now and unable to look into it
just yet.

On Thu, Mar 31, 2016 at 2:59 AM, Kevin Brubeck Unhammer <
notifications@github.com> wrote:

did you get the email?


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#91 (comment)

@unhammer
Copy link
Author

unhammer commented Apr 7, 2016

After updating to owncloud 9.0.0-1 (contacts 2:1.1.0.0-2), they changed among other things the url (/carddav/ turned into /dav/), which suddenly gave a 404. I fixed the url in state.json, and now it seems to be updating fine. Presumably they changed other things as well with their dav.

There may still be some bug in asynk ("ok" leading to error doesn't sound right :)) but I'm not seeing it any longer.

@skarra
Copy link
Owner

skarra commented Apr 28, 2016

Kevin, interesting. Thanks for reporting this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants