Stream-events SSH threads stuck

443 views
Skip to first unread message

Marcelo Ávila

unread,
Dec 1, 2014, 8:07:02 AM12/1/14
to Repo and Gerrit Discussion
Hello everybody,

We just upgraded from 2.9.1 to 2.9.2 to have the SSHD-348 fix but the stream-events ssh threads keep getting stuck:

> lsof -n -i :29418 | grep -c "ESTABLISHED"
203

And counting... the Gerrit server was restarted 8h ago... we're restarting it every day.

Is somebody having the same problem? Does the 2.9.2 solve this issue for anyone?

Thanks & regards,

--
Marcelo Ávila de Oliveira
CPqD - Information Technology Engineer

Saša Živkov

unread,
Dec 1, 2014, 8:38:35 AM12/1/14
to Marcelo Ávila, Repo and Gerrit Discussion
On Mon, Dec 1, 2014 at 2:06 PM, Marcelo Ávila <mav...@cpqd.com.br> wrote:
Hello everybody,

We just upgraded from 2.9.1 to 2.9.2 to have the SSHD-348 fix but the stream-events ssh threads keep getting stuck:

> lsof -n -i :29418 | grep -c "ESTABLISHED"
203

And counting... the Gerrit server was restarted 8h ago... we're restarting it every day.
 
These are bad news. 

Last Friday, I also upgraded our production server to 2.9.2. Right now, checked the SSH-Stream-Worker
threads and 2 out of 10 are already stuck.

Looks like we will have to go back to the SSHD 0.9.0 + "SSH handshake fix" +  "Authentication with partial success fix".



Is somebody having the same problem? Does the 2.9.2 solve this issue for anyone?

Thanks & regards,

--
Marcelo Ávila de Oliveira
CPqD - Information Technology Engineer

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Ostrovsky

unread,
Dec 1, 2014, 9:46:45 AM12/1/14
to repo-d...@googlegroups.com, mav...@cpqd.com.br

Am Montag, 1. Dezember 2014 14:38:35 UTC+1 schrieb zivkov:


On Mon, Dec 1, 2014 at 2:06 PM, Marcelo Ávila <mav...@cpqd.com.br> wrote:
Hello everybody,

We just upgraded from 2.9.1 to 2.9.2 to have the SSHD-348 fix but the stream-events ssh threads keep getting stuck:

> lsof -n -i :29418 | grep -c "ESTABLISHED"
203

And counting... the Gerrit server was restarted 8h ago... we're restarting it every day.
 
These are bad news. 


Indeed. I've reopened the issue upstream.
 
Last Friday, I also upgraded our production server to 2.9.2. Right now, checked the SSH-Stream-Worker
threads and 2 out of 10 are already stuck.

Can you create thread dump of stuck thread?

Gustavo Leite de Mendonça Chaves

unread,
Dec 1, 2014, 10:51:30 AM12/1/14
to David Ostrovsky, repo-discuss, Marcelo Avila Oliveira
Hi. I work with Marcelo and we just realized that only one of our 15 Jenkins servers have more than one connection to Gerrit. So, the problem seems to be on the Jenkins side, probably with the Gerrit-Trigger plugin.

I restarted it 25 minutes ago and it already has 9 ESTABLISHED connections.

Although the Gerrit-Trigger plugin is uptodate the Jenkins server is a little outdated and there are several other plugins outdated too. We'll upgrade it to see if it solves the problem and will let you know how it goes.

Thank you.

--
Gustavo Leite de Mendonça Chaves
CPqD - Gerência de Tecnologia da Informação e Comunicação

Saša Živkov

unread,
Dec 1, 2014, 11:00:46 AM12/1/14
to David Ostrovsky, repo-d...@googlegroups.com, Marcelo Ávila
Yes. Two threads are stuck with slightly different stack traces:

"SSH-Stream-Worker-3" cpu=76210.00 [reset 76210.00] ms elapsed=266202.69 [reset 266202.69] s allocat
io= file i/o: 11705408/0 B, net i/o: 0/0 B, files opened:0, socks opened:0  [reset file i/o: 1170540
prio=10 tid=0x00007f1a7c549800 nid=0x26ab / 9899  pthread-id=139750708037376 in Object.wait()  [_thr
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(J)V(Native Method)
        - waiting on <0x00007f1b77333080> (a org.apache.sshd.common.channel.Window)
        at java.lang.Object.wait()V(Object.java:503)
        at org.apache.sshd.common.channel.Window.waitForSpace()I(Window.java:148)
        - locked <0x00007f1b77333080> (a org.apache.sshd.common.channel.Window)
        at org.apache.sshd.common.channel.ChannelOutputStream.flush()V(ChannelOutputStream.java:116)
        - locked <0x00007f1b77335230> (a org.apache.sshd.common.channel.ChannelOutputStream)
        at org.apache.sshd.common.channel.ChannelOutputStream.write([BII)V(ChannelOutputStream.java:
        - locked <0x00007f1b77335230> (a org.apache.sshd.common.channel.ChannelOutputStream)
        at sun.nio.cs.StreamEncoder.writeBytes()V(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implFlushBuffer()V(StreamEncoder.java:291)
        at sun.nio.cs.StreamEncoder.implFlush()V(StreamEncoder.java:295)
        at sun.nio.cs.StreamEncoder.flush()V(StreamEncoder.java:141)
        - locked <0x00007f1b77336c30> (a java.io.OutputStreamWriter)
        at java.io.OutputStreamWriter.flush()V(OutputStreamWriter.java:229)
        at java.io.BufferedWriter.flush()V(BufferedWriter.java:254)
        - locked <0x00007f1b77336c30> (a java.io.OutputStreamWriter)
        at java.io.PrintWriter.flush()V(PrintWriter.java:320)
        - locked <0x00007f1b77336be8> (a java.io.BufferedWriter)
        at java.io.PrintWriter.checkError()Z(PrintWriter.java:357)
        at com.google.gerrit.sshd.commands.StreamEvents.writeEvents()V(StreamEvents.java:186)
        at com.google.gerrit.sshd.commands.StreamEvents.access$100(Lcom/google/gerrit/sshd/commands/
        at com.google.gerrit.sshd.commands.StreamEvents$3.run()V(StreamEvents.java:82)
        at java.util.concurrent.Executors$RunnableAdapter.call()Ljava/lang/Object;(Executors.java:47
        at java.util.concurrent.FutureTask.run()V(FutureTask.java:262)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Ljava/uti
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run()V(ScheduledThre
        at com.google.gerrit.server.git.WorkQueue$Task.run()V(WorkQueue.java:364)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecuto
        at java.util.concurrent.ThreadPoolExecutor$Worker.run()V(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run()V(Thread.java:812)

"SSH-Stream-Worker-10" cpu=62710.00 [reset 62710.00] ms elapsed=266202.18 [reset 266202.18] s alloca
io= file i/o: 9527648/0 B, net i/o: 0/0 B, files opened:0, socks opened:0  [reset file i/o: 9527648/
prio=10 tid=0x0000000002aaa800 nid=0x26b2 / 9906  pthread-id=139750700668672 in Object.wait()  [_thr
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(J)V(Native Method)
        - waiting on <0x00007f1b63b0ba18> (a org.apache.sshd.common.channel.Window)
        at java.lang.Object.wait()V(Object.java:503)
        at org.apache.sshd.common.channel.Window.waitForSpace()I(Window.java:148)
        - locked <0x00007f1b63b0ba18> (a org.apache.sshd.common.channel.Window)
        at org.apache.sshd.common.channel.ChannelOutputStream.flush()V(ChannelOutputStream.java:116)
        - locked <0x00007f1b63b0d9d0> (a org.apache.sshd.common.channel.ChannelOutputStream)
        at sun.nio.cs.StreamEncoder.implFlush()V(StreamEncoder.java:297)
        at sun.nio.cs.StreamEncoder.flush()V(StreamEncoder.java:141)
        - locked <0x00007f1b63b20728> (a java.io.OutputStreamWriter)
        at java.io.OutputStreamWriter.flush()V(OutputStreamWriter.java:229)
        at java.io.BufferedWriter.flush()V(BufferedWriter.java:254)
        - locked <0x00007f1b63b20728> (a java.io.OutputStreamWriter)
        at java.io.PrintWriter.flush()V(PrintWriter.java:320)
        - locked <0x00007f1b63b206e0> (a java.io.BufferedWriter)
        at java.io.PrintWriter.checkError()Z(PrintWriter.java:357)
        at com.google.gerrit.sshd.commands.StreamEvents.writeEvents()V(StreamEvents.java:186)
        at com.google.gerrit.sshd.commands.StreamEvents.access$100(Lcom/google/gerrit/sshd/commands/
        at com.google.gerrit.sshd.commands.StreamEvents$3.run()V(StreamEvents.java:82)
        at java.util.concurrent.Executors$RunnableAdapter.call()Ljava/lang/Object;(Executors.java:47
        at java.util.concurrent.FutureTask.run()V(FutureTask.java:262)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Ljava/uti
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run()V(ScheduledThre
        at com.google.gerrit.server.git.WorkQueue$Task.run()V(WorkQueue.java:364)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecuto
        at java.util.concurrent.ThreadPoolExecutor$Worker.run()V(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run()V(Thread.java:812)

Marcelo Ávila

unread,
Dec 15, 2014, 6:14:27 AM12/15/14
to repo-discuss, David Ostrovsky, Gustavo Leite de Mendonça Chaves
Hello everyone,

We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).

Gerrit: 2.9.2
Jenkins: 1.580.1
Gerrit Plugin: 2.12.0

If I have news I let you know.

Regards,

--
Marcelo Ávila de Oliveira
CPqD - Information Technology Engineer

David Ostrovsky

unread,
Dec 15, 2014, 6:19:58 AM12/15/14
to repo-d...@googlegroups.com

Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:
Hello everyone,

We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).


Can you define so far (in hours)?
 
Gerrit: 2.9.2
Jenkins: 1.580.1
Gerrit Plugin: 2.12.0

Interesting. What have you changed in your setup and from what version?

Marcelo Ávila

unread,
Dec 15, 2014, 7:07:56 AM12/15/14
to David Ostrovsky, Repo and Gerrit Discussion
2014-12-15 9:19 GMT-02:00 David Ostrovsky <david.o...@gmail.com>:

Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:
Hello everyone,

We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).


Can you define so far (in hours)?

 We had a Gerrit auto restart running every day (3AM) to live with this issue, but last week we noticed the issue was not happening anymore, I mean, the SSH threads were not getting stuck during the day, so we disabled the Gerrit auto restart on this weekend (the last one was executed on 13-Dec).

Gerrit: 2.9.2
Jenkins: 1.580.1 <= from 1.532.2
Gerrit Plugin: 2.12.0 <= from 2.11.0

Saša Živkov

unread,
Dec 15, 2014, 9:34:29 AM12/15/14
to Marcelo Ávila, David Ostrovsky, Repo and Gerrit Discussion
On Mon, Dec 15, 2014 at 1:07 PM, Marcelo Ávila <mav...@cpqd.com.br> wrote:
2014-12-15 9:19 GMT-02:00 David Ostrovsky <david.o...@gmail.com>:

Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:
Hello everyone,

We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).


Can you define so far (in hours)?

 We had a Gerrit auto restart running every day (3AM) to live with this issue, but last week we noticed the issue was not happening anymore, I mean, the SSH threads were not getting stuck during the day, so we disabled the Gerrit auto restart on this weekend (the last one was executed on 13-Dec).

How many SSH-Stream-Worker threads do you have?
In our productive system we observed, on average, one SSH-Stream-Worker thread per day getting stuck.
 

Gerrit: 2.9.2
Jenkins: 1.580.1 <= from 1.532.2
Gerrit Plugin: 2.12.0 <= from 2.11.0

Interesting. What have you changed in your setup and from what version?

--

Marcelo Ávila

unread,
Dec 15, 2014, 10:00:56 AM12/15/14
to Saša Živkov, David Ostrovsky, Repo and Gerrit Discussion
2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:


On Mon, Dec 15, 2014 at 1:07 PM, Marcelo Ávila <mav...@cpqd.com.br> wrote:
2014-12-15 9:19 GMT-02:00 David Ostrovsky <david.o...@gmail.com>:

Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:
Hello everyone,

We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).


Can you define so far (in hours)?

 We had a Gerrit auto restart running every day (3AM) to live with this issue, but last week we noticed the issue was not happening anymore, I mean, the SSH threads were not getting stuck during the day, so we disabled the Gerrit auto restart on this weekend (the last one was executed on 13-Dec).

How many SSH-Stream-Worker threads do you have?

20

Gustavo Leite de Mendonça Chaves

unread,
Dec 15, 2014, 11:01:38 AM12/15/14
to Marcelo Ávila, Saša Živkov, David Ostrovsky, Repo and Gerrit Discussion
2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:
2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:

How many SSH-Stream-Worker threads do you have?

20

Just to be sure, each one of those threads are connected to a different Jenkins server and we haven't  seen them accumulating again. The "accumulation" of connections affected a single Jenkins server which we upgraded a few days ago as Marcelo said. Now each Jenkins server has a single SSH connection to Gerrit.

Saša Živkov

unread,
Dec 15, 2014, 11:16:01 AM12/15/14
to Gustavo Leite de Mendonça Chaves, Marcelo Ávila, David Ostrovsky, Repo and Gerrit Discussion
On Mon, Dec 15, 2014 at 5:01 PM, Gustavo Leite de Mendonça Chaves <gus...@cpqd.com.br> wrote:
2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:
2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:

How many SSH-Stream-Worker threads do you have?

20

Just to be sure, each one of those threads are connected to a different Jenkins server

AFAIK, it is NOT one thread per connection... and you don't need one thread per one Jenkins server.

As long as there are unblocked threads the events will be streamed to all Jenkins servers.

Gustavo Leite de Mendonça Chaves

unread,
Dec 15, 2014, 1:27:36 PM12/15/14
to Saša Živkov, Marcelo Ávila, David Ostrovsky, Repo and Gerrit Discussion
2014-12-15 14:15 GMT-02:00 Saša Živkov <ziv...@gmail.com>:

On Mon, Dec 15, 2014 at 5:01 PM, Gustavo Leite de Mendonça Chaves <gus...@cpqd.com.br> wrote:
2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:
2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:

How many SSH-Stream-Worker threads do you have?

20

Just to be sure, each one of those threads are connected to a different Jenkins server

AFAIK, it is NOT one thread per connection... and you don't need one thread per one Jenkins server.

As long as there are unblocked threads the events will be streamed to all Jenkins servers.

I'm sorry. I meant we see 20 connections (not threads) with the "ssh gerrit gerrit show-connections" command. Most of them are to the machines where we have our Jenkins servers running. Using "lsof -i :29418" on each of those machines we can see that each Jenkins server (a java process) has a single connection to Gerrit, while before we had one of those Jenkins servers which would accumulate multiple SSH connections to Gerrit over time.

How can I count those SSH-Stream-Worker threads? I tried using "jstack -F PID" to generate a thread dump from Gerrit but I couldn't find the string "SSH-Stream-Worker" anywhere in its output.

Saša Živkov

unread,
Dec 15, 2014, 4:51:49 PM12/15/14
to Gustavo Leite de Mendonça Chaves, Marcelo Ávila, David Ostrovsky, Repo and Gerrit Discussion
On Mon, Dec 15, 2014 at 7:27 PM, Gustavo Leite de Mendonça Chaves <gus...@cpqd.com.br> wrote:
2014-12-15 14:15 GMT-02:00 Saša Živkov <ziv...@gmail.com>:

On Mon, Dec 15, 2014 at 5:01 PM, Gustavo Leite de Mendonça Chaves <gus...@cpqd.com.br> wrote:
2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:
2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:

How many SSH-Stream-Worker threads do you have?

20

Just to be sure, each one of those threads are connected to a different Jenkins server

AFAIK, it is NOT one thread per connection... and you don't need one thread per one Jenkins server.

As long as there are unblocked threads the events will be streamed to all Jenkins servers.

I'm sorry. I meant we see 20 connections (not threads) with the "ssh gerrit gerrit show-connections" command. Most of them are to the machines where we have our Jenkins servers running. Using "lsof -i :29418" on each of those machines we can see that each Jenkins server (a java process) has a single connection to Gerrit, while before we had one of those Jenkins servers which would accumulate multiple SSH connections to Gerrit over time.

How can I count those SSH-Stream-Worker threads? I tried using "jstack -F PID" to generate a thread dump from Gerrit but I couldn't find the string "SSH-Stream-Worker" anywhere in its output.

Normally, "jstack PID" should print the thread dump directly to the stdout.
The PID of a running Gerrit process is stored under $SITE/logs/gerrit.pid.
Check the for "waitForSpace" call in the thread dump, for the "SSH-Stream-Worker..." threads.

Gustavo Leite de Mendonça Chaves

unread,
Dec 16, 2014, 5:49:00 AM12/16/14
to Saša Živkov, Marcelo Ávila, David Ostrovsky, Repo and Gerrit Discussion
I got it now. Yesterday I was running jstack as root and the thread names didn't appear in the output. Today, for no particular reason, I run jstack as the same user running Gerrit and the output is different, showing the thread names. So I can find there are just three SSH threads:

$ jstack 14181 | grep -c SSH-Stream-Worker
3

And this is their stacktraces:

$ jstack 14181 | grep -A10 SSH-Stream-Worker
"SSH-Stream-Worker-3" prio=10 tid=0x00007fd4400a7800 nid=0x5c25 waiting on condition [0x00007fd4376f5000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0000000780c510f8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1079)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
--
"SSH-Stream-Worker-2" prio=10 tid=0x00007fd4400a7000 nid=0x5c24 waiting on condition [0x00007fd465c23000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0000000780c510f8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1079)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
--
"SSH-Stream-Worker-1" prio=10 tid=0x00007fd4400a6000 nid=0x5c23 waiting on condition [0x00007fd464209000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x0000000780c510f8> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1079)
at java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

And "ssh gerrit gerrit show-connections" shows 17 connections from user jenkins.

Saša Živkov

unread,
Dec 16, 2014, 7:14:02 AM12/16/14
to Gustavo Leite de Mendonça Chaves, Marcelo Ávila, David Ostrovsky, Repo and Gerrit Discussion
This looks good.

Marcelo Ávila

unread,
Dec 23, 2014, 8:52:09 AM12/23/14
to Saša Živkov, Gustavo Leite de Mendonça Chaves, David Ostrovsky, Repo and Gerrit Discussion
It seems that things are better (Gerrit: 2.9.2, Jenkins: 1.580.1Gerrit Plugin: 2.12.0) but the SSH issue is not completely solved yet. The following graphic shows the number of active client SSH connections as displayed by "ssh gerrit show-connections" command. As you can see, sometimes the number of connections increase and we didn't find what have triggered these.


Regards,

--
Marcelo Ávila de Oliveira

Hugo Arès

unread,
Jan 6, 2015, 12:28:42 PM1/6/15
to repo-d...@googlegroups.com, ziv...@gmail.com, gus...@cpqd.com.br, david.o...@gmail.com
I reproduced the problem in my dev environment, it takes about 8-10 hours to get 5 threads stuck. I commented on the sshd issue and will do the follow up and test the new sshd version when it's available.

Hugo

Yogesh Bhat

unread,
Jun 2, 2015, 5:39:09 AM6/2/15
to repo-d...@googlegroups.com, david.o...@gmail.com, ziv...@gmail.com, gus...@cpqd.com.br
Any further update on this?

which gerrit/jenkins/gerrit-trigger version solves this problem completely?

Thanks,
Yogesh

David Ostrovsky

unread,
Jun 2, 2015, 5:48:37 AM6/2/15
to repo-d...@googlegroups.com

Am Dienstag, 2. Juni 2015 11:39:09 UTC+2 schrieb Yogesh Bhat:
Any further update on this?

which gerrit/jenkins/gerrit-trigger version solves this problem completely?

All Gerrit version starting from 2.9.3 shouldn't be affected by this bug.

In Gerrit 2.9.3 SSHD was downgraded to 0.9.0-4-g5967cfd version.
In Gerrit 2.10.3 SSHD was upgraded to 0.14.0 version. 
Reply all
Reply to author
Forward
0 new messages