Hi Michael,
FYI last night and the night before the mirror monitor was unable to connect mirror.nasutek.com:
rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
The IP address shown above for mirror.nasutek.com seems to be different than the IP address (158.69.26.24?) that pulls from the primary mirror but I don't know whether this has always been the case or whether this is significant.
Thank you for mirroring Trinity Desktop Environment.
--Mike
On Thu November 4 2021 10:27:57 Mike Bird wrote:
FYI last night and the night before the mirror monitor was unable to connect mirror.nasutek.com:
rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
The IP address shown above for mirror.nasutek.com seems to be different than the IP address (158.69.26.24?) that pulls from the primary mirror but I don't know whether this has always been the case or whether this is significant.
Hi Slávek,
Still no response and no resolution and the mirror doesn't seem to have updated since roughly 10/31.
I suggest we discontinue mirror.nasutek.com/trinity .
--Mike
On Thursday 11 of November 2021 10:30:24 Mike Bird wrote:
On Thu November 4 2021 10:27:57 Mike Bird wrote:
FYI last night and the night before the mirror monitor was unable to connect mirror.nasutek.com:
rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
The IP address shown above for mirror.nasutek.com seems to be different than the IP address (158.69.26.24?) that pulls from the primary mirror but I don't know whether this has always been the case or whether this is significant.
Hi Slávek,
Still no response and no resolution and the mirror doesn't seem to have updated since roughly 10/31.
I suggest we discontinue mirror.nasutek.com/trinity .
--Mike ____________________________________________________
At this time, mirror is marked as outdated and therefore is not used by redirector. We can wait for some time if there will be any reaction from Michael.
Thank you for your careful supervision of mirrors!
Cheers
On 2021-11-11 01:30, Mike Bird wrote:
On Thu November 4 2021 10:27:57 Mike Bird wrote:
FYI last night and the night before the mirror monitor was unable to connect mirror.nasutek.com:
rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
The IP address shown above for mirror.nasutek.com seems to be different than the IP address (158.69.26.24?) that pulls from the primary mirror but I don't know whether this has always been the case or whether this is significant.
Hi Slávek,
Still no response and no resolution and the mirror doesn't seem to have updated since roughly 10/31.
I suggest we discontinue mirror.nasutek.com/trinity .
--Mike ____________________________________________________ tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
I see this issue now, its really strange it changed.
Somehow when I rebooted the server both the syncing and then RSync was affected
I did fix this issue.
If you guys ever have an issue with this again, you can email me at nasutek at gmail.com and I will for sure respond faster.
Sorry for this.
Hi Michael,
Your mirror is not responding to rsync again.
Please fix - is it maybe your firewall?
Thanks,
--Mike
# time rsync mirror.nasutek.com:: rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
real 2m9.683s user 0m0.001s sys 0m0.006s
Ok will check out asap. It is the firewall i changed some ports yesterday
Sent from my iPhone
On Nov 22, 2021, at 5:53 PM, Mike Bird mgb-trinity@yosemite.net wrote:
Hi Michael,
Your mirror is not responding to rsync again.
Please fix - is it maybe your firewall?
Thanks,
--Mike
# time rsync mirror.nasutek.com:: rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
real 2m9.683s user 0m0.001s sys 0m0.006s ____________________________________________________ tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
I got it allowed again. I was pruning unused ports and forgot that 873 was RSync
Sorry about that. That was 100% my bad.
On 2021-11-23 12:14, Michael J. Manley via tde-devels wrote:
Ok will check out asap. It is the firewall i changed some ports yesterday
Sent from my iPhone
On Nov 22, 2021, at 5:53 PM, Mike Bird mgb-trinity@yosemite.net wrote:
Hi Michael,
Your mirror is not responding to rsync again.
Please fix - is it maybe your firewall?
Thanks,
--Mike
# time rsync mirror.nasutek.com:: rsync: [Receiver] failed to connect to mirror.nasutek.com (167.114.53.32): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(137) [Receiver=3.2.3]
real 2m9.683s user 0m0.001s sys 0m0.006s ____________________________________________________ tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...
tde-devels mailing list -- devels@trinitydesktop.org To unsubscribe send an email to devels-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydeskt...