https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-10-13T09:29:46ZopenSUSE Project Management ToolopenSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=4549942021-10-13T09:29:46Zpjessenper@computer.org
<ul><li><strong>Category</strong> set to <i>Mirrors</i></li><li><strong>Private</strong> changed from <i>Yes</i> to <i>No</i></li></ul><p><a href="mailto:olaf@aepfle.de">olaf@aepfle.de</a> wrote:</p>
<blockquote>
<p>At least <a href="https://provo-mirror.opensuse.org//history/latest" class="external">https://provo-mirror.opensuse.org//history/latest</a> was not updated since a few weeks.</p>
</blockquote>
<p>Confirmed, it does not seem to have been updated for a while. </p>
<blockquote>
<p>Perhaps there could be some monitoring of this specific file remains </p>
</blockquote>
<p>We scan all mirrors continually, so something is not quite right with the provo mirror.</p>
<blockquote>
<p>Also <a href="https://mirrors.opensuse.org/list/tumbleweed.html" class="external">https://mirrors.opensuse.org/list/tumbleweed.html</a> lists bogus entries for provo-mirror. Operator looks bogus, rsync://provo-downloadcontent.opensuse.org/repositories-scan does not seem to exist.</p>
</blockquote>
<p>It works fine here, but it is for internal use only:</p>
<pre><code># rsync --list-only rsync://provo-downloadcontent.opensuse.org/repositories-scan
drwxr-xr-x 188 2018/09/06 19:22:01 .
lrwxrwxrwx 10 2017/09/06 13:23:06 factory
drwxr-xr-x 74 2017/09/11 08:40:31 debug
drwxr-xr-x 81 2021/06/02 09:45:42 distribution
drwxr-xr-x 4,096 2021/08/26 03:00:01 history
drwxr-xr-x 154 2018/05/25 18:15:30 ports
drwxr-xr-x 4,096 2021/10/13 09:21:13 repositories
drwxr-xr-x 56 2018/11/06 10:34:42 source
drwxr-xr-x 94 2020/04/06 17:54:29 tumbleweed
drwxr-xr-x 169 2021/06/02 09:46:18 update
</code></pre> openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=4550002021-10-13T09:50:24Zpjessenper@computer.org
<ul></ul><p>It looks like one of the Heroes is logged in on provo-mirror, running a manual rsync. I'm guessing either Lars or Christian. I won't have any time for this until Monday, I'm sure it'll be sorted out by then.</p>
openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=4550122021-10-13T10:22:53Zpjessenper@computer.org
<ul><li><strong>Subject</strong> changed from <i>stale entries in /history/latest.mirrorlist</i> to <i>provo-mirror not synchronizing ?</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=4988742022-03-09T09:16:12Zpjessenper@computer.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-10 status-3 priority-4 priority-default closed" href="/issues/107971">tickets #107971</a>: outdated arm64 snapshot on provo-mirror.opensuse.org</i> added</li></ul> openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=4989342022-03-09T09:58:08Zpjessenper@computer.org
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>pjessen</i></li></ul><p>Well, it didn't sort itself out :-( <br>
Afaict, the sync jobs are running normally, except for maybe the weekly sync-all job. According to the log /home/mirror/log/sync_opensuse.log, since 30 December, it has been running for less than one second, which suggests a left-over lockfile. provo-mirror was rebooted about 12 hours ago and I'm just now running a manual /home/mirror/bin/sync_opensuse.sh. </p>
openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=4990962022-03-09T12:26:53Zpjessenper@computer.org
<ul></ul><p>My theory:<br>
when rsync hits some sort of a problem, e.g.</p>
<pre><code>Starting: Thu Dec 23 03:05:01 UTC 2021
rsync: [generator] write error: Connection reset by peer (104)
rsync error: error in socket IO (code 10) at io.c(829) [generator=3.1.3]rsync: connection unexpectedly closed (83614955428 bytes received so far) [receiver]
rsync error: received SIGUSR1 (code 19) at main.c(1455) [receiver=3.1.3]
Finished: Thu Dec 23 09:13:03 UTC 2021
Starting: Thu Dec 30 03:05:01 UTC 2021
Finished: Thu Dec 30 03:05:01 UTC 2021
Starting: Thu Jan 6 03:05:01 UTC 2022
Finished: Thu Jan 6 03:05:01 UTC 2022
Starting: Thu Jan 13 03:05:01 UTC 2022
Finished: Thu Jan 13 03:05:01 UTC 2022
Starting: Thu Jan 20 03:05:01 UTC 2022
Finished: Thu Jan 20 03:05:01 UTC 2022
Starting: Thu Jan 27 03:05:01 UTC 2022
Finished: Thu Jan 27 03:05:01 UTC 2022
Starting: Thu Feb 3 03:05:01 UTC 2022
Finished: Thu Feb 3 03:05:01 UTC 2022
Starting: Thu Feb 10 03:05:02 UTC 2022
Finished: Thu Feb 10 03:05:02 UTC 2022
Starting: Thu Feb 17 03:05:01 UTC 2022
Finished: Thu Feb 17 03:05:01 UTC 2022
Starting: Thu Feb 24 03:05:01 UTC 2022
Finished: Thu Feb 24 03:05:01 UTC 2022
Starting: Thu Mar 3 03:05:02 UTC 2022
Finished: Thu Mar 3 03:05:02 UTC 2022
</code></pre>
<p>the lockfile is not removed? According to 'man withlock':</p>
<pre><code>It uses locks that are valid only while the wrapper is running, and thus will never require additional cleanup
</code></pre>
<p>It seems to me that is simply wrong. </p>
openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=5002582022-03-11T18:26:37Zpjessenper@computer.org
<ul><li><strong>Due date</strong> set to <i>2022-03-18</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>Well, provo-mirror is now syncing again, albeit slowly. I'll take a look at it again next Friday.</p>
openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=5032222022-03-22T15:31:16Zpjessenper@computer.org
<ul></ul><p>I have enabled the four times a day rsync of ports.</p>
openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=5032252022-03-22T15:32:03Zpjessenper@computer.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-10 status-5 priority-4 priority-default closed" href="/issues/108524">tickets #108524</a>: provo-mirror.opensuse.org rsync issue</i> added</li></ul> openSUSE admin - tickets #100805: provo-mirror not synchronizing ?https://progress.opensuse.org/issues/100805?journal_id=5477122022-08-23T05:42:48Zpjessenper@computer.org
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>50</i> to <i>100</i></li></ul><p>I believe we have finally managed to create a mostly stable synchronization scheme on provo-mirror. There is still room for improvement, but I don't think that is a topic for this ticket. I might open a separate one to track what I think needs doing.</p>