Image drop issues after upgrade from 1.3.3 to 1.3.5
-
@Tim-Reynolds Does your fog server have direct Internet access? The fog installer needs to download some files from the fog mothership to complete the install.
-
@george1421 It does have direct access.
-
@Tim-Reynolds from the linux console you can ping fogproject.org?
-
@george1421 I can’t ping, but it resolves it as 162.213.199.177. I can browse to it from Firefox.
-
Try now please.
-
@Tom-Elliott I’m still unable to. I can ping Google.
-
You don’t need to ping.
You can retry the installer.
-
@Tom-Elliott Copying binaries where needed still failed.
-
@Tom-Elliott It unzipped the binaries successfully, it just wouldn’t copy them.
-
That doesn’t make any sense. What do you mean “it unzipped but wouldn’t copy them?”
What’s output of
df -h? -
@Tom-Elliott Attached is a document with the results of df-h and the install.0_1494274173932_1.4.0-rc9
-
@Tim-Reynolds the attachment is a text file.
-
@Tim-Reynolds Did the file attachment shed some light on the problem?
-
@Tim-Reynolds Seems like you have enough free space on the disk. Tom is right, this does not make much sense. Do you see anything in the install error log?
-
I encountered another user having a similar problem with this yesterday. It happened to be the proxy/filter was causing the binary data not to be stored properly. The binaries file would download, but the data was not available and would cause a failure. @Tim-Reynolds Please see if you have a content filter that may be causing problems.
-
@Tom-Elliott I have a rule on the filter that ensures that the content filter is disabled on the Fog server’s IP address. Also, I have the firewall allow all traffic to the Fog server.
-
@Tom-Elliott The issue has been resolved. I downloaded 1.4.0 SVN6069 and that install worked.
