Downloading inits, kernels and FOG Client...failed
* Downloading inits, kernels, and the fog client..............Failed!
I get the above when trying to update one of my storage nodes. That node is located in a plant that has very slow internet access (~100 KBps). Is it timing out? Any work around?
It’s not behind a proxy if that’s relevant.
@moses Possibly just start by re-installing those ssl and cert packages?
rpm -qa | grep -e ssl -e certto find the packages.
@Sebastian-Roth Yeah, I’ve tried all of that. I’m just going to reinstall the OS. Something wonky happened.
@moses Possibly something wrong with your
/etc/pki/tls/certs/ca-bundle.crt? Check this our: http://serverfault.com/questions/437546/centos-openldap-cert-trust-issues
@Wayne-Workman It looks like my problem is with SSL. Here’s the output of
[root@localhost ~]# curl -I -v https://google.com * About to connect() to google.com port 443 (#0) * Trying 220.127.116.11... * Connected to google.com (18.104.22.168) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * Server certificate: * subject: CN=*.google.com,O=Google Inc,L=Mountain View,ST=California,C=US * start date: Jun 16 08:37:32 2016 GMT * expire date: Sep 08 08:29:00 2016 GMT * common name: *.google.com * issuer: CN=192.168.2.44,C=US * NSS error -8172 (SEC_ERROR_UNTRUSTED_ISSUER) * Peer's certificate issuer has been marked as not trusted by the user. * Closing connection 0 curl: (60) Peer's certificate issuer has been marked as not trusted by the user. More details here: http://curl.haxx.se/docs/sslcerts.html
Never dealt with this in Linux, any experts out there? This happens with any SSL URL.
@moses There’s an option to keep going after failure. Then you can download the inits and kernels manually again.
I don’t use it very often so I forget what it is, but if you run the installer like this:
./installfog.sh --helpit’ll give you a menu with options.
@Wayne-Workman Failed again, unfortunately.
@Wayne-Workman I’m on round three, I’ll see if it works this time.
I don’t think there’s a timeout, most likely the connection is dropping.
Just try again.