Developers

@george1421 wont

@george1421 there is a message but the client doesn’t do anything with inventory updates. That is done through Fos as a task. There’s dedicated inventory task, or the next deploy to the machine will update the inventory info as well.

Edit the images d1.fixed_size_partitions file and add :1 if it’s not present already. It should be but it sounds like it’s not.

@loosus456 There’s a few posts, but it’s far from an expectation, and there are ways to set it up already available by using the storageLocation and storageLocationCapture elements. The idea for the installer is to make it easier to get up and running.

As for the issue with the network interfaces, I’m guessing you’re trying to run the installer from the master branch? I ask this as it was found and I believe fixed in dev-branch (which will soon become master). Would you mind switching to the dev-branch and see if the issue is still present?

@SPaceSkillz1 Which version of Windows 10 do you exactly have? Please run the command (Win+r) winver and post a picture of that here.

@pdit Ok, now we know that our link state check in the startup scripts is indeed working as well for your network card. So question remains, why does it take more than 35 seconds after boot up to change its link state to UP?

Sure we can adjust the wait time for you but I suspect this time to be caused by either spanning tree or energy efficency settings on your switch.

You said that you have an isolated setup with a dumb switch. Which switch model exactly are you using??

@loosus456 it only asks if the location is specified before install and the location is not found.

By default, it will choose /images

@mparlette you can set the location inline with
storageLocation=“/home/images” ./installfog.sh -y

@pdit Ahhhh, too bad, we can’t see the output as your screen does not seem to be properly calibrated with the resolution used by the Linux kernel. Can you try re-calibrating the display before running the command so we get all the information on the left end of the output. Otherwise we need to do some bash magic. Running the following command lines should also work if you can’t fix the display stuff:

linkstate=$(cat /sys/class/net/eth0/carrier)
[[ $linkstate -eq 1 ]] && echo "Yeah, we got link here" || echo "Tooooo bad, Linux kernel is not able to detect the link"

@mwolfe60 Hope you have both nodes still on 1.5.4! Please make sure you read and understand the release notes for 1.5.5 - https://news.fogproject.org/fog-1-5-5-officially-released/

IMPORTANT NOTICE:
Nodes being on different versions (1.5.4 vs. 1.5.5) will replicate images over and over again as some of the hashing code needed to be changed. Therefore we advise you to update all nodes in one go! Please make sure you stop replication on the master first systemctl stop FOGImageReplicator; systemctl stop FOGSnapinReplicator, then update the storage node(s) and then update master node as a last step.

Now to your points:

I’m not sure where the image replicator logs are located to review.

Take a look at /opt/fog/log/fogreplicator.log on your FOG server.

I should also mention that today we attempted to update the server 1.5.5 and the update failed.

We need more details to be able to help. At what stage exactly did it fail? Please post the exact output you get. Either as text or take a picture and post here.

… in the past with auto updates filling up the root file system.

Have you made sure there is sufficient space on both nodes?? Run df -h and post output here.