15 Nov
2021
15 Nov
'21
7:23 p.m.
On 2021-11-11 01:30, Mike Bird wrote:
On Thu November 4 2021 10:27:57 Mike Bird wrote:
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.
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(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…