Trunk install, getting checksum files for kernels a....failed!
-
Hello,
I’m french, I’m trying to update fog 1.2.0 to the latest trunk version and it fails on the step “getting cheksum files for kernels and inits…failed!”
Description: Debian GNU/Linux 7.6 (wheezy)
Release: 7.6
Codename: wheezyLinux fog 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
you are behind a proxy
Thank for your help
-
@hfredh So are you connected to the internet through a proxy server or directly?
-
I am connected to the internet through a proxy server
Thanks -
@hfredh The command line does not know about your proxy server. Usually most tools use the same environment variables. Try this before running the installer:
export http_proxy=http://<proxy_server_ip>:<proxy_server_port> export https_proxy=http://<proxy_server_ip>:<proxy_server_port> export ftp_proxy=http://<proxy_server_ip>:<proxy_server_port> export no_proxy="localhost,<fog_server_ip>"
If this is working you better put those settings in your bashrc or something as well. Ask google about ‘linux http_proxy’ and I am sure you will find instructions.
-
Thank, it’s ok
RESOLU -
i am getting this error also but i am not behind a proxy. any suggestions?
-
@edv-schuster what error?
-
@edv-schuster Does your fog server have direct (or indirect) internet access and can it resolve host names on the internet (i.e. www.google.com)? The fog installer reaches out to download the current kernel and inits during the install process.
-
@hfredh said:
getting cheksum files for kernels and inits…failed!
I am getting exactly this error during install. i have direct internet access. no idea, why the error occures. how can i track this down?
i run the ./installfog.sh as root and gave the freshly downloaded git-install-directory full access (777)
l use a freshyl installed deb 8…
-
@edv-schuster Try this from the command line on your FOG server:
wget --no-check-certificate https://fogproject.org/kernels/index.php
(does it work? If not, what error do you get?) -
ok guys. first of all… tnx for the quick responses!
dont blame me. i rebooted the machine and tried once more… exactly the same… and it worked !!!
no clue, what happened… but tnx for your replies - u are quicker than a gunshot