# Debian 7.x repository broken?

**URL:** <https://discuss.elastic.co/t/debian-7-x-repository-broken/284906>\
**Category:** Meta Elastic\
**Created:** [September 22, 2021, 4:58pm UTC](https://discuss.elastic.co/t/debian-7-x-repository-broken/284906 "2021-09-22T16:58:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![theredcat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theredcat/32/14164_2.png) [@theredcat](https://discuss.elastic.co/u/theredcat)\
**Post date:** [September 22, 2021, 4:58pm UTC](https://discuss.elastic.co/t/debian-7-x-repository-broken/284906/1 "2021-09-22T16:58:55Z")

</div>

Hi !

It seems that the 7.x debian repository is currently broken :

```auto
Get:7 https://artifacts.elastic.co/packages/7.x/apt stable/main amd64 Packages [78.8 kB]
Err:7 https://artifacts.elastic.co/packages/7.x/apt stable/main amd64 Packages
  File has unexpected size (78886 != 78795). Mirror sync in progress? [IP: 34.120.127.130 443]
  Hashes of expected file:
   - Filesize:78795 [weak]
   - SHA512:6a31510a68ed4ec43116053445bcae3e01e8aee5a0a91115d33106751aa07803260f9e7c8de356cc6e80ca3225f2f60280de694cb59e0bbb9654de3149a2147b
   - SHA256:33e8f2fba7c5914d6bae8741560b4f12874e7bd655dfc7eaa73c93ed80837707
   - SHA1:41ff70e24888210b61ddf373af05076563e69e82 [weak]
   - MD5Sum:d6ea4093e04c8575814315b36e7174f6 [weak]
  Release file created at: Wed, 15 Sep 2021 21:37:54 +0000
Get:8 https://artifacts.elastic.co/packages/7.x/apt stable/main amd64 Contents (deb) [2816 kB]
Err:8 https://artifacts.elastic.co/packages/7.x/apt stable/main amd64 Contents (deb)
  
Reading package lists... Done       
E: Failed to fetch https://artifacts.elastic.co/packages/7.x/apt/dists/stable/main/binary-amd64/Packages.bz2 File has unexpected size (78886 != 78795). Mirror sync in progress? [IP: 34.120.127.130 443]
   Hashes of expected file:
    - Filesize:78795 [weak]
    - SHA512:6a31510a68ed4ec43116053445bcae3e01e8aee5a0a91115d33106751aa07803260f9e7c8de356cc6e80ca3225f2f60280de694cb59e0bbb9654de3149a2147b
    - SHA256:33e8f2fba7c5914d6bae8741560b4f12874e7bd655dfc7eaa73c93ed80837707
    - SHA1:41ff70e24888210b61ddf373af05076563e69e82 [weak]
    - MD5Sum:d6ea4093e04c8575814315b36e7174f6 [weak]
   Release file created at: Wed, 15 Sep 2021 21:37:54 +0000
E: Failed to fetch https://artifacts.elastic.co/packages/7.x/apt/dists/stable/main/Contents-amd64.gz  
E: Some index files failed to download. They have been ignored, or old ones used instead.

```

I Have both 6.x and 7.x on the same machine (it was updated) and the 6.x seems to be fine.

I'm querying from AWS eu-west-1

I don't think this is a sync-in-progress issue because I'm having the same error for more than 2h.

The file size reported as incorrect by APT is indeed the real file size :

```auto
curl -s https://artifacts.elastic.co/packages/7.x/apt/dists/stable/main/binary-amd64/Packages.bz2 | wc -c
78886

```

And same result adding a cache-breaker to try bypassing the CDN :

```auto
curl -s 'https://artifacts.elastic.co/packages/7.x/apt/dists/stable/main/binary-amd64/Packages.bz2?qsdfqsdfqsdf' | wc -c
78886

```

And even if the cache-breaker is removed on the fly by the CDN, the error shouldn't have lasted more than 2 mn if this was a temporary issue :

```auto
curl -v -o /dev/null 'https://artifacts.elastic.co/packages/7.x/apt/dists/stable/main/binary-amd64/Packages.bz2' 2>&1 |grep cache-control
< cache-control: public, max-age=120

```

The problem seems to be in the InRelease file :

```auto
curl -s 'https://artifacts.elastic.co/packages/7.x/apt/dists/stable/InRelease' | grep main/binary-amd64/Packages.bz2
 d6ea4093e04c8575814315b36e7174f6 78795 main/binary-amd64/Packages.bz2
 41ff70e24888210b61ddf373af05076563e69e82 78795 main/binary-amd64/Packages.bz2
 33e8f2fba7c5914d6bae8741560b4f12874e7bd655dfc7eaa73c93ed80837707 78795 main/binary-amd64/Packages.bz2
 6a31510a68ed4ec43116053445bcae3e01e8aee5a0a91115d33106751aa07803260f9e7c8de356cc6e80ca3225f2f60280de694cb59e0bbb9654de3149a2147b 78795 main/binary-amd64/Packages.bz2

```

---

<div class="post-metadata">

**Author:** ![Stef\_Nestor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stef_nestor/32/85483_2.png) [@Stef\_Nestor](https://discuss.elastic.co/u/Stef_Nestor)\
**Post date:** [September 22, 2021, 6:00pm UTC](https://discuss.elastic.co/t/debian-7-x-repository-broken/284906/2 "2021-09-22T18:00:52Z")

</div>

Hello! Thanks for reaching out & apologies for the inconvenience. Our team's currently investigating (id: es#4929) & should have an update soon.

---

<div class="post-metadata">

**Author:** ![Stef\_Nestor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stef_nestor/32/85483_2.png) [@Stef\_Nestor](https://discuss.elastic.co/u/Stef_Nestor)\
**Post date:** [September 22, 2021, 6:40pm UTC](https://discuss.elastic.co/t/debian-7-x-repository-broken/284906/3 "2021-09-22T18:40:57Z")

</div>

Elastic Infra's still investigating. If you don't mind, let's consolidate this to [this parent Discuss post](https://discuss.elastic.co/t/centos-7-metadata-file-does-not-match-checksum-during-yum-update/284913) for updates.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 20, 2021, 6:41pm UTC](https://discuss.elastic.co/t/debian-7-x-repository-broken/284906/4 "2021-10-20T18:41:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.