@george1421 @martinetwork I believe you can also use the following as a guide: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

I have done this a dozen times in the last few weeks with no issues.

Essentially let http and other services through firewall (no need to disable it) and you can use the command:

setenforce 0

to temporarily disable SELinux. Its up to you at that point if you follow the guide and permanently set it to permissive or if you take the time to set the SELinux contexts required for it to all work.

Hope this helps

@tom-elliott Fixed. I’ll take back everything I thought bad of you man. Thanks 🙂

@daniel-dillard said in Group membership when adding hosts via CSV:

I just want to know if there is a way to do it by adding a column to the CSV for host import.

Yes, you can. For an example CSV, do: Web GUI -> Host Management -> Export Hosts. This will give you the format. In the same area, there is an Import Hosts link that will allow you to upload a CSV.

See also: https://wiki.fogproject.org/wiki/index.php?title=Replication

Any idea what the output shows? From what I can read, the Fog Server is seeing the request come in but I don’t have the experience enough to garner further support knowledge.

Thanx for the advice on the DNSMASQ. I’ll talk to my seniors about installing/configuring that hopefully this week.

@pijltje Hmm I don’t see that directory I am using Ubuntu (I know I know, first time fog when I have time I WILL switch been a pain honestly)

@BardWood Sorry, no change there. I don’t see any vendor class identification in the PCAP. I have searched the web up and down to see if others report similar issues but couldn’t find anything yet.

I really wonder if there is some kind of intermediate switch/router/firewall modifying the DHCP packets?!? Have you had FOG server and Mac client on the same switch yet?

I’m not sure if I should delete the information in the /images/dev/ or if I just need to change a setting somewhere.

@vince-villarreal what feature are you referring to? An image will deploy to a machine based on the storage nodes within a storage group. Assuming both storage nodes are in the same group, it uses a rudimentary load based system to determine which node to deploy the image from.

What version of fog are you using?

Everything seems to work fine until I go to use it, the web interface works no issue but the moment I go to image a pc it fails to pxe then I can’t get back on the web ui giving me err_connection_timed_out.

Ok, config for SELinux has been changed, did a reboot for testing, looking good so far.

Even if I still do not know, how the SELinux got enabled at all, it looks like the issue is solved.

Thank you very much to all of you guys who helped with the issue.

Cheers Nuit

@joe-schmitt Yes. Kaspersky starts when the snap-in finishes.

Sometimes the FOG Client will crash on other snap-ins, but setting the service to automatically restart fixes that issue. This is the only snap-in that does not always reboot after it is completed. I’ll play around with it, maybe adding a wait-time after Kaspersky is installed to let it do whatever it needs to will help.

Cool, I waited about an hour now and data has been transferring to the images folder.

Looks like it is working! I have another question, but will post it as a new topic

How many users do you have on the FOG system?

It’s possible PHP ran out of memory trying to process them all. (you can change the php memory value in the FOG Settings)

edit: Might be a similar situation to https://forums.fogproject.org/topic/11713/503-service-unavailable-error/61

I just found this thread: https://forums.fogproject.org/topic/11713/503-service-unavailable-error/40 I’m going to try some of that stuff and see what happens.

Access was trying to be achieved via hostname. The hostname was routing to a different subnet. Just edited the apache config to look at the server name of the host initially trying to be used, updated the fogsettings file to reflect so future updates don’t break this functionality.

@joshuaian What exactly was the date that it was passing. It wouldn’t matter if it was: 2018-05-13 but if the file was 2018/05/03 then it may have issues as the / represent directory separators in linux.

@cstfoguser does the image have an assigned storage group? Can you make sure it does? Go to the image-> edit -> storage groups. Ensure it’s got an assigned group, click the update/add as needed to ensure it does.

@george1421

Also, something to note, I had another machine I was testing this on and if you do not do the disk cleanup and remove the old windows installations the new inits work just fine. It appears the cleanup messes something up for some reason.

I’ve got a new issue just only with the AD join function… Here in the fog log :

03/05/2018 20:49 HostnameChanger Logon failure: unknown username or bad password, code = 1326

I havn’t change anything about the acount for joining the domain… Is there a new way to configure that ?

EDIT: a server update has desactivated the fog acount (for modifying the password)… Problem solved