Thanks Ricardo. Just some more info related to this for the other Ricardo (sorry for the private pastes - summaries provided :) ):
The app server logs don't record any issue afaict [1] but Squid is indeed logging some 502s [2], indicating that something upstream from squid is responding badly (possibly timing out). I checked the timeouts on the app servers (huge - as we don't have a separate service for uploads of desktop packages, unlike clicks/snaps), and the haproxy timeouts should be the same.
Ricardo, how long is the upload going for before you see the error? If it's a long time (ie. > 5mins) it would make sense.
Thanks Ricardo. Just some more info related to this for the other Ricardo (sorry for the private pastes - summaries provided :) ):
The app server logs don't record any issue afaict [1] but Squid is indeed logging some 502s [2], indicating that something upstream from squid is responding badly (possibly timing out). I checked the timeouts on the app servers (huge - as we don't have a separate service for uploads of desktop packages, unlike clicks/snaps), and the haproxy timeouts should be the same.
Ricardo, how long is the upload going for before you see the error? If it's a long time (ie. > 5mins) it would make sense.
[1] https:/ /pastebin. canonical. com/140480/ /pastebin. canonical. com/140479/
[2] https:/