error: RPC failed; result=22, HTTP code = 503

[eric van tassell]

How do I debug this situation? It seems to be happening with other peoples clients as well as mine.

git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/84/9584/6 && git cherry-pick FETCH_HEAD

error: RPC failed; result=22, HTTP code = 503

Thanks.

--
- evt
(Eric van Tassell)
twitter: evt_texelsoft
linked-in: linkedin.com/in/evttxl

[Shawn Pearce]

On Wed, Jan 12, 2011 at 13:39, eric van tassell <evt...@gmail.com> wrote:
> How do I debug this situation? It seems to be happening with other peoples
> clients as well as mine.
>
> git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/84/9584/6 &&
> git cherry-pick FETCH_HEAD
> error: RPC failed; result=22, HTTP code = 503

HTTP code 503 over the smart HTTP protocol happens when the server is
too busy to answer the client's request. Look at the server's
execution queue with gerrit show-queue, its probably got a lot of
requests in it that are active. Some might be wedged requests from
days ago that aren't making any progress, killing them would free up
threads to answer new incoming requests.

[Edwin Kempin]

Hi Shawn,

I'm currently facing the same problem when I'm trying to push
something over https
to the Android Gerrit Server:

$ git push https://edwin....@review.source.android.com/p/tools/gerrit
HEAD:refs/for/master
Password:
Counting objects: 7, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (4/4), done.
Writing objects: 100% (4/4), 415 bytes, done.
Total 4 (delta 3), reused 0 (delta 0)

error: RPC failed; result=22, HTTP code = 503

fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

Maybe you can check the queue on the server for hanging requests?

Thanks.
Edwin

On 12 Jan., 22:52, Shawn Pearce <s...@google.com> wrote:
> On Wed, Jan 12, 2011 at 13:39, eric van tassell <evt...@gmail.com> wrote:
>
> > How do I debug this situation? It seems to be happening with other peoples
> > clients as well as mine.
>

> > git fetchhttp://review.omapzoom.org/p/kernel/omaprefs/changes/84/9584/6 &&

[Shawn Pearce]

On Thu, Jan 13, 2011 at 01:19, Edwin Kempin <edwin....@gmail.com> wrote:
>
> I'm currently facing the same problem when I'm trying to push
> something over https
> to the Android Gerrit Server:
>
> $ git push https://edwin....@review.source.android.com/p/tools/gerrit

...

> error: RPC failed; result=22, HTTP code = 503

Seems fine now. Temporary busy state?

Unlike with SSH, Jetty doesn't wait very long before it throws the
connection out of the queue. Its possible that I just don't have
enough threads in the thread pool to handle current activity. I'll
see if we can increase sshd.threads on that server.

[Edwin Kempin]

yes, looks like it was only a temporary issue,
now it's working fine again

2011/1/13 Shawn Pearce <s...@google.com>

On Thu, Jan 13, 2011 at 01:19, Edwin Kempin <edwin....@gmail.com> wrote:
>
> I'm currently facing the same problem when I'm trying to push
> something over https
> to the Android Gerrit Server:
>

> $ git push https://edwin.kempin@review.source.android.com/p/tools/gerrit

[Edwin Kempin]

Hi Shawn,

just to let you know, lately I'm getting frequently the 503 error when
pushing
commits via https to review.source.android.com (e.g. every second time
I try
to push something). It is always only a temporary problem, means just
repeating
the push command a couple of times helps to get through.
It's not an urgent issue, but it's a bit annoying. Maybe it would not
be a bad idea
to increase the number of available threads.

Best regards,
Edwin

On 14 Jan., 09:01, Edwin Kempin <edwin.kem...@gmail.com> wrote:
> yes, looks like it was only a temporary issue,
> now it's working fine again
>
> 2011/1/13 Shawn Pearce <s...@google.com>
>

> > On Thu, Jan 13, 2011 at 01:19, Edwin Kempin <edwin.kem...@gmail.com>

> > wrote:
>
> > > I'm currently facing the same problem when I'm trying to push
> > > something over https
> > > to the Android Gerrit Server:
>

> > > $ git push https://edwin.kem...@review.source.android.com/p/tools/gerrit

[Shawn Pearce]

On Mon, Feb 14, 2011 at 06:25, Edwin Kempin <edwin....@gmail.com> wrote:
> just to let you know, lately I'm getting frequently the 503 error when
> pushing
> commits via https to review.source.android.com (e.g. every second time
> I try
> to push something). It is always only a temporary problem, means just
> repeating
> the push command a couple of times helps to get through.
> It's not an urgent issue, but it's a bit annoying. Maybe it would not
> be a bad idea
> to increase the number of available threads.

I did increase the thread count about a week or so ago. So hopefully
this will occur less.