Hello,
We mirror these archives 'MX-ISOs' and 'MX-Packages' every 6:45 hours
This is the address of 'rsync-mxlinux.org': 162.212.157.246 and those are the address of 'iso.mxrepo.com': 104.200.67.193 , 23.227.184.135
Recently the script usually returns the following:
----MX-ISOs (lun feb 6 10:54:06 CET 2023)
----
receiving file list ... done
./
rsync: connection unexpectedly closed (5357 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [receiver=3.1.2]
rsync: [generator] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(820) [generator=3.1.2]
----
----MX-Packages (lun feb 6 10:54:14 CET 2023)
----
Greetings.
Mirror synchronization problems
-
- Posts: 10
- Joined: Fri Feb 03, 2023 4:41 am
Re: Mirror synchronization problems
Hello,dolphin_oracle wrote: Fri Feb 03, 2023 9:05 am @mxlinux-cica thanks for the command.
which mirror are you?
We are ftp.cica.es mirror, url: https://ftp.cica.es/mirrors/Linux/MX-ISOs/MX/Final/
Greetings
Re: Mirror synchronization problems
I was looking for same error online and one of the responses that seems relevant and we can act on sounds like this:
Can you try to clean the destination folder and try to sync again? Otherwise people report different things, even difference in rsync versions... hope it's not something too weird going on.I happened to run into this error for a specific file's transfer because a previously aborted rsync run seems to have corrupted the destination file (maybe due to interrupted delta/incremental changes on the destination file).
My solution was to find out which file caused the error (by using -v and/or --progress), deleting that file in the destination, then running rsync normally again.
-
- Posts: 10
- Joined: Fri Feb 03, 2023 4:41 am
Re: Mirror synchronization problems
Thank you very much for your response.Adrian wrote: Mon Feb 06, 2023 8:36 am I was looking for same error online and one of the responses that seems relevant and we can act on sounds like this:
Can you try to clean the destination folder and try to sync again? Otherwise people report different things, even difference in rsync versions... hope it's not something too weird going on.I happened to run into this error for a specific file's transfer because a previously aborted rsync run seems to have corrupted the destination file (maybe due to interrupted delta/incremental changes on the destination file).
My solution was to find out which file caused the error (by using -v and/or --progress), deleting that file in the destination, then running rsync normally again.
We can't do that without knowing for sure that the problem will be solved. Since this action can take a long time and during this synchronization time our mirror won't be available.
-
- Posts: 10
- Joined: Fri Feb 03, 2023 4:41 am
Re: Mirror synchronization problems
Hello,
We continue with synchronization errors with 'MX-ISOs'. The script returns error code 10:
MX-ISOs = 10
According to list of rsync exit codes, it means:
10: Error in socket I/O. There was an error with the socket input/output.
Greetings.
We continue with synchronization errors with 'MX-ISOs'. The script returns error code 10:
MX-ISOs = 10
According to list of rsync exit codes, it means:
10: Error in socket I/O. There was an error with the socket input/output.
Greetings.
- Eadwine Rose
- Administrator
- Posts: 14925
- Joined: Wed Jul 12, 2006 2:10 am
Re: Mirror synchronization problems
You'll have to do what was suggested or continue with the errors. Stuff has to be ruled out or we can't help you and it will continue to be like this.
MX-23.6_x64 July 31 2023 * 6.1.0-37amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
-
- Posts: 10
- Joined: Fri Feb 03, 2023 4:41 am
Re: Mirror synchronization problems
Hello,
It worked. Yesterday I deleted the destination folder and synchronized again. I have verified that it has synchronized well in the last logs. For example i attached one from yestarday:
During today I will be in observation, if there aren't more errors, tomorrow I will notify and it can be considered solved.
Thank you very much to everybody.
Greetings.
It worked. Yesterday I deleted the destination folder and synchronized again. I have verified that it has synchronized well in the last logs. For example i attached one from yestarday:
----MX-ISOs (mié feb 8 18:45:01 CET 2023)
----
receiving file list ... done
Number of files: 171 (reg: 160, dir: 11)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 0
Total file size: 26,272,595,220 bytes
Total transferred file size: 0 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 5,349
File list generation time: 0.001 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 19
Total bytes received: 5,360
sent 19 bytes received 5,360 bytes 2,151.60 bytes/sec
total size is 26,272,595,220 speedup is 4,884,289.87
----
----MX-Packages (mié feb 8 18:45:04 CET 2023)
----
receiving file list ... done
During today I will be in observation, if there aren't more errors, tomorrow I will notify and it can be considered solved.
Thank you very much to everybody.
Greetings.
-
- Posts: 10
- Joined: Fri Feb 03, 2023 4:41 am
Re: Mirror synchronization problems
Hello,
I have checked that it has synchronized well in the last logs. The problem has been resolved by deleting destination directory and synchronizing again.
So it looks like the origin of the problem was that there was a conflict with some file and it caused some problem when synchronizing.
Thank you very much!
I have checked that it has synchronized well in the last logs. The problem has been resolved by deleting destination directory and synchronizing again.
So it looks like the origin of the problem was that there was a conflict with some file and it caused some problem when synchronizing.
Thank you very much!