tickets #114577
closed
local mirror setup - no new rsync files
Added by list-s@vink-slott.dk over 2 years ago.
Updated over 2 years ago.
Description
Hi
I have hacked together a small script for local mirror.
Problem is that after the initial download ~ 4 days ago, it does not see
any new files. Latest example:
On a another host not using my local mirror:
~> rpm -qa | grep 'glibc-2.31-150300'
glibc-2.31-150300.37.1.x86_64
but my mirror dont get any glibc > 31
~> find /mirror -name "glibc-2.31-150300*"
/mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.20.7.x86_64.rpm
/mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.26.5.x86_64.rpm
/mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.26.5.x86_64.slsa_provenance.json
/mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.26.5_150300.31.2.x86_64.drpm
/mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.31.2.x86_64.slsa_provenance.json
/mirror/update/leap/15.3/sle/x86_64/glibc-2.31-150300.9.12.1.x86_64.rpm
rsync.opensuse.org does not seem to have any glibc > 31. Could update of
this rsync server have stalled?
--
Regards
Klaus
- Category set to Mirrors
- Private changed from Yes to No
Hej Klaus
not necessarily stalled, but simply slow to update. Still, being a week behind on updates/ sounds unlikely. I'll see if I can get access from my current location (Skyros in the Aegean).
- Due date set to 2022-07-30
pjessen wrote:
I'll see if I can get access from my current location (Skyros in the Aegean).
I don't seem able to connect to our infrastructure, but we're moving to a new location in a couple of days, maybe things will improve.
- Is duplicate of tickets #97520: rsync.opensuse.org out of synch ? added
pjessen wrote:
pjessen wrote:
I'll see if I can get access from my current location (Skyros in the Aegean).
I don't seem able to connect to our infrastructure, but we're moving to a new location in a couple of days, maybe things will improve.
The vpn issue was fixed, and it looks like the immediate issue of opensuse/update/leap/15.3/sle/x86_64 being-out-of-date has been resolved. It was very late though - "glibc-2.31-150300.37.1.x86_64.rpm" is dated 21 July, but it was only available on rsync.o.o five days later, 26 July.
We do run an rsync on updates/ every 10 minutes, which should have taken are of this. I'll see if I can find anything in the output.
- Status changed from New to In Progress
- % Done changed from 0 to 50
Yeah, I've found something:
2022-07-28T09:20:01.145084+02:00 rsync cron[28521]: *** stack smashing detected ***: terminated
Have just restarted cron. Divine inspiration from #113809
- Is duplicate of deleted (tickets #97520: rsync.opensuse.org out of synch ?)
- Is duplicate of tickets #113809: cron - *** stack smashing detected ***: terminated added
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
the rsync cron jobs are running again, I'm closing this as resolved.
Also available in: Atom
PDF