[Solved] new llvm19-lib.tcz breaks local mirrors

[GNUser]

Hi Juanito, Rich, and friends. I synced my local TCL mirror to the official repo today and I saw an updated llvm19-lib.tcz trickle in along with a few other new or updated extensions.

My TCL laptops are unable to update llvm19-lib when using my local mirror. This command never returns:

Code: [Select]

laptop$ tce-update
...
Checking Tiny Core Applications in /mnt/sda1/tce/optional
Updating llvm19-lib.tcz
My http server log quickly fills up with entries like this:

Code: [Select]

Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
...
If I manually edit the .md5.txt of other extensions on my laptop to bogus md5sums, those extensions can be successfully updated from the local mirror.

If I use the official repo, llvm19-lib can be successfully updated.

There seems to be something about the updated llvm19-lib.tcz that breaks local mirrors. Any ideas?

[GNUser]

I can no longer reproduce my problem, after reproducing it about a dozen times including after reboots.

Strange, but I guess the problem went away on its own somehow.

[Juanito]

The main repo takes time to sync with the mirrors?

[GNUser]

Hi Juanito. That's not it. I sync the local mirror by manually running  rsync  on my server. I wait for rsync to finish before I attempt to update my TCL machines that use the local mirror.

I'll keep an eye on this. If it happens again I'll investigate further and will post here.

[Rich]

Hi GNUser

... My http server log quickly fills up with entries like this:

Code: [Select]

Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
Fri 5/1/26 10:12AM,/tinycorelinux/17.x/x86_64/tcz/llvm19-lib.tcz,200,198.44.159.34
 ----- Snip ----- ...

That  200  looks like it may be an HTTP 200 OK status code. Maybe it's lying?
Also, I Googled that IP address and it came back as blacklisted by a couple of sites.

[GNUser]

That  200  looks like it may be an HTTP 200 OK status code. Maybe it's lying?

Yes, 200 means HTTP OK. I agree that it must be a lie here. Good observation.

Also, I Googled that IP address and it came back as blacklisted by a couple of sites.

I use VPN for privacy. A lot of sites blacklist VPN IPs, so finding my IP on a blacklist is not surprising. However, this would not explain my problem--I do not block VPN IPs (or any IPs, for that matter) from accessing my http server.

[GNUser]

I had a similar problem today when a different extension was being updated. Based on my http server's logs, I realized that the problem had nothing to do with the specific extension. The problem had to do with broken  zsync  support in my http server.

If mirror uses http (i.e., not https) and zsync is present on the TCL box being updated (zsync is part of the base system, so theoretically is always present unless user deletes it), then  tce-update  defaults to using  zsync  when updating extensions due to this line in /usr/bin/tce-update:

Code: [Select]

[ "$MIRRORPROTO" == "http" ] && [ -n "`which zsync`" ] && USEZSYNC=yes

Once I fixed my http server to correctly handle zsync transfers (see https://forum.tinycorelinux.net/index.php?topic=28140.msg182931#msg182931), then all zsync-related problems went away.

This thread is solved.

[Rich]

Hi GNUser
Marked as solved.