Best posts made by JGallo

@cnkpadobi

You might want to switch to the working branch.

FOG Install instructions on wiki

Here you will see instructions on how to install Git and switch to working branch. Hope this helps.

@Wayne-Workman @Tom-Elliott I just imaged one computer with the empty storage group in the location plug in and it pulled the image from the slave node. I’m going to leave it like that for now and when we go to image the lab later today, I will report. Like I said before, it is strange that the storage group is not visually represented on the location management page but once you click on the location, you can see that the storage group is defined.

@sebastian-roth

@Tom-Elliott
I tried to test this as well. I’m on SVN 6080 and when creating a group and hitting create, it takes me to a separate page with this message

{“msg”:“Successfully added selected hosts to the group!”}

When I hit the back button, then go to groups, the group is there along with random clients I did not check to add into this group. Really strange. Also forgot to mention that when I tried to delete the group, it also does not delete the clients in that group.

@george1421 @Tom-Elliott I will go ahead and restore the fog.postinit script back to its intended use. Call the patch.fullreg script to reflect exactly what we are trying to do, that is to copy our custom script and replace /bin/fog.man.reg That way as @george1421 has said to prevent any updates from replacing the script by accident.

@dpotesta50

looks like your FTP credentials are not matching properly. The error is not on the Windows 10 machine but on the fog server ftp credentials.

@joe-gill We need more tabs!!!

@george1421

I will check tomorrow and place the results here.

@klkwarrior May I suggest the following:

1. If your project of imaging lots of machines are on the same network, maybe image as a group based on the model computers? Or are the computers at various sites?

2. Not sure if latest working branch has this but I know that 1.6 does have the deploy image option from the client which just basically allows for you to choose the image to deploy rather than defining anything. That I think is what is probably going to accomplish for you and you don’t have to do anything on the web UI in the sense of adding additional functions. Just define the image, upload, and then begin imaging.

@sebastian-roth

Sweet. The default setting for the loglevel is 4. Taking it down to 3 no longer produces those USB errors. Thank you. The computer does register and I can image but those USB errors were extremely annoying. Seems like this will suppress those messages and works just fine now.

Custom FOG Full host registration

This guide is to allow you remove questions asked during the full host registration process. In previous versions of FOG, the only way to customize this was to modify the /bin/fog.man.reg manually. The instructions on this link are for FOG versions 1.2.0 and below:

https://wiki.fogproject.org/wiki/index.php?title=Create_Custom_Fog_Registration_menu

In FOG 1.4.0rc2 and higher, we must use post init scripts. Once a major update is released, this tutorial can be modified to reflect those changes.

Let’s start by creating a few scripts. Secondly we will modify the fog.postinit script to call our custom scripts. Our first script that we will create will be called fog.man.reg.fix which will be a modified version of the script in /bin/fog.man.reg This script is actually everything that is performed when selecting the full host registration option when you boot into FOG but this tutorial utilizes post init scripts to “copy” our customized script and replaces /bin/fog.man.reg script. So let’s go to our steps and begin:

Step 1
Obtain a copy of /bin/fog.man.reg so we can modify it to our needs.
Here is the link on github:

https://github.com/FOGProject/fogproject/blob/master/src/buildroot/package/fog/scripts/bin/fog.man.reg

We can go ahead and place this file under /images/dev/postinitscripts/ and rename it to fog.man.reg.fix so we can reference it later.

As in the Wiki link earlier above, we will now modify the fog.man.reg.fix script using the same concepts. A good rule of thumb is for every question you want to remove during the full host registration process, you will have to delete the variable towards the bottom of the code.

ex:

askme=""
while [[ -z $askme ]]; do
    echo -n "    Would you like to associate this host with groups? (y/N) "
    read askme
    case $askme in
        [Nn]|[Nn][Oo]|"")
            askme="N"
            ;;
        [Yy]|[Yy][Ee][Ss])
            setIDs "groupid" "group" "true" "" 20
            group64=$groupid
            ;;
        *)
            askme=""
            echo " * Invalid input, please try again"
            ;;
    esac
done

So if you don’t want to be asked this question above, you must delete everything between askme=“” and done. Then towards the bottom of the code, you will see the following:

while [[ -z $res ]]; do
    res=$(curl -ks --data "mac=$mac&advanced=$(echo -n 1 | base64)&host=$host&imageid=$imageid&primaryuser=$primaryuser&other1=$other1&other2=$other2&doimage=$realdoimage&doad=$blDoAD&location=$location64&username=$user64&groupid=$group64&snapinid=$snapin64&productKey=$productKey" http://${web}service/auto.register.php 2>/dev/null)
    echo "$res"
    usleep 2000000
done

Look for the section where it says groupid because that is the variable we no longer need. So from there delete the following: &groupid=$group64 The & must be in the front of the variable being removed in case another variable must follow.

By following the steps on the Wiki link

https://wiki.fogproject.org/wiki/index.php?title=Create_Custom_Fog_Registration_menu

We can follow the same concepts. Now we can just really skip any modifications to the inits.

Step 2
Now that we have a customized fog.man.reg.fix script and placed it in the proper directory, we can now create the script that fog.postinit will call. We will call this script patch.fullreg and use the following code:

#!/bin/bash

echo "Installing Patch"
debugPause

cp -f ${postinitpath}fog.man.reg.fix /bin/fog.man.reg

echo "Done Patching stuff"
debugPause

We then save that file also in the same directory that fog.man.reg.fix and fog.postinit which is /images/dev/postinitscripts/ As you can see, we are really just copying our custom fog.man.reg.fix script to fog.man.reg This allows us to basically simplify our full host registration process. Through this process, we can now remove questions like product key, user1, user2, primary user, active directory, etc.

Notes: This will not work if using fog 1.3.0 - 1.4.0 rc 1 from my understanding. I’m sure I will be updating this post and making changes to improve the language and references. Hopefully with this, we can update the Wiki page to reflect the newer version of FOG and utilizing post init scripts in the future.

@ravigon

No. As long as the correct commands in the fog.postinit that calls the patch.fullreg script and patch.fullreg copies correctly and that there are no syntax errors in fog.man.reg.fix you should be fine. Fog will know to call patch.fullreg when running a full host registration.

@Wayne-Workman

@Sebastian-Roth remoted in and looks like mysql was limited to 150 connections. He raised it to 250 and now it would appear fixed so far. I’m keeping an eye on the max used connections and it hasn’t gone over 161 so I must have been hitting that 150 max. Thanks for all your help here. Greatly appreciate it.

@jj-fullmer

It works now. I did a git pull from working branch and don’t have problems now.

@nrg

I also had the valid database connection error which turned out to be a limit that I was hitting with mysql. Could be related and you could go into mysql and check to see if you are hitting that provided your credentials for your nodes are correct. It sounds like they are because replication is working.

Discussion about valid database connection

If you go into mysql, you could check by running the following command:

mysql> show variables like 'max_connections';

that max value if it’s being hit will show in the following command:

mysql> show status like '%onn%';

If the output of that is higher than the max connections then there is your problem. Read through the discussion and see if it can help what your dealing with.

@nrg

Just realized your node is on 1.2 and your FOG server is on 1.5 RC10. I would update your storage node first if that’s an option. Many changes since 1.2

May I suggest the following:

https://forums.fogproject.org/topic/9851/custom-full-host-registration-menu-for-1-4-0-rc2-and-later

You may edit the registration process by eliminating questions you don’t want to deal with. Hence cutting the registration process depending on how many questions you eliminate. What I have done is removed unnecessary questions like product key, group, etc so that only three important questions are asked. Name of host, image ID, location, and then image now. If you have groups, you could just use the web ui to group them together. Mind you, this is only a suggestion to your scenario as my environment has several storage nodes and master nodes within those storage nodes and I replicate images across domains. Pretty cool in the end that FOG is capable of this.

@Sebastian-Roth I switched over to replication branch and updated all storage nodes along with my fog server. I uploaded image and it seemed like its working fine for original image. I haven’t updated the image since its very new but I when I have a chance, which will be very shortly since a project im currently working on will allow me to update an image on an existing one, I will go ahead and updated it and tail the replication log.

I also noticed in a different post that another user did the same thing and tested replication. Looks like the changes in the replication branched have work. I will update as well once i upload an image to an existing one to see if the updated image replicates properly to storage node.

@Tom-Elliott @Wayne-Workman Worked like a charm. The lab imaged with 20 going on at once with both nodes active and remaining clients were placed in line to wait until slots opened up. Thank you both for all your help.

@Sebastian-Roth So I went ahead and switched to dev-branch and upgrade nodes along with fog server. Seems like it’s working fine and the storage group info is now displayed. Thank you again for your help in this.