Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handler crashed with error net/http: abort Handler #18087

Closed
vmwiz opened this issue Jan 10, 2023 · 7 comments · May be fixed by #21479
Closed

Handler crashed with error net/http: abort Handler #18087

vmwiz opened this issue Jan 10, 2023 · 7 comments · May be fixed by #21479
Labels
Stale

Comments

@vmwiz
Copy link

vmwiz commented Jan 10, 2023

Expected behavior and actual behavior:
When pulling from a proxy cache project we see panics in harbor-core

(sorry the image here is from a private quay repo, used to upgrade an openshift cluster, if you do not have a Red Hat subscription, you won't have access to it but it's the only logs I've right now, the problem also occur with non-proxy cache projects and other public/private images)

2023/01/10 10:14:22.658 �[1;35m[C]�[0m [config.go:500]  the request url is  /v2/quay.io_openshift-release-dev/openshift-release-dev/ocp-v4.0-art-dev/blobs/sha256:79a35526965599b4684f26fbce8f776c0bf80e38d28ee31afdc70b6f5c590cc2
2023/01/10 10:14:22.658 �[1;35m[C]�[0m [config.go:501]  Handler crashed with error net/http: abort Handler
2023/01/10 10:14:22.658 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/runtime/panic.go:884
2023/01/10 10:14:22.658 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/httputil/reverseproxy.go:363
2023/01/10 10:14:22.658 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/repoproxy/proxy.go:76
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/repoproxy/proxy.go:52
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/metric/metric.go:84
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/v2auth/auth.go:170
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/router/router.go:92
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/vendor/github.com/beego/beego/v2/server/web/router.go:1149
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/vendor/github.com/beego/beego/v2/server/web/filter.go:83
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/vendor/github.com/beego/beego/v2/server/web/router.go:1002
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:52
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/security/security.go:75
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/security/security.go:62
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/artifactinfo/artifact_info.go:96
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.659 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:52
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/notification/notification.go:31
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/orm/orm.go:54
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:52
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/session/session.go:35
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/log/log.go:33
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/requestid/requestid.go:43
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/metric/metric.go:51
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/trace/trace.go:28
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/mergeslash/mergeslash.go:17
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/url/parse.go:22
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /harbor/src/server/middleware/middleware.go:57
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2109
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:2947
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/net/http/server.go:1991
2023/01/10 10:14:22.660 �[1;35m[C]�[0m [config.go:507]  /usr/local/go/src/runtime/asm_amd64.s:1594

The cluster report back the following error when trying to pull the image from harbor:

Failed to pull image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7459b3d89433e97e5d5a73b20f80c68e89a6286d0a71d46053462cc2aef1c378": rpc error: code = Unknown desc = writing blob: storing blob to file "/var/tmp/storage199032593/1": happened during read: unexpected EOF

After some retries the image is finally pulled in the cache and operations continue normally.

Steps to reproduce the problem:
Difficult to provide as the problem is intermittent; it also seems to happen on non proxy projects (have seen the seem panic on a replicated project but logs are already rotated)

Versions:

  • harbor version: 2.7.0
  • kubernetes version: 1.22
  • openshift version: 4.9
@stonezdj
Copy link
Contributor

Maybe duplicated with #15751

@tamcore
Copy link

tamcore commented Feb 10, 2023

We're randomly experiencing the same. With the exact same trace in our logs. Usually in combination when the S3 backend has random stability issues. The image size doesn't even matter too much. The first example i could find from the last days references /v2/docker.io/library/nginx/blobs/sha256:c7a81ce22aacea2d1c67cfd6d3c335e4e14256b4ffb80bc052c3977193ba59ba

@github-actions
Copy link

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label Apr 12, 2023
@vmwiz
Copy link
Author

vmwiz commented Apr 12, 2023

Issue still exists on 2.7.1

@github-actions github-actions bot removed the Stale label Apr 13, 2023
@xiao1wen2
Copy link

I also encountered the same problem on version 2.7.1, I don't know if you have resolved it yet

@github-actions
Copy link

github-actions bot commented Aug 7, 2023

This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.

@github-actions github-actions bot added the Stale label Aug 7, 2023
@github-actions
Copy link

github-actions bot commented Sep 7, 2023

This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2023
@khumps khumps mentioned this issue Mar 20, 2024
Closed
This was referenced Feb 3, 2025
Closed
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Stale
Projects
None yet
Milestone
No milestone
4 participants
@tamcore @stonezdj @vmwiz @xiao1wen2