Ubuntu Trunk Checksum failed

[george1421]

@reflexxion Just looking what you posted and the resolve.conf is really wrong, unless you had a type-o the local host is 127.0.0.1 and not 127.0.1.1

[reflexxion]

@george1421 I see that but, I’m not quite sure how that happened as I made no changes to those settings during install other than pointing it to my dhcp and dns server.

[reflexxion]

I’m going to run a CLEAN install of both OS and fog… may skip 1.2.0 and go straight to TRUNK and see what happens.

[Tom Elliott]

@reflexxion Why not just add to the /etc/resolv.conf file a real nameserver:.

Something like:

nameserver 8.8.8.8

Then try pinging google.com

[reflexxion]

@Tom-Elliott I tried that as well still wouldn’t take… If it fails again during this install I’ll try that again.

[reflexxion]

@Tom-Elliott P.S. ping always worked and always resolved with those settings. It just will not get the inits and kernels.

[reflexxion]

Alright, after a clean install and NOTHING else accept hardcoding the NIC, I checked the resolve.conf file and it was defaulted to 127.0.1.1

I manually changed it to nameserver 8.8.8.8 as suggested, verified ping still worked and then started the TRUNK install via svn

still fails at the same point “Getting checksum files for kernels and inits… Failed!”

[george1421]

After digging into the code I see the devs are using curl to get the checksums with

curl -ko "checksums" https://fogproject.org/inits/index.php

The above is a hacked version of what they are doing. What I would like you to do is the following

1. From the fog server try to ping fogproject.org to ensure it responds with a proper internet address.
2. Copy and paste in the above command, do this when you are in root’s home dir. The output of this command should be a file called checksum in root’s home dir (or current dir). If you look into that file there will be a digial fingerprint of the inits. What is in there isn’t important as long as it downloads and it has some content ending with the name of the file.

[reflexxion]

@george1421 Gentlemen, I’m actually done for the week, so I’ll try this first thing Monday morning when I get in and let you know. I appreciate all of the timely responses and advice.

[Wayne Workman]

@reflexxion It might be possible to install fog and tell it to continue in the event of a failure, and just download the kernels and inits later… ./installfog.sh -X I think. And at the bottom of this article you’ll find the manual methods to download the very latest: https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

[reflexxion]

@george1421

[Tom Elliott]

@reflexxion said:

advice.

What’s your server’s time?

[reflexxion]

@Tom-Elliott the servers time and date are correct +/- 2 mins

10:55 am EST
3/21/2016

[Tom Elliott]

@reflexxion Can you ensure they’re correct?

This can be done with

sudo ntpdate pool.ntp.org or sudo service ntp restart

Of course NTP and/or the ntpdate utility will need to be installed.

[reflexxion]

@Tom-Elliott ran and verified.

[Tom Elliott]

@reflexxion Now can you try: curl -ko "checksums" https://fogproject.org/inits/index.php

[reflexxion]

@Tom-Elliott same output as before.

[Tom Elliott]

@reflexxion Then I don’t know.

Something is wrong with your system. Are you sure it’s supposed to be EST and not EDT? EDT means one hour ahead. That should still be in the write timing for the ssl stuff to work, but I don’t know what’s going on with your system/network.

Something indeed is wrong, but it’s not coming from FOG at all.

[reflexxion]

Let me do a little more digging on my end and see what I can find out… If I come up with anything I’ll be sure to post it here.

Thanks for all the troubleshooting.

[reflexxion]

@Tom-Elliott hey Tom, I just re-ran that curl command again without the “https” and it returned data… does that mean it’s an ssl issue?