4 Nov
2021
4 Nov
'21
5:27 p.m.
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
11 Nov
11 Nov
9:30 a.m.
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
11:21 a.m.
On Thursday 11 of November 2021 10:30:24 Mike Bird wrote:
On Thu November 4 2021 10:27:57 Mike Bird wrote:
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
--
Slávek
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
____________________________________________________ 
15 Nov
15 Nov
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…
23 Nov
23 Nov
1:53 a.m.
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
8:14 p.m.
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(a)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(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…
24 Nov
24 Nov
2:20 a.m.
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(a)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(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…
> ____________________________________________________
> 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…
883
days inactive
903
days old
8 comments
4 participants
participants (4)
-
Michael J. Manley -
Mike Bird -
mjmanley＠ntge.net
-
Slávek Banko