Posts made by Wayne Workman

Wayne Workman

I rebuilt my master and slave from scratch. Everything worked as expected, this topic can be resolved.

Wayne Workman

Any plans on spreading the colors evenly across the color spectrum? Just wondering. Back in the day, it seemed like the colors would automatically spread across the color spectrum.
Firefox_Screenshot_2019-09-20T00-43-12.150Z.png

Wayne Workman

Just close it. Maybe I’ll put together a Galera tutorial one of these days for FOG.

Wayne Workman

@agray said in Golden Image Deploy Problems:

I don’t have drivers specific for the 3060, but I do have 3050 which are close. Could that be the problem?

Yes, it could be. The wiki also has notes about sysprepping with the fog client that you should read through:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

Wayne Workman

Do you have fresh installs or upgraded FOG master node?

It’s an upgraded master.

Do you have DB setup with root password set?

No.

I’m going to just blast this master and make a new one. I’ll see how that goes.

Wayne Workman

Hey there,

I’m trying to add a fog storage node, it’s not working.

My fog master is version 1.5.7, Commit ID is a83b77d2c7f6a90da950d72997893ae11f85dc37

My Fog storage node is version 1.5.7, Commit ID is a83b77d2c7f6a90da950d72997893ae11f85dc37

Both are Debian 9, fully patched.

There’s two problems really. The first problem is that I remember the storage node installation process would add the node to the remote database for you. I helped work this out with @Tom-Elliott a couple years ago. This feature is not working.

The second problem is that the manual storage node add process via the GUI isn’t working. I fill out all of the required information and click “add” at the bottom, I get a green box that says the action was completed, yet the node is not added. It’s not listed in the GUI, and not listed in the database in the nfsGroupMembers table.

I’ve checked the apache error log, I am not seeing any errors about this.

However, after manually adding the node into the nfsGroupMembers table, it appears in the GUI. After adding it to the database manually, FOG is replicating everything from the master to the node as it should, everything seems OK.

Wayne Workman

I can test this tomorrow.

Wayne Workman

Hey, @Neil messaged me recently about this. Our conversation is below. Thought I’d get this out in the open so more eyes can see it.

Hi Wayne, sorry for messaging you directly but was hoping to pick your brains. I work at a university in the UK where we’ve used fog since its first public release. We use fog to manage about 2000 computers which is a 1/3 of the university (thats complicated, dont ask). Since moving to 1.x branch we’ve seen serious performance issues. We’ve done a lot of work to fix these performance issues but are now seeing other odd issues. We are now running 1 x master node, 2 x storage nodes, with each connected to a 3 node galera cluster. We are running nginx and php7.2-fpm on the master node, haven’t gotten round to doing anything with the storage nodes with regards to that. Everything is running smoothly from a performance point of view. Galera is being hammered we are seeing roughly 700 - 1,400 queries a second from fog. The issue we are currently seeing is when you deploy snapins via groups. One of our IT Suites have 71 machines in, if we push something out to it, only a 3rd of them get the snapin, this is consistant no matter how many machines are in the group. An entry appears in the all task list for each, but only 1/3 appear in the active snapin task list. I thought this might be something to do with galera so took one of the nodes out to find that the number of machines that get the snapin changes to 50%. Can’t be a co-insidence? You see to be the only person on the fog forums thats using galera so wondered if you’ve seen anything like this?

Again sorry to bother you! Neil

Wayne Workman

Neil,

I’m sure you’ve read this on the forums already, but I suggest you significantly increase your fog client chekin period, maybe to once per 5 minutes, maybe larger.

About the Snapin issues you are seeing with Galera, this is really interesting.

I think because fog is making so frequent queries to the database, changes may be in one of your galera nodes but not replicated to the others yet.

if you increase the checkin rate, it’s possible the issue gets resolved.

Are you sure you have Galera replicating?

And I assume your Galera cluster is load balanced?

And is FOG set to use the load balancer?

Wayne Workman

@agray This question is pretty open-ended. Let’s start with questions about your capture process.
What version of FOG are you using?
Did you capture your golden image from a VM?
Did you SysPrep the VM?
Does the image have drivers available for the destination hardware?
Do you know if the image you captured was legacy or UEFI?

Wayne Workman

No idea, haven’t used Windows in a year.

Wayne Workman

@zfeng said in How to do remote management:

How can that be possible if they are not under the same network?

Fog of course needs a network path to the target.
Beyond that, you can make things more efficient with storage nodes, which are sort of like remote fog slave servers under the control of the master server - they hold images so that you don’t have to image across a WAN. Also there is the FOG Client which allows for OS level management of all the workstations you’re managing.

Look at these wiki articles for some insight:

Wayne Workman

@JGwinner Please create a new thread with all the details of your problem.

Wayne Workman

Posting this as just informational. Seems to be some sort of problem with installing on Arch.

It seems to be the caused by a change in Arch Linux, not FOG, as installation of three different FOG branches are failing all on the same day today. I’ll keep an eye on it, and see if the same thing happens again tomorrow before I invest time into looking at it.

Wayne Workman

@developers @moderators I was able to get the daily installation tests to test upgrading from FOG 1.5.5. Mostly this is going good, but 1.5.5 didn’t install correctly on Fedora 30 or RHEL7. Those two are totally jacked, but everything else seems to be working right.

I need to write some new scripts to make the setup more easy though.

Wayne Workman

@Sebastian-Roth said in FOG install overwrites /etc/exports with no warning:

Upgrade install with a clean /etc/exports file: either we use checksum or regex to make sure it is not modified and move the file to /etc/exports.d/fog.exports (and maybe create an empty /etc/exports)

Just check if it exists.

if [[ ! -f "/etc/exports.d/fog.exports" ]]; then 
    echo "do stuff"
fi

I’d suggest asking the user to confirm the actions to be taken, with a default answer of “y”.
Maybe something like “it’s detected that fog configuration exists in /etc/exports. Would you like the installer to move this to the new location for you?”

Just kicking around ideas…

Wayne Workman

@george1421 said in FOG install overwrites /etc/exports with no warning:

Questions: what happens if we have 2 exports.d file that contains the same fsid? Will that break something?

In what scenarios do you see having two?

Wayne Workman

@EduardoTSeoane It sounds like you’re using groups to deploy several snapins at once? If that’s the case, as a work-around, I might suggest deploying 1 snapin at a time with groups. That way they happen in the order needed. Not optimal, I know.

Wayne Workman

@EduardoTSeoane I think snapins have always executed in alpha-numeric order.

Wayne Workman

@george1421 said in Change the boot order automatically:

But we do it this way to make sure we don’t reimage the CFOs computer by accident (again) if everything was automatic.

That must have been a bad day.

Wayne Workman

@Sebastian-Roth said in TFTP won't start at the installation:

@Onirix I probably need to test with Debian 9.9 myself to figure this out. Not sure when I will get to this.

I see you’ve already tested it, but the daily install tests - in the case of Debian 9 - always are testing the very latest version of Debian 9 automatically every day. Arch is always the latest version. Centos 7 is always the latest centos7. Fedora 30 is always the latest 30. Ubuntu 18.04 is always the latest 18.04.xx.