Mailing List Archive

one machine out of many has nothing to update
Hello.

I update several machines every month.  This month, most of the machines
needed to update more than 300 packages.  But one, which isn't any
different than the others, has 0 to update, after running --sync.

Does anybody have an explanation for that?
Re: one machine out of many has nothing to update [ In reply to ]
On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
> Hello.
>
> I update several machines every month.  This month, most of the machines
> needed to update more than 300 packages.  But one, which isn't any
> different than the others, has 0 to update, after running --sync.
>
> Does anybody have an explanation for that?
>
>

The manifest verification failed during emerge --sync and you didn't
notice it. Happens to me every time.
Re: one machine out of many has nothing to update [ In reply to ]
Am Wed, May 05, 2021 at 02:24:48PM -0400 schrieb Michael Orlitzky:
> On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
> > Hello.
> >
> > I update several machines every month.  This month, most of the machines
> > needed to update more than 300 packages.  But one, which isn't any
> > different than the others, has 0 to update, after running --sync.
> >
> > Does anybody have an explanation for that?
> >
> >
>
> The manifest verification failed during emerge --sync and you didn't
> notice it. Happens to me every time.

For the sake of speed and bandwidth saving, I used to sync both tree and
distfiles between my hosts. So the main PC synced from the interwebs, and
the laptop fetched from the PC. So as soon as you know your “master” machine
works, you should be fine if your other machines pull from it.

--
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.

No trees were killed in the sending of this message.
However, a large number of electrons were terribly inconvenienced.
Re: one machine out of many has nothing to update [ In reply to ]
On 5/5/21 8:24 PM, Michael Orlitzky wrote:
> On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
>> Hello.
>>
>> I update several machines every month.  This month, most of the machines
>> needed to update more than 300 packages.  But one, which isn't any
>> different than the others, has 0 to update, after running --sync.
>>
>> Does anybody have an explanation for that?
>>
>>
> The manifest verification failed during emerge --sync and you didn't
> notice it. Happens to me every time.
>

Yes!  It did!  It does, every time!  But why?  I have enough disk space...
Re: one machine out of many has nothing to update [ In reply to ]
On 5/6/21 7:30 AM, n952162 wrote:
> On 5/5/21 8:24 PM, Michael Orlitzky wrote:
>> On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
>>> Hello.
>>>
>>> I update several machines every month.  This month, most of the
>>> machines
>>> needed to update more than 300 packages.  But one, which isn't any
>>> different than the others, has 0 to update, after running --sync.
>>>
>>> Does anybody have an explanation for that?
>>>
>>>
>> The manifest verification failed during emerge --sync and you didn't
>> notice it. Happens to me every time.
>>
>
> Yes!  It did!  It does, every time!  But why?  I have enough disk
> space...
>
>
>

This forum entry from 2018:

https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
<https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>

lists various possible causes, all of which involve complicated or
expensive fixes:

1. with "hard-links"
2. without "hard-links"
3. /usr/portage is corrupted (/var/db/repos/gentoo in my case, I guess)
4. rsync-excludes?
5. use a different mirror (but it works for other machines)

Is there a consensus in the mean time?
Re: one machine out of many has nothing to update [ In reply to ]
On 06/05/2021 01:10, Frank Steinmetzger wrote:
> For the sake of speed and bandwidth saving, I used to sync both tree and
> distfiles between my hosts.

When I had two machines, the second just nfs-mounted the first's
repository. So updating one updated the other at the same time :-)

Cheers,
Wol
Re: one machine out of many has nothing to update [ In reply to ]
On 5/6/21 7:42 AM, n952162 wrote:
> On 5/6/21 7:30 AM, n952162 wrote:
>> On 5/5/21 8:24 PM, Michael Orlitzky wrote:
>>> On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
>>>> Hello.
>>>>
>>>> I update several machines every month.  This month, most of the
>>>> machines
>>>> needed to update more than 300 packages.  But one, which isn't any
>>>> different than the others, has 0 to update, after running --sync.
>>>>
>>>> Does anybody have an explanation for that?
>>>>
>>>>
>>> The manifest verification failed during emerge --sync and you didn't
>>> notice it. Happens to me every time.
>>>
>>
>> Yes!  It did!  It does, every time!  But why?  I have enough disk
>> space...
>>
>>
>>
>
> This forum entry from 2018:
>
> https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
> <https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>
>
> lists various possible causes, all of which involve complicated or
> expensive fixes:
>
> 1. with "hard-links"
> 2. without "hard-links"
> 3. /usr/portage is corrupted (/var/db/repos/gentoo in my case, I guess)
> 4. rsync-excludes?
> 5. use a different mirror (but it works for other machines)
>
> Is there a consensus in the mean time?
>
>

Here's the error:

 * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine
...!!! Manifest verification failed:
Manifest mismatch for metadata/Manifest.gz
  __size__: expected: 3019, have: 3011

I diffed the two metadata/Manifest.gz files, here as a png to retain the
spacing.

I'm not sure what __size__ is being displayed there.
Re: one machine out of many has nothing to update [ In reply to ]
On Thu, May 06, 2021 at 07:42:19AM +0200, n952162 wrote
>
> This forum entry from 2018:
>
> https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
> <https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>
>
> lists various possible causes, all of which involve complicated or
> expensive fixes:

In a worst-case, you could try skipping manifest verification
altogether on the affected machine. You must do 2 steps to get that
working.

1) In /etc/portage/repos.conf/gentoo.conf set...

sync-rsync-verify-metamanifest = no

The default installed setting is "yes"

2) Add the line...

sys-apps/portage -rsync-verify

...to package.use and then re-emerge portage.

emerge -1a portage

--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
Re: one machine out of many has nothing to update [ In reply to ]
On Thursday, May 6, 2021 9:40:21 AM CEST n952162 wrote:
> On 5/6/21 7:42 AM, n952162 wrote:
> > On 5/6/21 7:30 AM, n952162 wrote:
> >> On 5/5/21 8:24 PM, Michael Orlitzky wrote:
> >>> On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
> >>>> Hello.
> >>>>
> >>>> I update several machines every month. This month, most of the
> >>>> machines
> >>>> needed to update more than 300 packages. But one, which isn't any
> >>>> different than the others, has 0 to update, after running --sync.
> >>>>
> >>>> Does anybody have an explanation for that?
> >>>
> >>> The manifest verification failed during emerge --sync and you didn't
> >>> notice it. Happens to me every time.
> >>
> >> Yes! It did! It does, every time! But why? I have enough disk
> >> space...
> >
> > This forum entry from 2018:
> >
> > https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
> > <https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>
> >
> > lists various possible causes, all of which involve complicated or
> >
> > expensive fixes:
> > 1. with "hard-links"
> > 2. without "hard-links"
> > 3. /usr/portage is corrupted (/var/db/repos/gentoo in my case, I guess)
> > 4. rsync-excludes?
> > 5. use a different mirror (but it works for other machines)
> >
> > Is there a consensus in the mean time?
>
> Here's the error:
>
> * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine
> ...!!! Manifest verification failed:
> Manifest mismatch for metadata/Manifest.gz
> __size__: expected: 3019, have: 3011
>
> I diffed the two metadata/Manifest.gz files, here as a png to retain the
> spacing.
>
> I'm not sure what __size__ is being displayed there.

What's the size of the "Manifest.gz" file?
And did you try re-synching?

--
Joost
Re: one machine out of many has nothing to update [ In reply to ]
On 5/6/21 11:00 AM, J. Roeleveld wrote:
> On Thursday, May 6, 2021 9:40:21 AM CEST n952162 wrote:
>> On 5/6/21 7:42 AM, n952162 wrote:
>>> On 5/6/21 7:30 AM, n952162 wrote:
>>>> On 5/5/21 8:24 PM, Michael Orlitzky wrote:
>>>>> On Wed, 2021-05-05 at 20:11 +0200, n952162 wrote:
>>>>>> Hello.
>>>>>>
>>>>>> I update several machines every month. This month, most of the
>>>>>> machines
>>>>>> needed to update more than 300 packages. But one, which isn't any
>>>>>> different than the others, has 0 to update, after running --sync.
>>>>>>
>>>>>> Does anybody have an explanation for that?
>>>>> The manifest verification failed during emerge --sync and you didn't
>>>>> notice it. Happens to me every time.
>>>> Yes! It did! It does, every time! But why? I have enough disk
>>>> space...
>>> This forum entry from 2018:
>>>
>>> https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
>>> <https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>
>>>
>>> lists various possible causes, all of which involve complicated or
>>>
>>> expensive fixes:
>>> 1. with "hard-links"
>>> 2. without "hard-links"
>>> 3. /usr/portage is corrupted (/var/db/repos/gentoo in my case, I guess)
>>> 4. rsync-excludes?
>>> 5. use a different mirror (but it works for other machines)
>>>
>>> Is there a consensus in the mean time?
>> Here's the error:
>>
>> * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine
>> ...!!! Manifest verification failed:
>> Manifest mismatch for metadata/Manifest.gz
>> __size__: expected: 3019, have: 3011
>>
>> I diffed the two metadata/Manifest.gz files, here as a png to retain the
>> spacing.
>>
>> I'm not sure what __size__ is being displayed there.
> What's the size of the "Manifest.gz" file?
> And did you try re-synching?
>
> --
> Joost
>

01/var/db/repos/gentoo>ls -l metadata/Manifest.gz
.tmp-unverified-download-quarantine/metadata/Manifest.gz
-rw-r--r-- 1 root root 3011 May  6 07:39
.tmp-unverified-download-quarantine/metadata/Manifest.gz
-rw-r--r-- 1 root root 3007 Apr  1 12:09 metadata/Manifest.gz

01/var/db/repos/gentoo>wc  <(gzip -cd < metadata/Manifest.gz | sort)
<(gzip -cd < .tmp-unverified-download-quarantine/metadata/Manifest.gz |
sort)
     21     127    5298 /dev/fd/63
     21     127    5298 /dev/fd/62
     42     254   10596 total

I've resynced multiple times over multiple days.

Interesting observation - all three syncs I did in May have this
__size__ issue.  When I look back at the logs from April, I see I did it
twice.  The first time also failed for metadata/Manifest.gz, but not for
a __size__ problem, but the check sums were dumped.

Apparently, the update failed and I resynced, and the second time it
succeeded!
Re: one machine out of many has nothing to update [ In reply to ]
On 5/6/21 10:55 AM, Walter Dnes wrote:
> On Thu, May 06, 2021 at 07:42:19AM +0200, n952162 wrote
>> This forum entry from 2018:
>>
>> https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
>> <https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>
>>
>> lists various possible causes, all of which involve complicated or
>> expensive fixes:
> In a worst-case, you could try skipping manifest verification
> altogether on the affected machine. You must do 2 steps to get that
> working.
>
> 1) In /etc/portage/repos.conf/gentoo.conf set...
>
> sync-rsync-verify-metamanifest = no
>
> The default installed setting is "yes"
>
> 2) Add the line...
>
> sys-apps/portage -rsync-verify
>
> ...to package.use and then re-emerge portage.
>
> emerge -1a portage
>
Ok, that's good to have a way ...

Question: (I know, this is old, but I'm still not comprehending it): why
wouldn't you want portage in your world set?
Re: one machine out of many has nothing to update [ In reply to ]
It's pointless to have things in your world set that are by the very
nature of the distro in the system set, it's just causing extra
dependency calculations to no purpose. You dont add gcc to the world
set either. or binhost. or libtools.

On Thu, 6 May 2021 at 21:27, n952162 <n952162@web.de> wrote:
>
> On 5/6/21 10:55 AM, Walter Dnes wrote:
> > On Thu, May 06, 2021 at 07:42:19AM +0200, n952162 wrote
> >> This forum entry from 2018:
> >>
> >> https://forums.gentoo.org/viewtopic-t-1085556-start-0.html
> >> <https://forums.gentoo.org/viewtopic-t-1085556-start-0.html>
> >>
> >> lists various possible causes, all of which involve complicated or
> >> expensive fixes:
> > In a worst-case, you could try skipping manifest verification
> > altogether on the affected machine. You must do 2 steps to get that
> > working.
> >
> > 1) In /etc/portage/repos.conf/gentoo.conf set...
> >
> > sync-rsync-verify-metamanifest = no
> >
> > The default installed setting is "yes"
> >
> > 2) Add the line...
> >
> > sys-apps/portage -rsync-verify
> >
> > ...to package.use and then re-emerge portage.
> >
> > emerge -1a portage
> >
> Ok, that's good to have a way ...
>
> Question: (I know, this is old, but I'm still not comprehending it): why
> wouldn't you want portage in your world set?
>
>
>
Re: one machine out of many has nothing to update [ In reply to ]
On Thu, 6 May 2021 11:51:17 +0200, n952162 wrote:

> I've resynced multiple times over multiple days.
>
> Interesting observation - all three syncs I did in May have this
> __size__ issue.  When I look back at the logs from April, I see I did it
> twice.  The first time also failed for metadata/Manifest.gz, but not for
> a __size__ problem, but the check sums were dumped.
>
> Apparently, the update failed and I resynced, and the second time it
> succeeded!

Deleting the entire portage tree and syncing from scratch usually fixes
these issues.


--
Neil Bothwick

In possession of a mind not merely twisted, but actually sprained.
Re: one machine out of many has nothing to update [ In reply to ]
On Thu, 2021-05-06 at 07:30 +0200, n952162 wrote:
>
>
> Yes!  It did!  It does, every time!  But why?  I have enough disk space...
>

I have no idea. I fix it by re-syncing until the error stops. That's
how computers work.
Re: one machine out of many has nothing to update [ In reply to ]
On 5/6/21 2:37 PM, Michael Orlitzky wrote:
> On Thu, 2021-05-06 at 07:30 +0200, n952162 wrote:
>>
>> Yes!  It did!  It does, every time!  But why?  I have enough disk space...
>>
> I have no idea. I fix it by re-syncing until the error stops. That's
> how computers work.
>
>
>
Oh bummer.  So, I started it for a fourth time (23 min.s).  This time,
instead  of the __size__ problem, I have the checksum dump again:

* Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine
...!!! Manifest verification failed:
Manifest mismatch for metadata/news/Manifest
  BLAKE2B: expected:
043eb190ef9e0459a146d8b9989dd905608c218a67652dee9cb7337e8c9096c7ce9137d927d42c113f55b1a761e45d7a4dbf6e4c353f3ff7db1cd2edd938fef7,
have:
829c36d9c8ae31172f3b79f01d251051b5a99f3312b619319c2d02663d811ab2a5b9d453e31bd81d0188a1d4d083816d172910aded3999897be16328a01c5736
  SHA512: expected:
d60b42276be831cec73ec9b7dc669fd1902627c1ff788f06d6049b60f8f4d9733de6b193dc9fb586730f8229fce83972bf4d4b099bce7cbc648a5f5e6accd8a1,
have:
7057bc3445c11b9725b79f845e1dc5393fee13920b3e8a4b7038badbaeccec33d6ca2f2381c430de660a51fedd14ff2844234cd560101ab32a6cbd68050f8d9b

It's starting to look like it might really be a race condition...

And that since about 2 years.