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
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
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
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
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 the best way of resolving this?
> >
> start with the -D output ...
That
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 the best way of resolving this?
>
start with the -D output ...
___
isync-devel mailing list
isync-de
