Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On Thu, 2018-01-11 at 22:15 +, RW wrote: > On Thu, 11 Jan 2018 09:46:24 -0600 > David Jones wrote: > > > > I bet most mirrors have a cron entry like "*/10" ... If we still > > see > > problems I can extend the delay some more. > > But the point of a longer delay is that it gives rsync a

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 1/11/2018 5:20 PM, Bill Cole wrote: On 11 Jan 2018, at 12:58 (-0500), Kevin A. McGrail wrote: And not to run GPG if we don't even download anything. I have not had this issue myself so I all I have is the one example in the ticket, but the logged bad hash there was for a partial

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 01/11/2018 04:15 PM, RW wrote: On Thu, 11 Jan 2018 09:46:24 -0600 David Jones wrote: I bet most mirrors have a cron entry like "*/10" ... If we still see problems I can extend the delay some more. But the point of a longer delay is that it gives rsync a guaranteed minimum head start on

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 11 Jan 2018, at 12:58 (-0500), Kevin A. McGrail wrote: And not to run GPG if we don't even download anything. I have not had this issue myself so I all I have is the one example in the ticket, but the logged bad hash there was for a partial download: the first 14372 bytes of

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On Thu, 11 Jan 2018 09:46:24 -0600 David Jones wrote: > I bet most mirrors have a cron entry like "*/10" ... If we still see > problems I can extend the delay some more. But the point of a longer delay is that it gives rsync a guaranteed minimum head start on the DNS. It doesn't rely on

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 1/11/2018 12:57 PM, David Jones wrote: On 01/11/2018 11:24 AM, Kevin A. McGrail wrote: On 1/11/2018 10:46 AM, David Jones wrote: There will be a 30 second to a few minutes delay for the DNS updates to propagate even for DNS caches that don't have the TXT record in their cache. I bet

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 01/11/2018 11:24 AM, Kevin A. McGrail wrote: On 1/11/2018 10:46 AM, David Jones wrote: There will be a 30 second to a few minutes delay for the DNS updates to propagate even for DNS caches that don't have the TXT record in their cache. I bet most mirrors have a cron entry like "*/10" so

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 1/11/2018 10:46 AM, David Jones wrote: There will be a 30 second to a few minutes delay for the DNS updates to propagate even for DNS caches that don't have the TXT record in their cache. I bet most mirrors have a cron entry like "*/10" so they should pull the files at 8:40 AM UTC -- a

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 01/11/2018 09:02 AM, RW wrote: On Wed, 10 Jan 2018 14:06:52 -0600 David Jones wrote: On 01/10/2018 12:40 PM, Alex wrote: Hi, On Wed, Jan 10, 2018 at 12:21 PM, Kevin A. McGrail wrote: On 1/10/2018 11:23 AM, David Jones wrote: I need to see the debug verbose

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On Wed, 10 Jan 2018 14:06:52 -0600 David Jones wrote: > On 01/10/2018 12:40 PM, Alex wrote: > > Hi, > > > > On Wed, Jan 10, 2018 at 12:21 PM, Kevin A. McGrail > > wrote: > >> On 1/10/2018 11:23 AM, David Jones wrote: > >>> > >>> I need to see the debug verbose

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

Hi, >>> Agreed. We need someone to run with -D and log it and IDEALLY run a few >>> right after to see if it resolves. I'm guessing one mirror is blocking >>> or >>> something. >> >> >> I've updated my sa-cron script to loop to try again should it fail due >> to this error, as well as provide

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 01/10/2018 12:40 PM, Alex wrote: Hi, On Wed, Jan 10, 2018 at 12:21 PM, Kevin A. McGrail wrote: On 1/10/2018 11:23 AM, David Jones wrote: I need to see the debug verbose output of one that fails to troubleshoot further. Agreed. We need someone to run with -D

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

Hi, On Wed, Jan 10, 2018 at 12:21 PM, Kevin A. McGrail wrote: > On 1/10/2018 11:23 AM, David Jones wrote: >> >> I need to see the debug verbose output of one that fails to troubleshoot >> further. > > > Agreed. We need someone to run with -D and log it and IDEALLY run

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 1/10/2018 11:23 AM, David Jones wrote: I need to see the debug verbose output of one that fails to troubleshoot further. Agreed.  We need someone to run with -D and log it and IDEALLY run a few right after to see if it resolves.  I'm guessing one mirror is blocking or something.

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On Wed, 2018-01-10 at 15:23 +, RW wrote: > On Wed, 10 Jan 2018 15:10:52 + > Martin Gregorie wrote: > > > > The update defaults to being run from /etc/cron.weekly/sa-update, > > which runs /usr/bin/sa-update without any other parameters and does > > nothing else except for decoding the

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

Hi, > Update: If the downloads are successful but the GPG verification is > failing, then this would not be a routing issue. > > The rsync'ing by the mirrors should happen quickly and the .sha1 and .asc > files should sync quickly since they are very small files. If the downloads > are

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 01/10/2018 10:08 AM, David Jones wrote: On 01/10/2018 09:23 AM, RW wrote: On Wed, 10 Jan 2018 15:10:52 + Martin Gregorie wrote: The update defaults to being run from /etc/cron.weekly/sa-update, which runs /usr/bin/sa-update without any other parameters and does nothing else except for

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On 01/10/2018 09:23 AM, RW wrote: On Wed, 10 Jan 2018 15:10:52 + Martin Gregorie wrote: The update defaults to being run from /etc/cron.weekly/sa-update, which runs /usr/bin/sa-update without any other parameters and does nothing else except for decoding the exit code and mailing all

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

Kevin A. McGrail schrieb am 10.01.2018 um 15:09: > > Anyone having issues with Sha1 failures on their machines on sa-updates? > > Anyone familiar with sa-update.cron so we can try and get more data on this bug below? I'm using sa-update.cron from CentoOS 7. Here it failed once on 09-Jan-2018

Re: [Bug 7331] channel: SHA1 verification failed, channel failed

On Wed, 10 Jan 2018 15:10:52 + Martin Gregorie wrote: > The update defaults to being run from /etc/cron.weekly/sa-update, > which runs /usr/bin/sa-update without any other parameters and does > nothing else except for decoding the exit code and mailing all output > to root: I think its the

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

On Wed, Jan 10, 2018 at 03:10:52PM +, Martin Gregorie wrote: > On Wed, 2018-01-10 at 09:09 -0500, Kevin A. McGrail wrote: > > Anyone having issues with Sha1 failures on their machines on sa- > > updates? > > > No problems are being reported. The log just shows a single 'Update > completed'

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

On Wed, 2018-01-10 at 09:09 -0500, Kevin A. McGrail wrote: > Anyone having issues with Sha1 failures on their machines on sa- > updates? > No problems are being reported. The log just shows a single 'Update completed' line for each weekly update. > Anyone familiar with sa-update.cron so we can

Re: Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

etc/aliases file or by putting a MAILTO=b...@example.com line in the top of the sa-update.cron file. This assumes that the local MTA is configured properly to send email outbound to the Internet. Forwarded Message ---- Subject: [Bug 7331] channel: SHA1 verification failed,

Fwd: [Bug 7331] channel: SHA1 verification failed, channel failed

Anyone having issues with Sha1 failures on their machines on sa-updates? Anyone familiar with sa-update.cron so we can try and get more data on this bug below? Forwarded Message Subject:[Bug 7331] channel: SHA1 verification failed, channel failed Date: Tue, 09