github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 04:25:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

gnutls_handshake() failed: The TLS connection was non-properly terminated #11305

New Issue
Closed
opened 2025-11-02 09:33:50 -06:00 by GiteaMirror · 12 comments
GiteaMirror commented 2025-11-02 09:33:50 -06:00
Owner
Copy Link

Originally created by @somera on GitHub (Jul 22, 2023).

Description

After upgrade to 1.20.1 I see some of this

Failed to update mirror repository '/var/lib/gitea/repositories/raviyasas/spring-boot-hibernate-demo.git': fatal: unable to access 'https://github.com/raviyasas/spring-boot-hibernate-demo.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated.

I run 1.20.0 for some days and I didn't see this error. My mirrors will be updated every 4h.

error after update mirrors.

Gitea Version

1.20.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.41.0

Operating System

Ubuntu 20.04.6

How are you running Gitea?

Precompiled gitea-1.20.1-linux-amd64

Database

PostgreSQL

Originally created by @somera on GitHub (Jul 22, 2023). ### Description After upgrade to 1.20.1 I see some of this `Failed to update mirror repository '/var/lib/gitea/repositories/raviyasas/spring-boot-hibernate-demo.git': fatal: unable to access 'https://github.com/raviyasas/spring-boot-hibernate-demo.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated.` I run 1.20.0 for some days and I didn't see this error. My mirrors will be updated every 4h. error after update mirrors. ### Gitea Version 1.20.1 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.41.0 ### Operating System Ubuntu 20.04.6 ### How are you running Gitea? Precompiled gitea-1.20.1-linux-amd64 ### Database PostgreSQL
GiteaMirror added the issue/needs-feedback label 2025-11-02 09:33:50 -06:00
GiteaMirror commented 2025-11-02 09:33:51 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 22, 2023):

Are you able to clone that repo on the server with just your Unix user account? That feels like it might be a git error that's floating up into Gitea

@techknowlogick commented on GitHub (Jul 22, 2023): Are you able to clone that repo on the server with just your Unix user account? That feels like it might be a git error that's floating up into Gitea
GiteaMirror commented 2025-11-02 09:33:51 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 22, 2023):

All affected repors are mirrored from Github. And I didn't see this error for months with other Gitea versions.

@somera commented on GitHub (Jul 22, 2023): All affected repors are mirrored from Github. And I didn't see this error for months with other Gitea versions.
GiteaMirror commented 2025-11-02 09:33:51 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 22, 2023):

Tje repo from the initial post is: https://github.com/raviyasas/spring-boot-hibernate-demo

@somera commented on GitHub (Jul 22, 2023): Tje repo from the initial post is: https://github.com/raviyasas/spring-boot-hibernate-demo
GiteaMirror commented 2025-11-02 09:33:51 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Jul 22, 2023):

Does git clone work when running on that server for that repo?

@lafriks commented on GitHub (Jul 22, 2023): Does git clone work when running on that server for that repo?
GiteaMirror commented 2025-11-02 09:33:52 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 22, 2023):

Yes, I can clone the project from github and my gitea instance.

I'm using gitea no for ~3 years. And I had less problems in this time. I have a lot of mirrors which. The cron is running every 4h and need 6-7 days for all mirrors.

With the 1.20.0 version I didn't saw

gnutls_handshake() failed: The TLS connection was non-properly terminated

but now with 1.20.1 7 times.

This is not a repo problem. But looks like a gitea problem.

@somera commented on GitHub (Jul 22, 2023): Yes, I can clone the project from github and my gitea instance. I'm using gitea no for ~3 years. And I had less problems in this time. I have a lot of mirrors which. The cron is running every 4h and need 6-7 days for all mirrors. With the 1.20.0 version I didn't saw `gnutls_handshake() failed: The TLS connection was non-properly terminated` but now with 1.20.1 7 times. This is not a repo problem. But looks like a gitea problem.
GiteaMirror commented 2025-11-02 09:33:52 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 22, 2023):

This

2023/07/22 22:02:50 ...irror/mirror_pull.go:290:runSync() [E] SyncMirrors [repo: <Repository 17079:muesli/gotable>]: failed to update mirror repository:
Stdout:
Stderr: fatal: unable to access 'https://github.com/muesli/gotable.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated.

Err: exit status 128
        /source/services/mirror/mirror_pull.go:290 (0x24445de)
        /source/services/mirror/mirror_pull.go:432 (0x2446fe7)
        /source/services/mirror/mirror.go:28 (0x243eeae)
        /source/services/mirror/mirror.go:125 (0x243f884)
        /source/modules/queue/workerqueue.go:246 (0x1c8f05c)
        /source/modules/queue/workergroup.go:98 (0x1c9184d)
        /source/modules/queue/workergroup.go:162 (0x1c8ea68)
        /usr/local/go/src/runtime/asm_amd64.s:1598 (0x475380)
                goexit: BYTE    $0x90   // NOP

was the stacktrace.

Smetimes my IP will be blocked by Github and I have wait some time. But in this case I got every time othe error in gitea.

@somera commented on GitHub (Jul 22, 2023): This ``` 2023/07/22 22:02:50 ...irror/mirror_pull.go:290:runSync() [E] SyncMirrors [repo: <Repository 17079:muesli/gotable>]: failed to update mirror repository: Stdout: Stderr: fatal: unable to access 'https://github.com/muesli/gotable.git/': gnutls_handshake() failed: The TLS connection was non-properly terminated. Err: exit status 128 /source/services/mirror/mirror_pull.go:290 (0x24445de) /source/services/mirror/mirror_pull.go:432 (0x2446fe7) /source/services/mirror/mirror.go:28 (0x243eeae) /source/services/mirror/mirror.go:125 (0x243f884) /source/modules/queue/workerqueue.go:246 (0x1c8f05c) /source/modules/queue/workergroup.go:98 (0x1c9184d) /source/modules/queue/workergroup.go:162 (0x1c8ea68) /usr/local/go/src/runtime/asm_amd64.s:1598 (0x475380) goexit: BYTE $0x90 // NOP ``` was the stacktrace. Smetimes my IP will be blocked by Github and I have wait some time. But in this case I got every time othe error in gitea.
GiteaMirror commented 2025-11-02 09:33:52 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 22, 2023):

After I updated to 1.20.0 I saw high CPU usage on my system comparing to 1.19.x. Cause you changed how the queues works.

In 1.19.x my configuration was

[queue.mirror]
LENGTH = 30000
WORKERS = 1

Now I changet it to

[queue]
MAX_WORKERS = 4

[queue.mirror]
LENGTH = 30000
WORKERS = 1
MAX_WORKERS = 1

[queue.repo_stats_update]
WORKERS = 1
MAX_WORKERS = 1

Cause MAX_WPRKERS is 10 as default. And in this case my system runs on 100% cpu usage.

When you change parameters, than this should be shown after the Gitea restart. For exampe on the first Gitea start in the browser or in the log.

@somera commented on GitHub (Jul 22, 2023): After I updated to 1.20.0 I saw high CPU usage on my system comparing to 1.19.x. Cause you changed how the queues works. In 1.19.x my configuration was ``` [queue.mirror] LENGTH = 30000 WORKERS = 1 ``` Now I changet it to ``` [queue] MAX_WORKERS = 4 [queue.mirror] LENGTH = 30000 WORKERS = 1 MAX_WORKERS = 1 [queue.repo_stats_update] WORKERS = 1 MAX_WORKERS = 1 ``` Cause MAX_WPRKERS is 10 as default. And in this case my system runs on 100% cpu usage. When you change parameters, than this should be shown after the Gitea restart. For exampe on the first Gitea start in the browser or in the log.
GiteaMirror commented 2025-11-02 09:33:52 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 22, 2023):

Could you run gnutls-cli -p 443 github.com -V? "gnutls_handshake() failed: The TLS connection was non-properly terminated." is an error that is reported to gitea from the git CLI. Is it possible you did an apt update/upgrade around the same time you updated gitea to 1.20?

@techknowlogick commented on GitHub (Jul 22, 2023): Could you run `gnutls-cli -p 443 github.com -V`? "gnutls_handshake() failed: The TLS connection was non-properly terminated." is an error that is reported to gitea from the git CLI. Is it possible you did an `apt update/upgrade` around the same time you updated gitea to 1.20?
GiteaMirror commented 2025-11-02 09:33:53 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 22, 2023):

Could you run gnutls-cli -p 443 github.com -V? "gnutls_handshake() failed: The TLS connection was non-properly terminated." is an error that is reported to gitea from the git CLI. Is it possible you did an apt update/upgrade around the same time you updated gitea to 1.20?

Here the ouput:

github.com.txt

I didn't make any apt update at this time.

I tried to reproduce the problem. But I can't.

@somera commented on GitHub (Jul 22, 2023): > Could you run `gnutls-cli -p 443 github.com -V`? "gnutls_handshake() failed: The TLS connection was non-properly terminated." is an error that is reported to gitea from the git CLI. Is it possible you did an `apt update/upgrade` around the same time you updated gitea to 1.20? Here the ouput: [github.com.txt](https://github.com/go-gitea/gitea/files/12137423/github.com.txt) I didn't make any apt update at this time. I tried to reproduce the problem. But I can't.
GiteaMirror commented 2025-11-02 09:33:53 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 23, 2023):

I can see two questions here.

  1. "gnutls_handshake() failed: The TLS connection was non-properly terminated."
    • It indicates that the "https/tls" connection fails, it's usually a network problem (and some ratelimiter may also cause such problem)
  2. Cause MAX_WPRKERS is 10 as default. And in this case my system runs on 100% cpu usage.
    • Do you have a lot of mirror tasks? Maybe we can low the default MAX_WORKERS to 1 or 2 in next release.
    • Update: ps: what's your hardware? How many CPU cores?
@wxiaoguang commented on GitHub (Jul 23, 2023): I can see two questions here. 1. "gnutls_handshake() failed: The TLS connection was non-properly terminated." * It indicates that the "https/tls" connection fails, it's usually a network problem (and some ratelimiter may also cause such problem) 2. Cause MAX_WPRKERS is 10 as default. And in this case my system runs on 100% cpu usage. * Do you have a lot of mirror tasks? Maybe we can low the default MAX_WORKERS to 1 or 2 in next release. * Update: ps: what's your hardware? How many CPU cores?
GiteaMirror commented 2025-11-02 09:33:53 -06:00
Author
Owner
Copy Link

@somera commented on GitHub (Jul 26, 2023):

I can see two questions here.

  1. "gnutls_handshake() failed: The TLS connection was non-properly terminated."

    • It indicates that the "https/tls" connection fails, it's usually a network problem (and some ratelimiter may also cause such problem)

I didn't see this error again.

  1. Cause MAX_WPRKERS is 10 as default. And in this case my system runs on 100% cpu usage.

    • Do you have a lot of mirror tasks? Maybe we can low the default MAX_WORKERS to 1 or 2 in next release.
    • Update: ps: what's your hardware? How many CPU cores?

My config is:

[queue]
MAX_WORKERS = 4

[queue.mirror]
LENGTH = 30000
WORKERS = 1
MAX_WORKERS = 1

[queue.repo_stats_update]
WORKERS = 1
MAX_WORKERS = 1

My hardware is an Intel NUC with Intel Pentium Silver J5005 (4) @ 2.800GHz. It's my Mini-Server where I run:

  • Gitea
  • Nexus
  • PostgreSQL
  • some docker containers

This
image
image
is the 20 last days of the CPU usage. On 16.07. I updated to 1.20.0. And than you see the increased CPU usage. Ans some days ago I chanched the config. And now it's better
image

@somera commented on GitHub (Jul 26, 2023): > I can see two questions here. > > 1. "gnutls_handshake() failed: The TLS connection was non-properly terminated." > > * It indicates that the "https/tls" connection fails, it's usually a network problem (and some ratelimiter may also cause such problem) I didn't see this error again. > 2. Cause MAX_WPRKERS is 10 as default. And in this case my system runs on 100% cpu usage. > > * Do you have a lot of mirror tasks? Maybe we can low the default MAX_WORKERS to 1 or 2 in next release. > * Update: ps: what's your hardware? How many CPU cores? My config is: ``` [queue] MAX_WORKERS = 4 [queue.mirror] LENGTH = 30000 WORKERS = 1 MAX_WORKERS = 1 [queue.repo_stats_update] WORKERS = 1 MAX_WORKERS = 1 ``` My hardware is an Intel NUC with Intel Pentium Silver J5005 (4) @ 2.800GHz. It's my Mini-Server where I run: - Gitea - Nexus - PostgreSQL - some docker containers This ![image](https://github.com/go-gitea/gitea/assets/8334250/93141994-253f-47b5-937a-03b3580164e8) ![image](https://github.com/go-gitea/gitea/assets/8334250/f3c8acf3-0828-4545-9eb0-7a0f9d67c1f6) is the 20 last days of the CPU usage. On 16.07. I updated to 1.20.0. And than you see the increased CPU usage. Ans some days ago I chanched the config. And now it's better ![image](https://github.com/go-gitea/gitea/assets/8334250/4c30e537-07c0-4f1e-a907-6d2972e11517)
GiteaMirror commented 2025-11-02 09:33:54 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 27, 2023):

I think we can do this:

Calculate MAX_WORKERS default value by CPU number #26177

On your system, the default MAX_WORKERS will be "2" then.

ps: the WORKERS = 1 is a no-op, only MAX_WORKERS is used

@wxiaoguang commented on GitHub (Jul 27, 2023): I think we can do this: Calculate MAX_WORKERS default value by CPU number #26177 On your system, the default MAX_WORKERS will be "2" then. ps: the `WORKERS = 1` is a no-op, only MAX_WORKERS is used
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#11305
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?