No feedback? Is everyone else just ignoring these messages?
Thomas
-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Thomas Leavitt
Sent: Monday, February 29, 2016 10:53 AM
To: [log in to unmask]
Subject: RE: "Not using downloaded repomd.xml because it is older than what we have:"
Not using downloaded repomd.xml because it is older than what we have:
Current : Tue Feb 16 08:58:20 2016
Downloaded: Tue Feb 16 08:58:13 2016
A 7 second variance shouldn't be that much of an issue.
Regards,
Thomas Leavitt
-----Original Message-----
From: Thomas Leavitt
Sent: Monday, February 29, 2016 10:52 AM
To: [log in to unmask]
Subject: RE: "Not using downloaded repomd.xml because it is older than what we have:"
I've been meaning to write about this for a while... my inbox is flooded every day with messages with this as the content from my SL7 machines (the ones I have set up to forward mail sent to root). I checked the time on them, they're using NTP, and the time agrees, almost to the second, with that of network time services and other machines, I doubt there's even a 30 second variance.
What's the strategy for dealing with this? Seems like it isn't an isolated problem.
Regards,
Thomas Leavitt
-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of David Sommerseth
Sent: Thursday, February 18, 2016 2:51 AM
To: Peter Boy; [log in to unmask]
Subject: Re: "Not using downloaded repomd.xml because it is older than what we have:"
On 13/02/16 19:24, Peter Boy wrote:
> Hi all,
>
> since several months I get constantly from anacreon:
>> ——————————<
> /etc/cron.daily/0yum-daily.cron:
>
> Not using downloaded repomd.xml because it is older than what we have:
> Current : Thu Feb 4 16:13:26 2016
> Downloaded: Thu Feb 4 16:13:25 2016
>> ——————————<
>
>
> The time difference is quite minimal. And a manual „yum update“
> confirms that no updates are waiting.
>
> Using my favourite search engine I found it might have be caused by an
> unresponsive of lazy mirror. But I use the standard configuration, i.e.
> the mirror list just includes the three scientificlinux servers. Other
> entries refer old bugs long fixed.
>
> I tried a yum clean all but it didn’t fix it.
>
> And all our other don’t show this issue, but the configuration is all
> the same, at least according to my knowledge.
>
>
> Obviously, there is no harm done and it can be safely ignored. But it
> always pulls our issue alert button.
Hi,
I am seeing exactly the same. I thought it was NTP issues related to my own setup, where I have a local rsync mirror. But then I installed from scratch SL7 on another site without any local mirrors, and the same issue appears there too. So I see this both with public repositories as well as local rsync repositories.
I have also seen this on SL6, but not as frequent as on SL7.
Even though they cause no obvious harm, it gets quite annoying when you receive many of them during a day ... sometimes even several days in a row.
Perhaps yum should be more graceful to the timestamp? And just quiet these messages if the time difference is less than 30 seconds or so.
--
kind regards,
David Sommerseth
--
kind regards,
David Sommerseth
________________________________
This e-mail may contain privileged or confidential information. If you are not the intended recipient: (1) you may not disclose, use, distribute, copy or rely upon this message or attachment(s); and (2) please notify the sender by reply e-mail, and then delete this message and its attachment(s). EAG, Inc. and its affiliates disclaim all liability for any errors, omissions, corruption or virus in this message or any attachments.
|
