Opened 3 years ago
Last modified 3 years ago
#17119 new bug
Refreshing repository "Haiku" failed 0%: Bad data
Reported by: | nephele | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Kits/Network Kit | Version: | R1/beta3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
Seems to be caused by an overloaded server anyhow. But the error message is not that descriptive.
hrev55257 for me
The end is at 65% because i terminated the process with CTRL-C sind it didn't seem to be doing anything anymore for some time.
# pkgman update HTTPS: Resolving https://eu.hpkg.haiku-os.org/haiku/master/x86_64/current/repo.sha256 HTTPS: Hostname resolved to: 104.248.198.131:443 HTTPS: Connection to eu.hpkg.haiku-os.org on port 443. HTTPS: Connection opened, sending request. --> HTTPS: GET /haiku/master/x86_64/current/repo.sha256 HTTP/1.1 --> HTTPS: Host: eu.hpkg.haiku-os.org --> HTTPS: Accept: */* --> HTTPS: Accept-Encoding: gzip --> HTTPS: Connection: close --> HTTPS: User-Agent: Services Kit (Haiku) HTTPS: Request sent. HTTPS: Status line received: Code 502 (Bad Gateway) <-- HTTPS: Date: Mon, 26 Jul 2021 11:12:59 GMT <-- HTTPS: Content-Length: 11 <-- HTTPS: Content-Type: text/plain; charset=utf-8 <-- HTTPS: Connection: close HTTPS: 4 headers and 0 bytes of data remaining Refreshing repository "Haiku" failed 0%: Bad data HTTPS: Resolving https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/repo.sha256 HTTPS: Hostname resolved to: 104.248.198.131:443 HTTPS: Connection to eu.hpkg.haiku-os.org on port 443. HTTPS: Connection opened, sending request. --> HTTPS: GET /haikuports/master/x86_64/current/repo.sha256 HTTP/1.1 --> HTTPS: Host: eu.hpkg.haiku-os.org --> HTTPS: Accept: */* --> HTTPS: Accept-Encoding: gzip --> HTTPS: Connection: close --> HTTPS: User-Agent: Services Kit (Haiku) HTTPS: Request sent. HTTPS: Status line received: Code 200 (OK) <-- HTTPS: Accept-Ranges: bytes <-- HTTPS: Content-Length: 64 <-- HTTPS: Content-Type: application/octet-stream <-- HTTPS: Date: Mon, 26 Jul 2021 11:13:09 GMT <-- HTTPS: Etag: "60fdafdc-40" <-- HTTPS: Last-Modified: Sun, 25 Jul 2021 18:39:24 GMT <-- HTTPS: Server: nginx <-- HTTPS: Connection: close HTTPS: 8 headers and 0 bytes of data remaining 100% repochecksum-1 [64 bytes] Validating checksum for HaikuPorts...done. HTTPS: Resolving https://eu.hpkg.haiku-os.org/haikuports/master/x86_64/current/repo HTTPS: Hostname resolved to: 104.248.198.131:443 HTTPS: Connection to eu.hpkg.haiku-os.org on port 443. HTTPS: Connection opened, sending request. --> HTTPS: GET /haikuports/master/x86_64/current/repo HTTP/1.1 --> HTTPS: Host: eu.hpkg.haiku-os.org --> HTTPS: Accept: */* --> HTTPS: Accept-Encoding: gzip --> HTTPS: Connection: close --> HTTPS: User-Agent: Services Kit (Haiku) HTTPS: Request sent. HTTPS: Status line received: Code 200 (OK) <-- HTTPS: Accept-Ranges: bytes <-- HTTPS: Content-Length: 1462068 <-- HTTPS: Content-Type: application/octet-stream <-- HTTPS: Date: Mon, 26 Jul 2021 11:13:10 GMT <-- HTTPS: Etag: "60fdafdc-164f34" <-- HTTPS: Last-Modified: Sun, 25 Jul 2021 18:39:24 GMT <-- HTTPS: Server: nginx <-- HTTPS: Connection: close 65% repocache-2 935.75 KiB/1.39 MiB 209.72 KiB/s
Change History (4)
comment:1 by , 3 years ago
Description: | modified (diff) |
---|
comment:2 by , 3 years ago
comment:3 by , 3 years ago
The repos have been fixed now.
The main problem was this: HTTPS: Status line received: Code 502 (Bad Gateway)
This should be clearly reported as "server is down" or something like that, not just "bad data"
comment:4 by , 3 years ago
Component: | Kits/Package Kit → Kits/Network Kit |
---|
Note:
See TracTickets
for help on using tickets.
I've had that happen as well, it only affects the Haiku repo, NOT the HaikuPorts repo. I feel like it's a corrupted repo.sha256 file. Note the line
HTTPS: Content-Length: 11
. That seems way too small.