5 a.m.
Seeing a consistent failure after upgrade to Ubuntu Karmic Koala (Version .9)
Major error: http://my.funambol.com/sync via libsoup: Cannot connect to
destination
I've seen some references to libsoup and SSL, but thought that this was a compiling
problem. Any suggestions?
If you want the full dump, let me know where. I don't want to spam the list.
Jim
[2009-10-30 13:34:42.256] End of 'SyncML_Outgoing' [->top]
* [2009-10-30 13:37:51.250] TransportException thrown
at /work/runtests/head/syncevolution/src/core/SoupTransportAgent.cpp:161
*
* [2009-10-30 13:37:51.250] http://my.funambol.com/sync via
libsoup: Cannot connect to destination
*
* –[2009-10-30 13:37:51.250] 'SessionAbort' - Aborting Session,
Status=20017, ProblemSource=LOCAL [--][++] [->end]
* [2009-10-30 13:37:51.250] WARNING: Aborting Session with
Reason Status 20017 (LOCAL problem) ***
* [2009-10-30 13:37:51.250] --------------- Ignoring all
commands in this message (after 188 sec. request
processing, 188 sec. total) with Status 514 (0=none)
from here on
* –[2009-10-30 13:37:51.250] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.250] 'SaveSuspendState' -
Saving state for
suspend/resume [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.250]
'SaveAdminData' - Saving changelog,
target and map
info [--][++] [->end] [->enclosing]
–[2009-10-30 13:37:51.250] End of
'SaveAdminData' [->top] [->enclosing]
–[2009-10-30 13:37:51.250] End of
'SaveSuspendState' [->top] [->enclosing]
* [2009-10-30 13:37:51.250] ***************
Warning: Datastore flagged aborted (after 188
sec. request processing, 188 sec. total) with
LOCAL Status 20017
–[2009-10-30 13:37:51.250] End of
'DSAbort' [->top] [->enclosing]
* –[2009-10-30 13:37:51.250] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.251] 'SaveSuspendState' -
Saving state for
suspend/resume [--][++] [->end] [->enclosing]
* –[2009-10-30 13:37:51.251]
'SaveAdminData' - Saving changelog,
target and map
info [--][++] [->end] [->enclosing]
–[2009-10-30 13:37:51.251] End of
'SaveAdminData' [->top] [->enclosing]
–[2009-10-30 13:37:51.251] End of
'SaveSuspendState' [->top] [->enclosing]
* [2009-10-30 13:37:51.251] ***************
Warning: Datastore flagged aborted (after 189
sec. request processing, 189 sec. total) with
LOCAL Status 20017
–[2009-10-30 13:37:51.251] End of
'DSAbort' [->top] [->enclosing]
* +[2009-10-30 13:37:51.251] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
* +[2009-10-30 13:37:51.251] 'DSAbort' - Aborting
datastore sync, abortStatusCode=20017, localProblem=yes,
resumable=yes [--][++] [->end] [->enclosing]
–[2009-10-30 13:37:51.252] End of 'SessionAbort'
6:04 a.m.
Jim Rorie <jfrorie@...> writes:
Seeing a consistent failure after upgrade to Ubuntu Karmic Koala (Version .9)
Major error: http://my.funambol.com/sync via libsoup: Cannot connect to
destination
I've seen some references to libsoup and SSL, but thought that this was a
compiling problem. Any suggestions?
I've been having the same problem since 2009-10-20 on Fedora 10 w/ SyncEvolution
0.9.1beta[12]. It still worked fine with SyncEvolution 0.9.1beta1 as of
2009-10-10. I don't think it's a problem w/ SyncEvolution, I think there's a
problem w/ the myFunambol server.
-Richard
6:23 a.m.
Richard Calmbach <rcalmbac@...> writes:
Jim Rorie <jfrorie@...> writes:
0.9.1beta[12]. It still worked fine with SyncEvolution 0.9.1beta1 as
of
2009-10-10. I don't think it's a problem w/ SyncEvolution, I think there's a
problem w/ the myFunambol server.
-Richard
I'm starting to think otherwise. My blackberry is syncing fine as is my
Outlook connector.
Me thinks that something locally changed recently that boinked us. Were
there any recent config file changes?
6:52 p.m.
On Mon, 2009-11-02 at 19:23 +0000, Jim Rorie wrote:
Richard Calmbach <rcalmbac@...> writes:
>
> Jim Rorie <jfrorie@...> writes:
>
> 0.9.1beta[12]. It still worked fine with SyncEvolution 0.9.1beta1 as of
> 2009-10-10. I don't think it's a problem w/ SyncEvolution, I think
there's a
> problem w/ the myFunambol server.
>
> -Richard
>
I'm starting to think otherwise. My blackberry is syncing fine as is my
Outlook connector.
The my.funambol.com server seems to have load problems. Right now,
pointing my web browser to http://my.funambol.com/sync took several
minutes to show the server version information.
Me thinks that something locally changed recently that boinked us.
Were
there any recent config file changes?
Not between beta 1 and beta 2.
If you are unsure, then fire up Wireshark and do a network dump of eth0
with filter "host my.funambol.com" while you try to run a sync. That
should show whether it is a low-level network problem.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
7:32 p.m.
On Fri, 2009-10-30 at 19:04 +0000, Richard Calmbach wrote:
I've been having the same problem since 2009-10-20 on Fedora 10
w/ SyncEvolution
0.9.1beta[12]. It still worked fine with SyncEvolution 0.9.1beta1 as of
2009-10-10. I don't think it's a problem w/ SyncEvolution, I think there's a
problem w/ the myFunambol server.
I've seen some users having problems after the upgrade to karmic because
of something different in IPv6 support, especially related to Firefox.
Can this be your case too?
/stef
--
Funambol :: Open Source Mobile Cloud Sync and Push Email
Community manager :: https://www.forge.funambol.org
Follow the tweets: http://twitter.com/funambol
Funambol Identi.ca group: http://identi.ca/group/funambol
3:41 a.m.
Bingo. It's Ipv6. I just turned it off and sync is now connecting.
On Tue, 2009-11-03 at 09:32 +0100, Stefano Maffulli wrote:
I've seen some users having problems after the upgrade to karmic
because
of something different in IPv6 support, especially related to Firefox.
Can this be your case too?
/stef
4:06 a.m.
On Tue, 2009-11-03 at 16:41 +0000, Jim Rorie wrote:
Bingo. It's Ipv6. I just turned it off and sync is now
connecting.
How did you turn it off?
SyncEvolution doesn't handle IPv4 or IPv6 itself. That's all done by
libsoup. If it's broken for SyncEvolution, it's also broken for lots of
other apps.
Ubuntu now has a native package for SyncEvolution. Can you reproduce it
using that package? In any case, can you file a bug with Ubuntu?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
4:15 a.m.
By adding
ipv6.disable=1
to the grub boot line and rebooting.
I'm using the native package.
--
Jim Rorie
jfrorie(a)gmail.com
http://www.unconventional-wisdom.org
IM: jfrorie (XMPP/GoogleTalk)
There are 4 boxes to use in the defense of liberty:
Soap, Ballot, Jury, Ammo. Use in that order.
On Tue, 2009-11-03 at 18:06 +0100, Patrick Ohly wrote:
On Tue, 2009-11-03 at 16:41 +0000, Jim Rorie wrote:
> Bingo. It's Ipv6. I just turned it off and sync is now connecting.
How did you turn it off?
SyncEvolution doesn't handle IPv4 or IPv6 itself. That's all done by
libsoup. If it's broken for SyncEvolution, it's also broken for lots of
other apps.
Ubuntu now has a native package for SyncEvolution. Can you reproduce it
using that package? In any case, can you file a bug with Ubuntu?
4:36 a.m.
Alright, logged at:
https://bugs.launchpad.net/libsoup/+bug/473042
which has this upstream libsoup bug link I created as well.
BTW, I noticed with ipv6 turned off, firefox is faster. Placebo effect?
I think not...
--
Jim Rorie
jfrorie(a)gmail.com
http://www.unconventional-wisdom.org
IM: jfrorie (XMPP/GoogleTalk)
There are 4 boxes to use in the defense of liberty:
Soap, Ballot, Jury, Ammo. Use in that order.
On Tue, 2009-11-03 at 18:06 +0100, Patrick Ohly wrote:
On Tue, 2009-11-03 at 16:41 +0000, Jim Rorie wrote:
> Bingo. It's Ipv6. I just turned it off and sync is now connecting.
How did you turn it off?
SyncEvolution doesn't handle IPv4 or IPv6 itself. That's all done by
libsoup. If it's broken for SyncEvolution, it's also broken for lots of
other apps.
Ubuntu now has a native package for SyncEvolution. Can you reproduce it
using that package? In any case, can you file a bug with Ubuntu?
5:10 a.m.
On Tue, Nov 3, 2009 at 12:32 AM, Stefano Maffulli <maffulli(a)funambol.com> wrote:
On Fri, 2009-10-30 at 19:04 +0000, Richard Calmbach wrote:
> I've been having the same problem since 2009-10-20 on Fedora 10 w/ SyncEvolution
> 0.9.1beta[12]. It still worked fine with SyncEvolution 0.9.1beta1 as of
> 2009-10-10. I don't think it's a problem w/ SyncEvolution, I think
there's a
> problem w/ the myFunambol server.
I've seen some users having problems after the upgrade to karmic because
of something different in IPv6 support, especially related to Firefox.
Can this be your case too?
I just did a successful refresh-from-client sync with myFunambol.
@Jim: The only diffs between my beta1 and beta2 config files are in
comments, so no functional differences.
For completeness, below is the output of the *failed* sync run from
2009-10-30. Jim and I may have experienced sync failure for different
reasons. In my case it's most likely a transient issue w/ the
myFunambol server. I've had no networking related changes on my end.
-Richard
syncevolution output of failed run:
Local data changes to be applied to server during synchronization:
*** addressbook ***
no changes
*** memo ***
no changes
*** todo ***
no changes
*** calendar ***
no changes
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] SyncContext: resend previous request #1
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] SyncContext: resend previous request #2
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] SyncContext: resend previous request #3
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup:
Cannot connect to destination
[INFO] SyncContext: resend previous request #4
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup:
Cannot connect to destination
[INFO] SyncContext: resend previous request #5
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] Transport giving up after 5 retries and 6:00min
[ERROR] timeout, retry period exceeded
[INFO] addressbook: first time sync done unsuccessfully
[INFO] memo: first time sync done unsuccessfully
[INFO] todo: first time sync done unsuccessfully
[INFO] calendar: first time sync done unsuccessfully
Synchronization failed, see
/export/home/richard/.cache/syncevolution/myfunambol-rc-2009-10-30-09-46/sysynclib_linux.html
for details.
Changes applied during synchronization:
+---------------|-------ON CLIENT-------|-------ON SERVER-------|-CON-+
| | rejected / total | rejected / total | FLI |
| Source | NEW | MOD | DEL | NEW | MOD | DEL | CTS |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| addressbook | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 403 before sync, 403 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| calendar | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 169 before sync, 169 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| memo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 6 before sync, 6 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| todo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 2 before sync, 2 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| start Fri Oct 30 09:46:25 2009, duration 6:05min |
| synchronization failed (status code 20043) |
+---------------+-------+-------+-------+-------+-------+-------+-----+
Changes applied to client during synchronization:
*** addressbook ***
no changes
*** memo ***
no changes
*** todo ***
no changes
*** calendar ***
no changes
7:05 a.m.
Based on the canceled errors, I'd say they were different. Mine is
definitely an IPv6 issue. Confirmed upstream in gnome. Apparently
there is a voodoo glibc version packaged in Ubuntu.
On Tue, 2009-11-03 at 10:10 -0800, Richard Calmbach wrote:
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] SyncContext: resend previous request #1
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] SyncContext: resend previous request #2
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] SyncContext: resend previous request #3
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup:
Cannot connect to destination
[INFO] SyncContext: resend previous request #4
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup:
Cannot connect to destination
[INFO] SyncContext: resend previous request #5
[INFO] Transport timeout after 1:00min
[INFO] SoupTransport Failure: http://my.funambol.com/sync via libsoup: Cancelled
[INFO] Transport giving up after 5 retries and 6:00min
[ERROR] timeout, retry period exceeded
[INFO] addressbook: first time sync done unsuccessfully
[INFO] memo: first time sync done unsuccessfully
[INFO] todo: first time sync done unsuccessfully
[INFO] calendar: first time sync done unsuccessfully
Synchronization failed, see
/export/home/richard/.cache/syncevolution/myfunambol-rc-2009-10-30-09-46/sysynclib_linux.html
for details.
Changes applied during synchronization:
+---------------|-------ON CLIENT-------|-------ON SERVER-------|-CON-+
| | rejected / total | rejected / total | FLI |
| Source | NEW | MOD | DEL | NEW | MOD | DEL | CTS |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| addressbook | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 403 before sync, 403 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| calendar | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 169 before sync, 169 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| memo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 6 before sync, 6 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| todo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| item(s) in database backup: 2 before sync, 2 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| start Fri Oct 30 09:46:25 2009, duration 6:05min |
| synchronization failed (status code 20043) |
+---------------+-------+-------+-------+-------+-------+-------+-----+
Changes applied to client during synchronization:
*** addressbook ***
no changes
*** memo ***
no changes
*** todo ***
no changes
*** calendar ***
no changes
_______________________________________________
SyncEvolution mailing list
SyncEvolution(a)syncevolution.org
http://lists.syncevolution.org/listinfo/syncevolution
8:07 a.m.
On Tue, 2009-11-03 at 18:10 +0000, Richard Calmbach wrote:
For completeness, below is the output of the *failed* sync run from
2009-10-30. Jim and I may have experienced sync failure for different
reasons. In my case it's most likely a transient issue w/ the
myFunambol server.
Agreed. What you got is an unresponsive server which doesn't reply to
the TCP connection request or SyncML message within 1 minute, causing
SyncEvolution to resend. The issue that Jim had shows up as a real
problem detected by libsoup.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
4702
days inactive
4706
days old
syncevolution@synevolution.org
11 comments
4 participants
participants (4)
-
Jim Rorie -
Patrick Ohly -
Richard Calmbach -
Stefano Maffulli