cdlliuy
commented
6 years ago @cwb124 , from the proxy logs, it looks like the dependencies are not downloaded correctly which led to the error of api packaging failure.
Could you check whether all the dependencies were downloaded correctly in your "blobs" folder? Here is an example of mine:
>> ls -l -R blobs
total 0
drwxr-xr-x 3 root root 96 Sep 21 2017 golang
drwxr-xr-x 3 root root 96 Sep 21 2017 maven
drwxr-xr-x 4 root root 128 Sep 21 2017 nodejs
drwxr-xr-x 4 root root 128 Sep 21 2017 openjdk
blobs/golang:
total 164112
-rw------- 1 root root 84021919 Sep 21 2017 go1.7.4.linux-amd64.tar.gz
blobs/maven:
total 16592
-rw------- 1 root root 8491533 Sep 21 2017 apache-maven-3.3.9-bin.tar.gz
blobs/nodejs:
total 41768
-rw------- 1 root root 12041020 Sep 21 2017 node-v6.9.2-darwin-x64.tar.gz
-rw------- 1 root root 9342556 Sep 21 2017 node-v6.9.2-linux-x64.tar.xz
blobs/openjdk:
total 299320
-rw------- 1 root root 75550921 Sep 21 2017 openjdk-1.8.0_101-x86_64-mountainlion.tar.gz
-rw------- 1 root root 77696717 Sep 21 2017 openjdk-1.8.0_101-x86_64-trusty.tar.gz
cwb124
qibobo
boyang9527
I have a linux box with no internet access but has access via a proxy. I have set http_proxy and https_proxy on the box and I can curl -x successfully through the proxy. However when I run
bosh create-releaseit gets a good chunk of the way through but then dies on the apiserver part:Added package 'apiserver/b0ab0e6e8317cd7292c8230d491e13f232f623c7'It looks like those scripts are not honoring the proxy? I was watching my squid proxy logs throughout the create-release process and it was getting a lot of traffic until the apiserver portion started, and then there wasn't another entry in the proxy log while the apiserver part was running and eventually failed. It's not using the http(s)_proxy settings. Here's a couple snippets of the error:
apache-maven-3.3.9/bin/mvnyjp apache-maven-3.3.9/conf/ apache-maven-3.3.9/conf/logging/ apache-maven-3.3.9/conf/logging/simplelogger.properties apache-maven-3.3.9/conf/settings.xml apache-maven-3.3.9/conf/toolchains.xml apache-maven-3.3.9/lib/ext/ apache-maven-3.3.9/lib/ext/README.txt [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building db 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:09 min [INFO] Finished at: 2018-03-28T15:39:32+00:00 [INFO] Final Memory: 9M/111M [INFO] ------------------------------------------------------------------------ [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5 from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.44.215] failed: Connection timed out -> [Help 1]Mar 28, 2018 3:41:54 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute INFO: I/O exception (java.net.NoRouteToHostException) caught when processing request to {s}->https://repo.maven.apache.org:443: No route to host Mar 28, 2018 3:41:54 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute INFO: Retrying request to {s}->https://repo.maven.apache.org:443