@Tom-Elliott Thank you for all the assistance. I actually ended up testing dev versions 1.5.7.102, 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!

Found and fixed, details see here: https://forums.fogproject.org/topic/14115/boot-php-permission-denied

@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.

@falko Bump…

@EduardoTSeoane Is this still an issue?

@EduardoTSeoane I am marking this as solved as I would think the quick fix should help in your environment and we haven’t heard anything negative back yet.

The password is not encrypted anymore. This is not a bug, it’s expected behavior.

With that said, we did add some to the code to make sure that the password isn’t simply displayed in the plain text.

You’d need to install the dev-branch version though.

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.

@lebrun78 Disable Ad-Block addin and you will see the advanced menu field!

@george1421

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.

Junior Catherd

*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.

Seems, that on every 20th November the google search key doesn’t work.

What about using another search engine like quant?

https://www.qwant.com/?q=site:forums.fogproject.org&t=web

@Daniel-Miller Thanks for reporting! Obviously hasn’t been noticed in a while. I just pushed a fix to working-1.6.

Moving this to section bug reports and marking as solved.

Thanks.
1.5.7.745 update works fine.

@Tom-Elliott I am willing in a heartbeat. The problem right now may be my “history” of the old trunk builds causing some headaches in the past. I have some convincing to do for my boss, but having solid things that are fixed/improved helps the case. I am also probably going to need to take a medical leave soon and want to have FOG be stable while I’m gone. I will look at the features 1.6 and see if I can’t earn that tester badge again 😄

@isaiah658 Fixed in dev-branch on github - will be in the next release.

@Cheetah2003 I know it’s been a long time. Sorry this has gone lost! I only got to look into this and fixed it.

@markbam I started to implement that but need to push this further down the list. We need to focus on bugs of the core FOG code before that.

Note to myself: I have saved a diff of the current work in my workspace.

@Fernando-Gietz Just found this. Hope you got to test this at all. I am going to mark this fixed now.

@cromag Thanks for bringing this topic up again. Indeed there was an issue in the scripts. I just pushed a fix to dev-branch. Should be fine in the next release.

Though I still have no idea where the macvtap0@ thing came from reported in the first place.

Nevermind.
It’s working again.