com.google.gerrit.sshd.GerritServerSession

384 views
Skip to first unread message

Clyde Trent

unread,
Nov 18, 2015, 12:46:28 PM11/18/15
to Repo and Gerrit Discussion
Hi,
I am getting this warning a lot in my gerrit logs and was wondering what could be causing this and if there is something that I can do to fix this or suppress it. My set up information if needed:
Gerrit version = 2.11.3 on Ubuntu 14.04.3
Plugins = avatars-external, commit-message-length-validator, download-commands, javamelody, replication, reviewers, reviewnotes, singleusergroup
mysql db

WARN  com.google.gerrit.sshd.GerritServerSession : Exception caught
 java.io.IOException: Connection timed out
        at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
        at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
        at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
        at sun.nio.ch.IOUtil.read(IOUtil.java:197)
        at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
        at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:302)
        at org.apache.mina.transport.socket.nio.NioProcessor.read(NioProcessor.java:45)
       at org.apache.mina.core.polling.AbstractPollingIoProcessor.read(AbstractPollingIoProcessor.java:694)
        at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:668)
        at org.apache.mina.core.polling.AbstractPollingIoProcessor.process(AbstractPollingIoProcessor.java:657)
       at org.apache.mina.core.polling.AbstractPollingIoProcessor.access$600(AbstractPollingIoProcessor.java:67)
        at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java:1121)
      at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)             at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      at java.lang.Thread.run(Thread.java:745)

Thanks for the help
Clyde

Robert Mitwicki

unread,
Jan 22, 2016, 3:25:51 AM1/22/16
to Repo and Gerrit Discussion
Hi,

We having similar issue and it seems that it is happening only when the client use jgit to communicate with gerrit (hard to confirm).
We started monitoring the server to find out what Gerrit is doing while this is happening.
If you solved your issue or have any clue what could be the cause feel free to share.

Gerrit: gerrit version 2.11.3
deleteproject                  v2.9.1     ENABLED  delete-project.jar
download-commands              v2.11.3    ENABLED  download-commands.jar
gravatar-avatar-provider       v2.9.1     ENABLED  gravatar.jar
its-bugzilla                   v2.11.5-14-g9bf41e4 ENABLED  its-bugzilla.jar
reviewers                      v2.11.5-14-g9bf41e4 ENABLED  reviewers.jar
reviewnotes                    v2.11.3    ENABLED  reviewnotes.jar
singleusergroup                v2.11.3    ENABLED  singleusergroup.jar


Ian Kumlien

unread,
Jan 22, 2016, 9:02:04 AM1/22/16
to Clyde Trent, Repo and Gerrit Discussion

Hi,

It's been a while so please correct me if I'm wrong, :)

This looks like a normal connection timed out response for ssh clients (Gerrit uses Mina sshd).

As to why, who or if its a problem that's a bit more of a issue... You can actually look in the ssh log to find most of these - I just don't remember what exit code it was...

> Thanks for the help
> Clyde
>

> --
> --
> 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.

Robert Mitwicki

unread,
Jan 26, 2016, 5:19:12 AM1/26/16
to Repo and Gerrit Discussion, trance....@gmail.com
The problem is that in the ssh_log there is not much information why it happened, for example:

[2016-01-26 10:19:17,672 +0100] d41f69c1 john a/1000041 git-upload-pack./repo.git 0ms 30261ms killed

Is there a way to make it much more verbose, to get some more info?

I also noticed that while I am getting "killed" error message in ssh_log I can spot some gaps (like 5-10 minutes) in the error_log where there is nothing.

Any hint how to debug that issue will be welcome.

Thanks a lot
Best regards
Robert
Reply all
Reply to author
Forward
0 new messages