Posts made by Wayne Workman

@blindcat420 said in Cant pxe boot to fog.:

i disabled firewalld i assume that is different than selinux?

You need to set SELinux either to permissive or disabled, instructions for that are in the CentOS 7 tutorial.

@blindcat420 Just a quick question. Did you disable selinux? Check with sestatus or with getenforce. This is in the CentOS 7 instructions.

@george1421 The makeFogMobile script does update dnsmasq, but the updateIP script does not.

I would suggest a packet capture on the fog server to see whats going on.
@blindcat420 do you know if you’re VM is setup to network boot via Legacy or UEFI? Do you know what version of dnsmasq you’re using?

I think changing the web UI’s default user is a good idea.

Below are the spots that come to mind, but there are surely lots of other spots. I searched the wiki for ‘fog’ and ‘user’, the results weren’t helpful.

https://wiki.fogproject.org/wiki/index.php?title=.fogsettings#Username
https://wiki.fogproject.org/wiki/index.php?title=Password_Central
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords

@phil-dosi Are you familiar with Galera? It’s clustering for MariaDB. You could put the Fog database into a 3-node Galera cluster and do load balancing with HAProxy. Also you could setup a 3-node FOG master behind an HAProxy load balancer with sticky turned on due to the PHP sessions needing to stay with their originating web server… This should take care of 10,000+ nodes. For the locations, you would just use storage nodes plus the location plugin. Perhaps even two storage nodes per site if you have only 5 sites with 10,000 hosts.

@p4cm4n In the case of storage nodes, the fog server that hosts the database has to be updated with the remote node’s new IP address. So to answer your question, No. Though since the database credentials are present on the storage node, some alterations to the scripts could make this possible.

You can disable a linux user’s ability to use a shell. Assuming the user account is called fog the command is:
usermod -s /sbin/nologin fog
or
usermod -s /usr/sbin/nologin fog

Something more elaborate that I found on the net would look like this:

touch /bin/nologin
chmod 755 /bin/nologin
echo '#!/bin/bash' > /bin/nologin
echo 'echo The fog account should not be used for system management.' >> /bin/nologin
echo 'echo Please create another account for system management.' >> /bin/nologin
echo 'echo This session will end in 15 seconds' >> /bin/nologin
echo 'echo Goodbye' >> /bin/nologin
echo 'sleep 15' >> /bin/nologin
echo '/bin/nologin' >> /etc/shells
usermod -s /bin/nologin fog

Changing the default username to something besides fog shouldn’t affect existing fog systems, since the username setting inside of /opt/fog/.fogsettings would remain in existing systems, and the username for existing storage nodes wouldn’t be touched.

A downside is all the documentation / screenshots that would become incorrect for new installations. There is a lot of content ‘out there’ about fog.

@george1421 I wish the account were named svc.fog instead of just fog… it would solve a tremendous amount of problems.

For future readers, the updateIP tool also covers updating the config.class.php file.

@robertkwild In addition to the link posted by @igorpa2 and in addition to this wiki article refered to by @Sebastian-Roth, there is a tool called updateIP.

updateIP was created as a easy to use tool for updating your FOG server’s IP settings after you’ve updated the OS’s IP. I would highly recommend it.

@iekozz See these:
https://forums.fogproject.org/topic/10238/fog-1-4-2-unable-to-locate-image-store-bin-fog-download/8
https://forums.fogproject.org/topic/9187/unable-to-locate-image-store-bin-fog-download/7

@Keating178 It would probably be helpful if you could post a screenshot of the entire screen. In the photo you posted in your OP, most of the command is cut-off.

@Keating178 said in "Error trying to restore GPT partition Tables" HELP!!!:

Does anyone know what “Error 4” means

According to this page:
https://www.rodsbooks.com/gdisk/sgdisk.html

Exit code 4 for sgdisk is “An error prevented saving changes”
Not very descriptive…

@kickers56 Please try to set the domain password using Incognito mode in your browser, see if the issue persists. Browsers will auto-fill and auto-complete password fields as a feature, and this has on many occasions been the culprit in strange password issues with fog.

Have you seen this tool? https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

@bmick10 On the CLI, you must first become root:
sudo -i

Then, edit the fogsettings file with vim:
vim /opt/fog/.fogsettings

Set dodhcp to N, as you already know. Here’s the syntax:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings#dodhcp

Here’s a tutorial on vi, which also applies to vim:
https://wiki.fogproject.org/wiki/index.php?title=Vi
Make sure you save your changes.

Then re-run the fog installer.

Here’s just a handful of commands to do things with the dhcp service directly…
status: systemctl status dhcpd
stop: systemctl stop dhcpd
start: systemctl start dhcpd
disable: systemctl disable dhcpd
enable: systemctl enable dhcpd

@Tom-Elliott That’s what I instructed @JGallo to do, but when he does that, it unsets the storage group. Look at his last post.

@Tom-Elliott said in FOG doesn't detect the status of the clients:

FOG Uses port 445 to detect the status of the client machines. This is usually UDP, though I think opening UDP and TCP would help things out.

We use this port as it can give a more direct status than a simple ICMP request.

Hopefully this help.s

#wiki worthy

@moderators @testers @developers can anyone confirm that the location plugin should/does support a storage group serving a location? As opposed to an individual storage node serving a location.