Best posts made by Wayne Workman

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

@TBuzaTechnician said in Auto-Installing FOG with HTTPS enabled issues:

but I have a habit of using sudo anyway.

This has in-fact caused many people problems. I don’t know why, don’t really care why, but using sudo with the installer doesn’t work. As Sebastion said, properly log in as root with sudo -i and then execute the installer.

@cammykool It can do remote execution, printer management, power management, login recording, and other things. I’ve used it to run scripts, deploy software, and other things. Check out these wiki articles below, they might help you understand the capabilities.

• https://wiki.fogproject.org/wiki/index.php?title=FOG_Client
• https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
• https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks

There’s also a ton of stuff on the forums about printer management. Here is one with some detail: https://forums.fogproject.org/topic/8051/printer-deployment?page=1 though there’s probably hundreds of topics about printers.

I know @george1421 loves CentOS, but Debian is also very stable for fog too

You should certainly be able to search in the GUI by MAC address, however sometimes even then the host won’t display due to other issues. Using SQL, you can always find items.

Please have a read through the topic Sebastion mentioned. You might also look at this Wiki article: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

I can confirm Ubuntu 18.04 installs the latest version of fog just fine.

I run the daily fog installation tests, which test if the various branches of the fogproject github repo can install on the latest patched versions of various operating systems. I’ve been running these tests for maybe four years now, every day. The daily results are in my signature. While Ubuntu has been problematic sometimes, at the moment it installs fine.

My recommendation to you is to fully update your Ubuntu system before installing fog. This is what my daily installation tests do before installing fog:
apt-get update;apt-get -y dist-upgrade;apt-get -y autoclean;apt-get -y autoremove and then reboot before proceeding.

Further suggestions: Debian and CentOS are by-far the most stable Linux distributions that you can run FOG on. A couple years ago before a major re-write of the daily installation tests, I tracked success streaks of the various OSs and various fogproject branches. CentOS and Debian were neck-and-neck for 1st for the majority of the time on the master branch of the fogproject repo. If you want better luck overall with stability, it would be my modest recommendation to move to one of these distributions.

Future readers can also try this: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

@JJ-Fullmer A lot of the new client’s printer documentation is in the forums. The wiki does need updated concerning printers.

Try to restart nfs and rpc
sudo service nfs-kernel-server restart
sudo service rpcbind restart

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

@jyost Search the forums for snapin order. You’ll find several threads. Here’s one that probably will help:
https://forums.fogproject.org/topic/12784/snapin-order

@tesparza This should happen automatically. If it’s not, you have some sort of configuration problem. There’s a replication log you can look at in the web UI. Check that for errors.

Also, there’s this article on the location plugin. While this is meant to cover location plugin functionality, it also explains default functionality pretty well. https://wiki.fogproject.org/wiki/index.php?title=Location_Plugin

@jconway1006 Need more information. Fog version, screenshot of the issue. Number of fog clients, FOG Client checkin time, FOG Server hardware specs. Where is the fog server in relation to the node being imaged? What’s the network speed between the fog server and the node being imaged?

Every time I turn around, a new linux distro is released. I’ll work on getting the daily install tests updated to use some newer OSs.

@fog_newb said in Ugh so updating from 21.04 to 21.10 breaks the database:

have other services and things running on the box too

What sort of stuff? Just curious. If at all possible, I would recommend against server-sharing. Not only with FOG, but just as a general I.T. guidelines.

This is completely possible. For spreading things out, any of the following is possible.

Multiple FOG Masters to separate FOG Client traffic / node traffic from your traffic / engineer traffic.

• This solves the nervous user problem (clicking buttons in the UI over and over rapidly).
• This solves load issues with 15 engineers / technicians just sitting on the dashboard with the graphs chewing up server CPU.
• 1 FOG Master for people to interact with.
• 1 FOG Master for everything else (node check-ins, FOG Client check-ins)
• Could split this out even further if you wanted. Could setup load balancing with F5 or HAProxy, for example. Or, could do simple DNS load balancing by creating many records of the same DNS name, but each pointing to different FOG Server IP Addresses.

One or more seperate storage nodes for imaging load

• Build separate Storage Nodes, as many as you think you need. Set one as the storage master of your storage group. Only storage group masters can multicast.
• An image can be assigned to multiple storage groups. So you could have two storage nodes, each a master of a separate storage group. One will be the image master (the original), and that master will replicate to the other master.
• Replication documentation here.
• Multi-casting documentation here.
• Multi-casting troubleshooting documentation here.

If your geographically dispersed, use the location plugin.

• Documentation can be found here. This covers the topic with an older FOG version but is still accurate.

Put Database on dedicated VM.

• Setup MariaDB on another VM. Set password, remote access. Documentation here.
• Dump your database from your fog server, load to new DB.
• For all your your fog masters and storage nodes: Point them to the new database via this file: /opt/fog/.fogsettings. Documentation here.
• Re-run fog installers on all fog masters and all storage nodes.

Increase Client Checkin Time

• This will resolve a lot of the client load.
• Documentation here.

@trev-lchs MemCheck is not a snapin, it’s a built-in fog feature among others. Snapins are things you create that are executed by the FOG Client.

My guess is these were removed from the boot menu of the server you’ve got now. You might poke around in the IPXE boot menu area and see if you can add them back.

@lorentedford Not sure how you broke it, but I’d recommend wiping what you have and starting over. Here’s a recent article /w video I made covering debian. These steps will work exactly the same on Debian 9, so use Debian 9.

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

@icemannz I’m guessing the disk uses LVM. Fog doesn’t support LVM. If you create the partitions without LVM, it should work.

@noob It’s not a problem, it’s a default. Whether to change the partitioning or reinstall is up to you. You’d learn a lot going the longer road.

@george1421 I don’t think you’ve yet to explain what you’re trying to do really… If you did that, we could probably give you several configuration options.

The VPN over WAN issues is easily solved by the location plugin, for instance… You’re just poking here and there trying to make things work but we don’t know what you’re trying to do really.