Re: unresolvable lost pulled message leading to timeout

2019-01-04 Thread Oswald Buddenhagen
On Thu, Jan 03, 2019 at 06:38:12PM -0700, Benjamin Slade wrote: > On 2019-01-03T16:33:11-0700, Oswald Buddenhagen > wrote: > > On Thu, Jan 03, 2019 at 03:45:24PM -0700, Benjamin Slade wrote: > > > I'm having trouble with a lost pulled message leading to a timeout: > > > [...] > > > What is th

Re: unresolvable lost pulled message leading to timeout

2019-01-04 Thread Benjamin Slade
On 2019-01-04T03:24:26-0700, Oswald Buddenhagen wrote: > On Thu, Jan 03, 2019 at 06:38:12PM -0700, Benjamin Slade wrote: > > That was what seemed to the relevant part of the `-D` output. > > > > Do you think the entirety of the `-D` would be useful? > > > the network activity prior to th

[commit] 1.3: fix formatting of uint in callback debug stubs

2019-01-04 Thread Oswald Buddenhagen via isync-devel
commit b72800944c4b81024d30c5395de1ff4565273463 Author: Oswald Buddenhagen Date: Sat Jan 5 00:00:10 2019 +0100 fix formatting of uint in callback debug stubs amends bb632d1c. src/drv_proxy_gen.pl | 1 + 1 file changed, 1 insertion(+) diff --git a/src/drv_proxy_gen.pl b/src/drv_p

Re: unresolvable lost pulled message leading to timeout

2019-01-04 Thread Oswald Buddenhagen
On Fri, Jan 04, 2019 at 09:58:38AM -0700, Benjamin Slade wrote: > On 2019-01-04T03:24:26-0700, Oswald Buddenhagen > wrote: > > the network activity prior to this would be interesting. with > > timestamps, so pipe the output through ts '%.T'. > > Here is a pastebin of the output, with ellipsis

Re: unresolvable lost pulled message leading to timeout

2019-01-04 Thread Benjamin Slade
On 2019-01-04T17:37:26-0700, Oswald Buddenhagen wrote: > yes, it clearly gets upset when uploading the first message, which > has a whopping 9.3 megs, which you presumably don't have in the other > clones. > the default timeout of 20 secs is a bit tight, so you may just > increase it, and