Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"assets_precompile", "cmd"=>["su discourse -c 'bundle exec rake assets:precompile'"]}
c13084f0c50befc27d34645224f4b1680c28eda7e05030e8eb0114ff0e311d96
**FAILED TO BOOTSTRAP** please scroll up and look for earlier error messages, there may be more than one
```
If I download it on that server using `wget`, it untars fine.
EDIT: nope, I was downloading the wrong path (`https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.tar.gz`) whereas we use:
```plaintext
○ → wget https://geolite.maxmind.com/geoip/databases/GeoLite2-City/update
--2019-06-10 14:36:54-- https://geolite.maxmind.com/geoip/databases/GeoLite2-City/update
Resolving geolite.maxmind.com (geolite.maxmind.com)... 104.17.201.89, 104.17.200.89, 2606:4700::6811:c959, ...
Connecting to geolite.maxmind.com (geolite.maxmind.com)|104.17.201.89|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 28565904 (27M) [application/gzip]
Saving to: ‘update’
update 41%[===============================>] 11.17M 67.4KB/s eta 4m 27s
```
… which is evidently throttled to 64KBps. That’s harsh on rebuild times.
EDIT: seems that file is no longer throttled, I was able to pull it from multiple places at full speed and the rebuild succeeded as well.
(we should still fix the fact that it makes the build 💥)
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [10 Junho , 2019 21:16 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/2 "2019-06-10T21:16:06Z")
To me the only fix left here is to stop maxmind on precompile by default and rely on the somewhat stale db in the base image
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [10 Junho , 2019 21:20 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/3 "2019-06-10T21:20:18Z")
Maybe have an environment variable for people who really want it fresh? It seems like some people really care but others, not so much.
---
### Author:  [@supermathie](https://meta.discourse.org/u/supermathie)
#### Post date: [10 Junho , 2019 21:31 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/4 "2019-06-10T21:31:12Z")
It gets updated during runtime by a scheduled job so it doesn’t matter if it’s a bit stale during build.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [10 Junho , 2019 21:55 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/5 "2019-06-10T21:55:54Z")
The problem is that we would be allowing inconsistent state, location shows up right, rebuild, location is wrong
I much prefer consistency
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [11 Junho , 2019 05:49 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/6 "2019-06-11T05:49:15Z")
I’ll take a working instance with a slightly stale database over a failed rebuild any day of the week.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [11 Junho , 2019 06:31 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/7 "2019-06-11T06:31:13Z")
You can already do this today:
>
Set `DISCOURSE_REFRESH_MAXMIND_DB_DURING_PRECOMPILE_DAYS` to taste.
Set to 0 for… just don’t do anything during precompile, rely on base image for maxmind db.
Set to 100 for… I don’t care this can be pretty old, but not SUPER old.
* * *
The open discussion here is:
1. Should we add an `I don't care if maxmind update fails during precompile` option?
2. Should we add a “scheduled job” that updates maxmind DB if it is N days old?
I am **against** 1, cause it leads to “inconsistent state post rebuild”. We are used to having a very consistent state after rebuilds and this adds a wild card.
I am not strongly against (2) but one issue here for our own hosting is that we could not even use (2) cause we would likely get us banned off maxmind.
So I am not sure what more to do here.
If self hosters were complaining a lot about “rebuilds” failing due to maxmind I would be open to changing the default for `DISCOURSE_REFRESH_MAXMIND_DB_DURING_PRECOMPILE_DAYS` to 0.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [17 Junho , 2019 21:01 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/10 "2019-06-17T21:01:15Z")
> [@sam](#):
>
> If self hosters were complaining a lot about “rebuilds” failing due to maxmind
Looks like this is such a complaint:
[https://meta.discourse.org/t/restore-db-problem/120563/7](https://meta.discourse.org/t/restore-db-problem/120563/7)
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [21 Junho , 2019 16:58 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/11 "2019-06-21T16:58:11Z")
This appears to be MMDB related as well. Pardon the screen shot, but it’s what the client sent and it appears that he tried again and the upgrade worked.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [21 Junho , 2019 23:50 UTC](https://meta.discourse.org/t/rebuild-failing-due-to-maxmind-db/119942/12 "2019-06-21T23:50:22Z")