Downloading binaries needed..... Failed!
-
@george1421 Hi thanks. No not that. I’ve only added proxy details through the UI. Sounds like what you are saying is i need to invoke those setting in the terminal session as well.
Ive run the export command now before running the install.
Its in the process now. Ill let you know how it turns out. -
@george1421
Hi George,So i ran export command for “http_proxy” and “no_proxy”. We dont have a proxy for ftp specifically.
I still ended up with the “failed” line at the end. -
@nvdp2002 You may also need the https line. If you key those in per session (instead of adding them to the profile) you will need to key them in for each session.
Does your proxy server require authentication or is it a straight proxy?
You can test if the proxy settings work correctly by issuing this command (assuming that wget is installed in your linux OS)
wget https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
That will download the latest kernel to the current directory on your fog server. You don’t need the file, its just to test to ensure the proxy connection is working correctly
-
@george1421 Its a straight proxy. No authentication.
So i tried 2 ways. one with the https and one without.
the result without is :–2019-04-26 10:09:19-- https://fpgproject.org/kernels/kernel.TomElliot.4.19.6.64
Resolving fpgproject.org (fpgproject.org)… failed: Name or service not known.
wget: unable to resolve host address ‘fpgproject.org’The one with https is:
–2019-04-26 10:14:51-- https://fpgproject.org/kernels/kernel.TomElliot.4.19.6.64
Resolving e.e.mcorp.com (e.e.mcorp.com)… failed: Name or service not known.
wget: unable to resolve host address ‘e.e.mcorp.com’So i went and entered the http proxy directly into the settings and got a bit further.
What i get now is :
wget https://fogproject.org/kernels/kernel.TomElliot.4.19.6.64
–2019-04-26 15:58:03-- https://fogproject.org/kernels/kernel.TomElliot.4.19.6.64
Resolving fogproject.org (fogproject.org)… 162.213.199.177
Connecting to fogproject.org (fogproject.org)|162.213.199.177|:443… failed: Connection timed out.
Retrying.That mean anything to you?
-
@nvdp2002 You keep having typos in the URLs! Try copy&paste this one:
wget https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
It’s “Elliott” (with two t’s) and “Kernel.” (with uppercase k)…
-
@Sebastian-Roth well that’s embarrassing…
Sorry.
I copied and pasted now and this is the result.wget https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
–2019-04-26 16:51:41-- https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
Resolving fogproject.org (fogproject.org)… 162.213.199.177
Connecting to fogproject.org (fogproject.org)|162.213.199.177|:443… failed: Connection timed out. -
@nvdp2002 in this same session you keyed in the wget command
set | grep proxy
It almost appears to not be using the proxy variables.
It has to work because our fog server is behind a proxy too and I don’t have issues.
-
@Sebastian-Roth Just wanted to add that after the last test i tried to put the address direct into the browser and it downloaded without issues.
-
@george1421 Just wanted to let you know it can connect now. The HTTPS proxy was nonstandard. Thanks for taking the time to help with this. Ill let you know if the install completes this time. Thank you very much.
-
@Sebastian-Roth Hi. Seems to be working now. Thanks for your time. Its very much appreciated. Ill let you know how the install goes this time round.
-
@george1421 Hi.
So your file come through fine
$ wget https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
–2019-04-29 09:13:03-- https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
Connecting to 172.25.3.42:8080… connected.
Proxy request sent, awaiting response… 200 OK
Length: 8368800 (8.0M) [application/octet-stream]
Saving to: ‘Kernel.TomElliott.4.19.6.64’Kernel.TomElliott.4 100%[===================>] 7.98M 1.90MB/s in 4.2s
2019-04-29 09:13:09 (1.90 MB/s) - ‘Kernel.TomElliott.4.19.6.64’ saved [8368800/8368800]
But i still get the binaries failed line when running the install.
So close…
-
@nvdp2002 The installer uses
curl
instead ofwget
but both usually make use of the same environment variables. Please try this:curl -ko /tmp/Kernel.TomElliott.4.19.6.64 https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
-
@Sebastian-Roth Hi, That worked aswell.
$ curl -ko /tmp/Kernel.TomElliott.4.19.6.64 https://fogproject.org/kernels/Kernel.TomElliott.4.19.6.64
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8172k 100 8172k 0 0 2329k 0 0:00:03 0:00:03 --:–:-- 2329k -
@nvdp2002 So if curl is working then so should the fog installer. It is still failing?
-
@george1421 Yes still failing.
This was the last line in the log file:
Apr 29 12:33:54 vmubuntu systemd[1]: Starting MySQL Community Server…
Apr 29 12:33:55 vmubuntu systemd[1]: Started MySQL Community Server.
ERROR 1396 (HY000) at line 1: Operation ALTER USER failed for ‘root’@‘127.0.0.1’Does that help ?
-
@nvdp2002 well now that tells us you got passed the downloading issue and now for some reason mysql is giving you a problem.
Since you are running on ubuntu, I guess we can assume that this issue is coming into play. https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy
The issue is fog assumes that the root user shouldn’t have a password where if it does the mysql commands will fail. Ubuntu is changing the default when an update is applied so fog is now out of sync with what ubuntu installed.
-
@nvdp2002 said in Downloading binaries needed..... Failed!:
ERROR 1396 (HY000) at line 1: Operation ALTER USER failed for ‘root’@‘127.0.0.1’
This might be ok on Ubuntu. I am not exactly sure at the moment. We try different mysql commands at that stage and one or the other might fail.
Please take a picture of the installer output you see on screen as well so we know exactly where it fails.
-
Hi Sebastian, Sorry for the slow response.
Ive attached the log files.That seems to have the same output.
-
@nvdp2002 The last we see in the log is
Is the MySQL password blank? (Y/n)
- how do you answer the question? Do you know the password of your database? Is it blank or set?