question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Gitblit server occasionally stops responding to SSH connections on port 29418

See original GitHub issue

Having upgraded to Gitblit 1.7.1 we are experiencing the following problem: Gitblit server occasionally stops responding to SSH connections on port 29418. This usually occurs once per day, once a couple of days.

In the server log one can find the following exception: 2016-01-13 13:18:56 [WARN ] Caught IOException while accepting incoming connection from /0:0:0:0:0:0:0:0:29418: The specified network name is no longer available.

java.io.IOException: The specified network name is no longer available.

at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
at sun.nio.ch.Iocp.access$700(Iocp.java:46)
at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
at java.lang.Thread.run(Thread.java:745)

The last successful SSH session gets opened and closed just before this exception. No following SSH connections are possible any more. It seems as the socket accepting thread dies and the processing chain gets broken, preventing other following connection from processing.

Interestingly, other Gitblit services such as HTTPS, GIT, main page are operational.

The /0:0:0:0:0:0:0:0:29418 has suggested me that IPv6 might have been involved. I double checked the server set-up (Windows Server 2008 R2 (6.1)). The only existing Ethernet interface is bound to IPv4 only, no IPv6 is configured whatsoever.

I can bet the problem comes from way beneath Gitblit, and Gitblit is not to be blamed.

However I am considering some improvement in Gitblit alone, perhaps some exception handler, so that it is able to recover from such situation and be able to server following connections.

I would appreciate your comments and/or suggestions.

Dariusz

Issue Analytics

  • State:open
  • Created 8 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

0reactions
mkotsbakcommented, Nov 1, 2018

Yes I see two: https://github.com/gitblit/gitblit/pull/1272 https://github.com/gitblit/gitblit/pull/1216

but it seems like the prosject is not maintained and then no PR merged…

Read more comments on GitHub >

github_iconTop Results From Across the Web

Gitblit server occasionally stops responding to SSH ... - GitHub
It seems as the socket accepting thread dies and the processing chain gets broken, preventing other following connection from processing.
Read more >
Using the SSH Transport - Gitblit
By default, Gitblit serves the SSH transport on port 29418, which is the same as ... If you are working on Windows you'll...
Read more >
Mirrored repositories are not working - General - GitLab Forum
I need help with Mirroring repositories. I had set up mirroring a GitLab repo with AWS CodeCommit repo. It was working fine.
Read more >
Using SSH instead of HTTP to access GitBlit repository
Problem solved by moving GitBlit out of the Tomcat's ROOT directory and use rewriteRule on Apache VirtualHost
Read more >
SSH connections to Gerrit randomly hang - Google Groups
In short: commands requiring SSH connection to Gerrit randomly hang. I'm not ... debug1: Connecting to gerrit.repo [10.0.10.43] port 29418.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found