1:16 a.m.
Greetings,
I've been going back and forth with KeepContacts support in order to get
SyncEvolution working with their service.
We've gotten to the point that a connection can be established, but now
there are other issues that result in a 403 error.
Specifically, in contacting KeepContacts on this round, the reply is:
"I got word from the developer that your client is trying to do a "SyncML
Alert Code Resume Session (225)" which our server does not support. Can
you see if you can trigger a "Slow Sync, SyncML Alert Code Slow Sync
(201)" instead?"
I've briefly searched syncevolution's documentation. But if there is
someone who can adivse here more quickly, that would be very helpful.
Thank you,
Max Pyziur
pyz(a)brama.com
3:01 a.m.
Max Pyziur <pyz(a)brama.com> writes:
Greetings,
I've been going back and forth with KeepContacts support in order to get
SyncEvolution working with their service.
We've gotten to the point that a connection can be established,
What fixed it?
but now there are other issues that result in a 403 error.
Specifically, in contacting KeepContacts on this round, the reply is:
"I got word from the developer that your client is trying to do a "SyncML
Alert Code Resume Session (225)" which our server does not support. Can
you see if you can trigger a "Slow Sync, SyncML Alert Code Slow Sync
(201)" instead?"
I've briefly searched syncevolution's documentation. But if there is
someone who can adivse here more quickly, that would be very helpful.
You don't have any valuable data in the server, right?
Then you can start from scratch with "--sync refresh-from-local", which
will start a new sync session, delete whatever data it finds on the
server, and then send the local data.
"Resume Session" is used when previous sessions were not terminated
properly.
--
Best Regards
Patrick Ohly
9:07 a.m.
On Wed, 19 Jan 2022, Patrick Ohly wrote:
Max Pyziur <pyz(a)brama.com> writes:
> Greetings,
>
> I've been going back and forth with KeepContacts support in order to get
> SyncEvolution working with their service.
>
> We've gotten to the point that a connection can be established,
What fixed it?
I don't recall what was fixed regarding the establishment of a connection.
The next thing that was fixed was a recurring libsoup error.
> but now there are other issues that result in a 403 error.
>
> Specifically, in contacting KeepContacts on this round, the reply is:
> "I got word from the developer that your client is trying to do a "SyncML
> Alert Code Resume Session (225)" which our server does not support. Can
> you see if you can trigger a "Slow Sync, SyncML Alert Code Slow Sync
> (201)" instead?"
>
> I've briefly searched syncevolution's documentation. But if there is
> someone who can adivse here more quickly, that would be very helpful.
You don't have any valuable data in the server, right?
Then you can start from scratch with "--sync refresh-from-local", which
will start a new sync session, delete whatever data it finds on the
server, and then send the local data.
"Resume Session" is used when previous sessions were not terminated
properly.
Running the following command
syncevolution --run --sync refresh-from-local keepcontacts
this is the output that was echoed to the screen
[INFO] calendar: inactive
[INFO] memo: inactive
[INFO] todo: inactive
[INFO] addressbook: starting first time sync from client (peer is server)
[INFO] creating complete data backup of datastore addressbook before sync
(enabled with dumpData and needed for printChanges)
Local data changes to be applied during synchronization:
*** addressbook ***
Comparison was impossible.
[INFO] addressbook: sent 6/1431
[INFO] addressbook: sent 7/1431
[INFO] addressbook: sent 10/1431
[INFO] addressbook: first time sync done unsuccessfully
[ERROR] addressbook: remote, status 400
[INFO] creating complete data backup after sync (enabled with dumpData and
needed for printChanges)
Synchronization failed, see
/home/pyz/.cache/syncevolution/keepcontacts-2022-01-19-17-03/syncevolution-log.html
for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-local, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 1431 before sync, 1431 after it |
| remote, status 400 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Wed Jan 19 17:03:15 2022, duration 0:11min |
| remote, status 400 |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: remote, status 400
Data modified locally during synchronization:
*** addressbook ***
no changes
#####################
these seem to be the relevant lines from the logfile:
–
[2022-01-19 17:03:24.293] 'processStatus' - Processing incoming Status
[--][++] [->end] [->enclosing]
[2022-01-19 17:03:24.293] Started processing Command 'Status'
(incoming MsgID=4, CmdID=5)
[2022-01-19 17:03:24.293] WARNING: RECEIVED NON-OK STATUS 400 for
command 'Add' (outgoing MsgID=4, CmdID=5)
[2022-01-19 17:03:24.293] - SourceRef (localID) =
'pas-id-0bb48ef3ca252ea80c8d07fd720d9818b357a2e6'
[2022-01-19 17:03:24.293] Found matching command 'Add' for Status
[2022-01-19 17:03:24.293] Status: 400: originator exception
–
[2022-01-19 17:03:24.293] 'SessionAbort' - Aborting Session,
Status=400, ProblemSource=REMOTE [--][++] [->end] [->enclosing]
[2022-01-19 17:03:24.293] WARNING: Aborting Session with Reason
Status 400 (REMOTE problem) ***
[2022-01-19 17:03:24.293] --------------- Ignoring all commands in
this message (after 0 sec. request processing, 7 sec. total) with Status
514 (0=none) from here on
–
[2022-01-19 17:03:24.293] 'DSAbort' - Aborting datastore sync,
abortStatusCode=400, localProblem=no, resumable=yes [--][++] [->end]
[->enclosing]
–
[2022-01-19 17:03:24.294] 'SaveSuspendState' - Saving state
for suspend/resume, datastore=addressbook [--][++] [->end] [->enclosing]
+
[2022-01-19 17:03:24.294] 'SaveResumeMarks' - let
implementation save resume info, datastore=addressbook [--][++] [->end]
[->enclosing]
–[2022-01-19 17:03:24.294] End of 'SaveSuspendState' [->top]
[->enclosing]
[2022-01-19 17:03:24.294] *************** Warning: Datastore
flagged aborted (after 0 sec. request processing, 7 sec. total) with
REMOTE Status 400
–[2022-01-19 17:03:24.294] End of 'DSAbort' [->top] [->enclosing]
–[2022-01-19 17:03:24.294] End of 'SessionAbort' [->top] [->enclosing]
[2022-01-19 17:03:24.294] Deleted command 'Add' (outgoing MsgID=4,
CmdID=5)
[2022-01-19 17:03:24.294] Deleted command 'Status' (incoming MsgID=4,
CmdID=5)
–[2022-01-19 17:03:24.294] End of 'processStatus' [->top] [->enclosing]
[2022-01-19 17:03:24.294] addressbook: first time sync done unsuccessfully
[2022-01-19 17:03:24.295] remote, status 400
[2022-01-19 17:03:24.295] closing session
Thank you for help,
Max
7:26 p.m.
Max Pyziur <pyz(a)brama.com> writes:
#####################
these seem to be the relevant lines from the logfile:
–
[2022-01-19 17:03:24.293] 'processStatus' - Processing incoming Status
[--][++] [->end] [->enclosing]
[2022-01-19 17:03:24.293] Started processing Command 'Status'
(incoming MsgID=4, CmdID=5)
[2022-01-19 17:03:24.293] WARNING: RECEIVED NON-OK STATUS 400 for
command 'Add' (outgoing MsgID=4, CmdID=5)
[2022-01-19 17:03:24.293] - SourceRef (localID) =
'pas-id-0bb48ef3ca252ea80c8d07fd720d9818b357a2e6'
[2022-01-19 17:03:24.293] Found matching command 'Add' for Status
[2022-01-19 17:03:24.293] Status: 400: originator exception
As you seem to have KeepContact's attention, perhaps share this log file
with them? Further up there's the message that was sent to the
server. If you ran with a high enough log level, it will contain your
data - this is good for debugging, but beware of your privacy.
My guess is that SyncEvolution sends data that the server doesn't like,
but that's speculation. KeepContacts should know what this 400 status
means.
--
Best Regards
Patrick Ohly
12:58 a.m.
On Thu, 20 Jan 2022, Patrick Ohly wrote:
Max Pyziur <pyz(a)brama.com> writes:
> #####################
>
> these seem to be the relevant lines from the logfile:
>
> –
> [2022-01-19 17:03:24.293] 'processStatus' - Processing incoming Status
> [--][++] [->end] [->enclosing]
>
> [2022-01-19 17:03:24.293] Started processing Command 'Status'
> (incoming MsgID=4, CmdID=5)
> [2022-01-19 17:03:24.293] WARNING: RECEIVED NON-OK STATUS 400 for
> command 'Add' (outgoing MsgID=4, CmdID=5)
> [2022-01-19 17:03:24.293] - SourceRef (localID) =
> 'pas-id-0bb48ef3ca252ea80c8d07fd720d9818b357a2e6'
> [2022-01-19 17:03:24.293] Found matching command 'Add' for Status
> [2022-01-19 17:03:24.293] Status: 400: originator exception
As you seem to have KeepContact's attention, perhaps share this log file
with them? Further up there's the message that was sent to the
server. If you ran with a high enough log level, it will contain your
data - this is good for debugging, but beware of your privacy.
Yes, I shared it.
And I understand the concerns about privacy.
M
My guess is that SyncEvolution sends data that the server doesn't
like,
but that's speculation. KeepContacts should know what this 400 status
means.
241
days inactive
242
days old
syncevolution@syncevolution.org
4 comments
2 participants
participants (2)
-
Max Pyziur -
Patrick Ohly