There's probably something else not quite okay with that deployment. Note that apparently all the interactions fail with several minutes of delay, until apache sends the 408. Some of these operations are GET requests, for files that tend to be very small. For example, one of the timeouts was from:
2014-03-26 18:52:13 ERROR juju.cmd supercommand.go:300 failed to GET object provider-state from container juju-dist How was the event reported in the logs of Apache and Swift? On Wed, Mar 26, 2014 at 7:24 PM, Sebastian <[email protected]> wrote: > Yes!! it seems that the apache is giving the time out, for too long uploads. > > Maybe apache tweeks to increase time out? > > thank you people! :) > > Abs, > Sebas. > > > > 2014-03-26 18:54 GMT-03:00 Gustavo Niemeyer > <[email protected]>: >> >> The response was cut out: >> >> > It's worth noting the timing between the first and the second entries >> > in the log above. It's taking quite a while for apache to respond with >> > the 408 timeout, which might indicate that the >> >> ... swift in the backend isn't communicating properly for some reason. >> >> >> gustavo @ http://niemeyer.net >> >> -- >> Juju mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju > > -- gustavo @ http://niemeyer.net -- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
