Tiny Core Linux

General TC => General TC Talk => Topic started by: GNUser on April 19, 2025, 11:37:52 PM

Title: cannot sync mirror with official repository
Post by: GNUser on April 19, 2025, 11:37:52 PM

This command had been working for years, but today something broke:

Code: [Select]

$ rsync -dtvh --delete --progress repo.tinycorelinux.net::tc/16.x/x86_64/tcz/ /path/to/localmirror/16.x/x86_64/tcz
rsync: [Receiver] failed to connect to repo.tinycorelinux.net (128.127.66.77): Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1]
I tried connecting through my home's wifi as well as through mobile hotspot, with same result.

Has there been a recent change to the official repo? If so, what is the new way to sync mirrors with the official repo, please?

Title: Re: cannot sync mirror with official repository
Post by: Rich on April 20, 2025, 01:27:41 AM

Hi GNUser

Quote from: GNUser on April 19, 2025, 11:37:52 PM

... rsync error: error in socket IO (code 10) ...

A search on that error suggests that rsync is not running on the server.
I ran  ps aux | grep rsync  on the server and nothing showed up.

Title: Re: cannot sync mirror with official repository
Post by: GNUser on April 20, 2025, 06:34:25 AM

Hi Rich. In that case, can you please restart the rsync server?
If it's been turned off on purpose, what's the new way to sync?

Title: Re: cannot sync mirror with official repository
Post by: Rich on April 20, 2025, 09:44:29 AM

Hi GNUser
I'll bring it up with some of the other administrators.
I don't know enough about the server to bring up rsyncd.

Title: Re: cannot sync mirror with official repository
Post by: Paul_123 on April 20, 2025, 09:54:28 AM

should be set now.  The process was HUP'd, not sure why.

Title: Re: cannot sync mirror with official repository
Post by: GNUser on April 20, 2025, 10:32:12 AM

Yes, syncing with official repo works again. Thank you both.

Title: Re: cannot sync mirror with official repository
Post by: patrikg on April 20, 2025, 10:36:56 AM

Quote from: Paul_123 on April 20, 2025, 09:54:28 AM

should be set now.  The process was HUP'd, not sure why.

Maybe because of updated rsync daemon(system update)