in centos 7, bash deploy.sh is wrong about heavydb

[andrewseidl]

Try running it again, there might just be some intermittent issues with your upstream nameserver. You clearly can resolve it since that's the domain the deploy script was downloaded from, but it might be that the second lookup isn't cached locally and your upstream nameserver fails to resolve again.

If it's still an issue, try adding the following line to your /etc/hosts file:

72.28.97.165 internal-dependencies.mapd.com

[xuxilei]

after edit "72.28.97.165 internal-dependencies.mapd.com"
[root@localhost ~]# sudo bash deploy.sh
...................................

• FLAG=latest

• '[' '' == --testing ']'

• sudo wget --continue https://internal-dependencies.mapd.com/mapd-deps/mapd-deps-latest.tar.xz

--2017-05-23 03:17:12-- https://internal-dependencies.mapd.com/mapd-deps/mapd-deps-latest.tar.xz

Resolving internal-dependencies.mapd.com (internal-dependencies.mapd.com)... 72.28.97.165

Connecting to internal-dependencies.mapd.com (internal-dependencies.mapd.com)|72.28.97.165|:443... failed: Network is unreachable.

[xuxilei]

the computer throught two proxy to internet

[dwayneberry]

Hi

i have just tried to download this bundle from an external network and all appears to be working fine.

please review your network configuration, as this appears to be a network issue on your network side.

[dwayneberry]

If you have no luck with getting the pre built dependencies you can build your own by following the details here

https://github.com/mapd/mapd-core#centos-7

And the script here: https://github.com/mapd/mapd-core/blob/master/scripts/mapd-deps-linux.sh

[xuxilei]

in mapd-deps-linux.sh: "download" refer to ?

[andrewseidl]

It's a function at the top of the script: https://github.com/mapd/mapd-core/blob/f87d5deddfeda9eb539061bf507c65d6f2151ff7/scripts/mapd-deps-linux.sh#L18-L20

download() {
    wget --continue "$1"
}

Feel free to replace the wget with curl -O if that works better with your proxies.

[randyzwitch]

Closing, as this appeared to be a network issue, not a MapD issue. Please feel free to open another issue if this behavior persists