@JJ-Fullmer Thanks for the instructions; that worked!
Some notes on the situation for me:
Root password was set BUT only for ‘localhost’, but the host localhost did not have any type set (whereas the others had mysql_native_password)
I think that this may have also been the case for me. I certainly remember having set a root password but after fixing everything my only conclusion was that I must have not. But I did also notice that my mysql.user table had 3 different root users for localhost, 127.0.0.1, and 1 other I can’t remember right now. Mine were all set to the mysql_native_password plugin as well. It looks like a solution is in the works here already, but just wanted to add that note that the root problem might be the authentication problem.
@Tom-Elliott Thank you for all the assistance. I actually ended up testing dev versions 184.108.40.206, and 1.5.8 and I can confirm both indeed fix the issue. Both versions now start all the services correctly after several reboots. Thank you for all your assistance Tom and everyone!
@dforce New inits are build and you can simply re-run the installer to pull the new files. Tom also pushed some changes to dev-branch so you might want to do a git pull as well though it’s not needed. If you do so, don’t wonder about a decreased version number. Seems like we had that advanced a little too high at some point and Tom pulled it back now.
As @Sebastian-Roth has suggested, by default groups in fog are nothing more than a means to apply settings to multiple hosts at once.
So taking your example, if you apply image a in group a and refresh the page, you will see group a maintains image a as it’s set.
If you then go to group b and it contains all the same hosts as in group a, then apply group b image to image b, it will have set image b to all hosts in group a. So if you go back to group a, it will show image b as being set.
The way these fields are displayed, if all hosts in the group have the same image defined, it will display that image as being selected.
Groups in fog were not designed to be persistent.this is why you can associate a host to multiple groups at the same time.
Sorry, I wiped the PC. I have a hard deadline to meet to get the old FOG server replaced.
The good news is that a fresh install, starting from zero on bare metal with a Debian 10.2 net install* and a git clone of FOG worked with no FOG related problems. I have successfully collected an image from a local PC in the IT Admin Lab and deployed it across the routed network to two ‘volunteer’ PCs.
So I apologize again for wasting your time.
All I can suggest is that the installer checks if it is being run as a re-installation and posts a warning, and maybe points to some documentation on how to properly do a reinstall. I recognize I’ve incurred some debt here, so I’ll try and post some helpful information for other people.
I very much appreciate the FOG project. Thank you for providing such a useful tool.
*Debian 10.2 net install grabs a DHCP address, and persuading the OS later to use a static IP was a little more convoluted than I expected. Similarly, the default install does not include sudo, which is easy enough to remedy.