GithubHelp home page GithubHelp logo

"error copy client cont" error about pound HOT 8 CLOSED

abaldoni avatar abaldoni commented on August 30, 2024
"error copy client cont" error

from pound.

Comments (8)

graygnuorg avatar graygnuorg commented on August 30, 2024

This message means that the client didn't send the content of the request (as announced by the Content-Length header) within the client timeout. The timeout is set by the Client statement in the ListenHTTP . The default is 10 seconds.

Did this error appear when you were running 4.9.90?

from pound.

abaldoni avatar abaldoni commented on August 30, 2024

Hi, yes the error is in both version 4.9.90 and 4.11.90.
Unfortunately we cannot say whether it was present in earlier versions: we can only say that the backend seemed to work better in the past.

from pound.

graygnuorg avatar graygnuorg commented on August 30, 2024

And you can't reproduce it, can you?

from pound.

abaldoni avatar abaldoni commented on August 30, 2024

I a certain sense I can.
The backend connects to a Microsoft Exchange hybrid mode server and the error occurs when we need to migrate a mailbox from the on-premise server to the Microsoft cloud.
I tried again a few hours ago and the problem occurred again.

from pound.

graygnuorg avatar graygnuorg commented on August 30, 2024

That's great. A couple of questions then:

  1. Is it possible that this migration sometimes takes more than 10 seconds?
  2. Have you tried to raise the client timeout? If not, can you please try and see if this helps?
  3. Do you see anything special in the backend logs?

from pound.

abaldoni avatar abaldoni commented on August 30, 2024

The "time" factor is quite unclear to me.
The job gets scheduled on the Microsoft cloud which tries to execute it at its own pace.
I'll try to increate the client timeout since 10 secs is definitely too low.
The backend logs are unfortunately of no use in diagnosing the problem.
I'll be back with further details.

Thanks!

from pound.

graygnuorg avatar graygnuorg commented on August 30, 2024

In the meantime you might wish to pull the commit 3996e21 which improves diagnostic messages a bit.

from pound.

abaldoni avatar abaldoni commented on August 30, 2024

Hi, for this specific case we decided to move our Exchange from hybrid to full cloud so we won't be using this backend anymore.
Since no other backend presents the problem I'm going to close this issue.

Thanks!

from pound.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.