Re: bad hash in repo

2018-09-23 Thread Randy Bush
this problem seems to have magically cleared up, he said suspiciously

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-04 Thread Patrice Labracherie
Hello

I have exactly the same problem :
104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect 
hash.

I ve updated several 10.4 to 11.1 without problem near march/april.
In august, the same update failed on another 10.4

Today, here is the situation :
10.4to 11.2 OK
10.4to 11.1 10477 has incorrect hash
11.1p10 to 11.2 10477 has incorrect hash
11.1p10 to 11.1 10477 has incorrect hash

# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 2 patches.. done.
Applying patches... done.
Fetching 2 files... 
104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect 
hash.




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-02 Thread Randy Bush
> Is there any possibility there’s something between these you and these
> update hosts?

it is the internet; anything is possible :)  but the hosts having the
problem are on the nekkid global interner.
> 
> This thread has some interesting info

i need to tcpdump.  i'll try to do so in a day or three.

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-02 Thread Charles Sprickman via freebsd-stable

> On Sep 2, 2018, at 6:46 AM, Randy Bush  wrote:
> 
> someone asked if the failures were limited to update5.freebsd.org
> 
> today's batch were both 4 and 5

Is there any possibility there’s something between these you and these update 
hosts?

This thread has some interesting info, but specifically, note the description 
of how phttpget works at the bottom - it is NOT at all picky about what it 
receives, and seems to have some quirks:

https://lists.freebsd.org/pipermail/freebsd-stable/2015-December/083882.html 


Charles

> randy
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-02 Thread Randy Bush
someone asked if the failures were limited to update5.freebsd.org

today's batch were both 4 and 5

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-01 Thread Randy Bush
>>> # pkg update -f
>>> Updating FreeBSD repository catalogue...
>>> Fetching meta.txz: 100%944 B   0.9kB/s00:01
>>> Fetching packagesite.txz: 100%6 MiB   2.2MB/s00:03
>>> Processing entries: 100%
>>> FreeBSD repository update completed. 32029 packages processed.
>>> All repositories are up to date.
>>> # freebsd-update fetch
>>> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
>>> Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... 
>>> done.
>>> Fetching metadata index... done.
>>> Inspecting system... done.
>>> Preparing to download files... done.
>>> Fetching 2 patches.. done.
>>> Applying patches... done.
>>> Fetching 2 files... 
>>> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
>>> incorrect hash.
>> 
>> this is now over two weeks.  still multiple systems on public net, v4
>> and dual stack.
> 
> The other brute-force approach is:
> 
> rm -rf /var/db/freebsd-update/*

work0.psg.com:/root# rm -rf /var/db/freebsd-update/*

work0.psg.com:/root# freebsd-update --not-running-from-cron fetch
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching public key from update5.freebsd.org... done.
Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Fetching 2 metadata files... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 66 patches.102030405060... done.
Applying patches... done.
Fetching 3 files... 
104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect 
hash.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-01 Thread Charles Sprickman via freebsd-stable

> On Sep 1, 2018, at 1:09 PM, Randy Bush  wrote:
> 
> seeing a lot of these
> 
> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... 
> done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
> Fetching 2 patches.. done.
> Applying patches... done.
> Fetching 2 files... 
> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
> incorrect hash.
 these continue; like for a week.  for multiple servers, all on the
 global internet no filters other than samba etc.
>>> 
>>> have you forced pulling down metadata from the pkg servers?  i have
>>> gotten into this state in the past and a "pkg update -f" would get me
>>> out of that scenario.
>> 
>> # pkg update -f
>> Updating FreeBSD repository catalogue...
>> Fetching meta.txz: 100%944 B   0.9kB/s00:01
>> Fetching packagesite.txz: 100%6 MiB   2.2MB/s00:03
>> Processing entries: 100%
>> FreeBSD repository update completed. 32029 packages processed.
>> All repositories are up to date.
>> # freebsd-update fetch
>> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
>> Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... 
>> done.
>> Fetching metadata index... done.
>> Inspecting system... done.
>> Preparing to download files... done.
>> Fetching 2 patches.. done.
>> Applying patches... done.
>> Fetching 2 files... 
>> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
>> incorrect hash.
> 
> this is now over two weeks.  still multiple systems on public net, v4
> and dual stack.

The other brute-force approach is:

rm -rf /var/db/freebsd-update/*

Also, is it always fetching from "update5.freebsd.org”?

Charles

> 
> randy
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-09-01 Thread Randy Bush
 seeing a lot of these
 
 Looking up update.FreeBSD.org mirrors... 2 mirrors found.
 Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... 
 done.
 Fetching metadata index... done.
 Inspecting system... done.
 Preparing to download files... done.
 Fetching 2 patches.. done.
 Applying patches... done.
 Fetching 2 files... 
 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
 incorrect hash.
>>> these continue; like for a week.  for multiple servers, all on the
>>> global internet no filters other than samba etc.
>> 
>> have you forced pulling down metadata from the pkg servers?  i have
>> gotten into this state in the past and a "pkg update -f" would get me
>> out of that scenario.
> 
> # pkg update -f
> Updating FreeBSD repository catalogue...
> Fetching meta.txz: 100%944 B   0.9kB/s00:01
> Fetching packagesite.txz: 100%6 MiB   2.2MB/s00:03
> Processing entries: 100%
> FreeBSD repository update completed. 32029 packages processed.
> All repositories are up to date.
> # freebsd-update fetch
> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
> Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
> Fetching 2 patches.. done.
> Applying patches... done.
> Fetching 2 files... 
> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
> incorrect hash.

this is now over two weeks.  still multiple systems on public net, v4
and dual stack.

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-08-22 Thread Randy Bush
>>> seeing a lot of these
>>> 
>>> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
>>> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... 
>>> done.
>>> Fetching metadata index... done.
>>> Inspecting system... done.
>>> Preparing to download files... done.
>>> Fetching 2 patches.. done.
>>> Applying patches... done.
>>> Fetching 2 files... 
>>> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
>>> incorrect hash.
>> these continue; like for a week.  for multiple servers, all on the
>> global internet no filters other than samba etc.
> 
> have you forced pulling down metadata from the pkg servers?  i have
> gotten into this state in the past and a "pkg update -f" would get me
> out of that scenario.

# pkg update -f
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%944 B   0.9kB/s00:01
Fetching packagesite.txz: 100%6 MiB   2.2MB/s00:03
Processing entries: 100%
FreeBSD repository update completed. 32029 packages processed.
All repositories are up to date.
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 11.1-RELEASE from update5.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 2 patches.. done.
Applying patches... done.
Fetching 2 files... 
104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect 
hash.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-08-22 Thread Pete Wright



On 8/22/18 9:19 AM, Randy Bush wrote:

seeing a lot of these

Looking up update.FreeBSD.org mirrors... 2 mirrors found.
Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
Fetching 2 patches.. done.
Applying patches... done.
Fetching 2 files... 
104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect 
hash.

these continue; like for a week.  for multiple servers, all on the
global internet no filters other than samba etc.


have you forced pulling down metadata from the pkg servers?  i have 
gotten into this state in the past and a "pkg update -f" would get me 
out of that scenario.


-pete

--
Pete Wright
p...@nomadlogic.org
@nomadlogicLA

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-08-22 Thread Randy Bush
> seeing a lot of these
> 
> Looking up update.FreeBSD.org mirrors... 2 mirrors found.
> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
> Fetching 2 patches.. done.
> Applying patches... done.
> Fetching 2 files... 
> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has 
> incorrect hash.

these continue; like for a week.  for multiple servers, all on the
global internet no filters other than samba etc.

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-08-21 Thread Dejan Vučko
Same here:
---
#freebsd-update fetch -v debug -s update6.FreeBSD.org
Looking up update6.FreeBSD.org mirrors... none found.
Fetching metadata signature for 11.1-RELEASE from update6.FreeBSD.org...
latest.ssl100% of  512  B 3334 kBps 00m00s
done.
Fetching metadata index...
530eecbc563578617fecbbfa4036bd8d61f435d9147222100% of  225  B 1139 kBps 00m00s
done.
Inspecting system... done.
Preparing to download files... done.
Fetching 2 patches...
/usr/libexec/phttpget update6.FreeBSD.org 
11.1-RELEASE/i386/bp/7d5cea1a80a7c5f51461af4f408df0933785b8ee66614efbb13ef1e5f337e11d-d258e13105d0e360ab6f8048d0ac1a8c64297224e3c4c34f29e24988bb4bb16d
 
11.1-RELEASE/i386/bp/aaaef0cb3e66c7deb0f8af02a8036414f6a2110ccd9d7d6baec57d4848e0d7bb-104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77
http://update6.FreeBSD.org/11.1-RELEASE/i386/bp/7d5cea1a80a7c5f51461af4f408df0933785b8ee66614efbb13ef1e5f337e11d-d258e13105d0e360ab6f8048d0ac1a8c64297224e3c4c34f29e24988bb4bb16d:
 200 OK
http://update6.FreeBSD.org/11.1-RELEASE/i386/bp/aaaef0cb3e66c7deb0f8af02a8036414f6a2110ccd9d7d6baec57d4848e0d7bb-104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77:
 200 OK
 done.
Applying patches... done.
Fetching 2 files...
/usr/libexec/phttpget update6.FreeBSD.org 
11.1-RELEASE/i386/f/104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77.gz
 
11.1-RELEASE/i386/f/d258e13105d0e360ab6f8048d0ac1a8c64297224e3c4c34f29e24988bb4bb16d.gz
http://update6.FreeBSD.org/11.1-RELEASE/i386/f/104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77.gz:
 200 OK
http://update6.FreeBSD.org/11.1-RELEASE/i386/f/d258e13105d0e360ab6f8048d0ac1a8c64297224e3c4c34f29e24988bb4bb16d.gz:
 200 OK
104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect 
hash.
---



Best regards, 
Dejan Vučko



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-08-17 Thread Randy Bush
> Looking up update.FreeBSD.org
>> Applying patches... done.
>> Fetching 2 files...
>> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has
>> incorrect hash.
> Do you have a transparent proxy in your network or at your ISP

raw nekkid global ip space, aka the internet :)

randy
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: bad hash in repo

2018-08-17 Thread Jason Tubnor
On Sat., 18 Aug. 2018, 01:45 Randy Bush,  wrote:

> seeing a lot of these
>
> Looking up update.FreeBSD.org
> Applying patches... done.
> Fetching 2 files...
> 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has
> incorrect hash.
>


Do you have a transparent proxy in your network or at your ISP as I have
seen similar when those have been present. Bypassing these may fix your
issue.

>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"