Closed chris-patino-zartico closed 1 year ago
Oh wanted to add to this, I ran the curl commands locally and they work just fine so links aren't broken.
It's possible that BunnyCDN which we use had an intermittent connectivity issue.
If you try again now is it working?
exit(35)
as indicated in the log corresponds to an SSL connect error.
Still giving same error, not sure how to proceed with the SSL error. I felt a past closed ticket was seeing something similar and they mention something about the execution was being doing through a proxy and was causing the curl commands to fail, but I fear that is past my realm of expertise :/
So it could've been the version of the Ubuntu OS I was using. Went from Ubuntu 22.04 to 20.04 and worked just fine. (Used exact same steps did nothing differently.
So I was consistently getting this error when running
pelias download wof
Here is my step to set this up (setting up on a VM on GCP 32 cpus/64 GB of Ram. Here is my step set it all up (pretty much followed docker readme to a t), and I've also actually stood up the Texas project successfully and worked just fine, its just the planet that does this.
Error: Command failed: curl --silent -L https://data.geocode.earth/wof/dist/sqlite/inventory.json at checkExecSyncError (child_process.js:635:11) at Object.execFileSync (child_process.js:653:15) at module.exports (/code/pelias/whosonfirst/node_modules/download-file-sync/index.js:3:6) at generateSQLites (/code/pelias/whosonfirst/utils/download_sqlite_all.js:56:16) at download (/code/pelias/whosonfirst/utils/download_sqlite_all.js:108:29) at Object.<anonymous> (/code/pelias/whosonfirst/utils/download_sqlite_all.js:126:1) at Module._compile (internal/modules/cjs/loader.js:999:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) at Module.load (internal/modules/cjs/loader.js:863:32) at Function.Module._load (internal/modules/cjs/loader.js:708:14) { status: 35, signal: null, output: [ null, '', '' ], pid: 13, stdout: '', stderr: '' } ERROR: 1
I ran the pelias download osm and got a almost identical error, I've also ran these several times (hours apart) so I dont believe it was server issue. Any help is greatly apppreciated!