My boss was getting very worried about the state of some of the sites that were going to be imaged and wanted to setup conventional FOG normal installs at the sites in the meantime until the centralized AWS EC2 FOG server gets up and running.
However, I have (for the most part, with an issue related to the database in the “Linux Problems” forum) gotten the AWS EC2 instance working.
So this thread can be closed for now.
I am trying to setup a FOG server in an AWS EC2 instance. I got to the point in the install where it was “ensuring that node username and passwords match”, and it just hung there.
I then decided to restart the installer, and ever since then I get to “Backing up database” which fails after a long period of time.
I followed this: https://forums.fogproject.org/topic/10126/ensuring-node-username-and-passwords-match for my initial problem, but that hasn’t helped.
I have both commented out the two lines referred here: https://forums.fogproject.org/topic/8358/problem-updating-fog-backing-up-database-failed/26 and tried making the snmysqlhost blank, but that has not worked.
Another forum thread (https://forums.fogproject.org/topic/6097/backing-up-database-failed) said that the “backing up database” issue may be due to the existence of a proxy server. I use an elastic IP on the EC2 instance, which may be a proxy server, but I’m not sure what syntax to use in the configurations mentioned in the thread.
Other than than FOG works perfectly fine. I successfully imaged a machine at my workplace to a storage node at the work place using tasks issued by the EC2 server. It’s just a matter of getting the database working properly. I was even able to register the host machine via FOG’s Full Host Registration, so it seems as though that part of the database updating is done successfully.
UPDATE: Ran installer for 1.4.4, still did not work.
UPDATE: Apache error log appears to throw this error every time I run the installer: 
I have no idea what the “client” IP in that error is referring to, nor do I recognize the IP address.
UPDATE: Tried ALTER USER ‘root’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘’; but that didn’t work. Replacing ‘localhost’ with ‘127.0.0.1’ throws “Operation ALTER USER failed for ‘root’@‘127.0.0.1’”
UPDATE: Configured /etc/wgetrc with:
https_proxy = https://172.31.45.41
http_proxy = https://172.31.45.41
ftp_proxy = https://172.31.45.41
use_proxy = on
no_proxy = "localhost"
Got to point in install where I had to go to FOG_SERVER_IP/fog/management to update database schema. The prompt didn’t show up to update the schema, so I continued with the install. The install finished, however it still fails to update the database during imaging, throwing the error: Error returned: Type: 8, File: /var/www/fog/lib/fog/fogcontroller.class.php, Line: 1046, Message: Undefined offset: 3, Host 192.168.10.100, Username: fogstorage
@Quazz said in Adding FOG database to another FOG database.:
But as far as I understand the new one will only happen when this transition, occurs, yes? If so, overwriting the database is no problem.
The issue comes with the fact that there it may end up being the case that there are multiple “old” servers’ databases that are going to need to be put onto the “new” server.
Hello,
My company is planning on using FOG In such a way that we will start with one normal install backing up some computers, but will eventually switch to one normal install controlling multiple storage nodes that the backup said computers. This will involve effectively wiping the original normal install, and putting a FOG storage install on it. I see that I can copy the database with mysqldump --allow-keywords -x -v fog > fogbackup.sql and backup the images with cp images/* <backup location>, however I have questions about the process of restoring them.
While I understand that I can import the database to the new normal install of fog by going to “FOG Configuration” -> “Configuration Save” -> “Import”, will this overwrite the existing database, or will it add my imported database to the existing database?
If it does overwrite the existing database, how do I add my backup to the currently existing database?
@george1421 said in Host isn't booting into FOG menu:
In your setup clients at the 192.168.10.x subnet must be able to reach your control server during pxe booting. The control server will redirect the pxe booting clients to the storage node. Now understand the clients at 192.168.10.x can pxe boot (download undionly.kpxe) from your storage node, it will download default.ipxe from the storage node (which needs to point to your control server to pick up the boot.php file).
So, if I understand you correctly, I should go into default.ipxe and change the IP address to 10.8.0.1? I know you said that VPN isn’t the issue, but I don’t understand how the host is able to know where to go for the 10.8.0.1 IP, if it isn’t part of the VPN tunnel.
@george1421 said in Host isn't booting into FOG menu:
@Benjamin_D OK I think I need to get a clear picture of what is going on here, including the vpn tunnel.
Okay, let’s see if I can get us all on the same page here.
You have a remote site where a FOG Master node is installed. In addition to this device being a fog master node its also running isc-dhcp server.
Yes. It is a FOG storage installation that is itself the master node, and yes it is running ISC-DHCP-Server.
The fog master server’s IP address is 192.168.10.100 and its issuing IP address < .100.
Yes that is the IP address, however it’s range is only from .2 through .9 (it’s a test network with only one client for it to lease IPs to)
When you pxe boot target computers at that site it should boot from the local fog server.
Is that not happening? Now we are focusing on the master node at the remote site, pxe booting clients at the remote site.
Given that it does successfully talk to the master node at the remote site for the tftp portion, it seems like it’s getting part way through the boot at least.
(a quick doodle of your setup with ip addresses, might be in order here)
Okay, this has a bit more information that we probably need to solve it, but just to give you a full picture of the test network I have setup (the end goal is the VPN will be over the Internet, in-case you are wondering why it’s setup like it is):
@george1421 said in Host isn't booting into FOG menu:
@Benjamin_D While you have a unique setup and I don’t recommend doing this, in the default.ipxe that should point to the local fog server.
The other thing that IS supported is to install the location plugin. Create a location, assign your storage nodes to that location, and finally when you register a target computer ensure you assign it to that location. That way you can control which fog server the target will connect to.
I’ve changed the IP address in default.ipxe to the storage node’s LAN IP, which leads me to this error:
.
As far as the location plugin is concerned, it’s been installed and I use it, but I don’t see how that exactly solves my issue here. As far as IP schemes are concerned, it’s no different then just telling FOG what storage group to use like you would without the plugin, right?
@george1421 Okay I’ve reformatted my dhcpd.conf to match example 1, and now it gets to where it is trying to grab boot.php.
However, it fails to do that, and I believe that is due to the fact that the host is using the VPN IP of the storage node to grab boot.php, as opposed to the LAN IP. Is there a way to have the clients use the LAN IP address for grabbing boot.php even though I have to add the storage nodes via the VPN IP address?
@george1421 said in Host isn't booting into FOG menu:
Ok, so both dhcp (udp port 67 and I assume 68) and the tftp (udp port 69) are running. So the target should be getting something.
From your note, you feed that both dhcp options 66 and 67 are set correctly, yet no file is received by the client.
Correct.
quick check: Can you tftp using a windows computer, and transfer a file like undionly.kpxe from the master FOG server?
While I can ping the server’s LAN IP, the command: tftp 192.168.10.100 GET undionly.kpxe C:/ returns a “Connect request failed”
If that fails then we need to see what’s going down the wire. We can do that with your fog server as long as the pxe booting target computer and the fog server are on the same subnet. ref: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
If you know wireshark and can read [0_1497894431090_Capture.pcapng](Uploading 100%) the dhcp boot process you may review it, or post the pcap file here and we can take a look. What will be interesting to see is if the fog server IS responding to the dhcp request and what file name is the target computer being told to transfer.
Here’s a link to the capture. I stopped it once it got to the login screen: https://drive.google.com/open?id=0B5vOQkrBMlbtNUtrM0VQdzlBZjA
Edit: just as a thought, you only have one dhcp server at the remote location… and that’s the fog server right?
Correct. If it helps, here is the relevant part of my dhcpd.conf file:
subnet 192.168.10.0 netmask 255.255.255.0
{
range 192.168.10.2 192.168.10.9;
default-lease-time 600;
max-lease-time 7200;
# option 66
option tftp-server-name "192.168.10.100";
# option 67
option bootfile-name "undionly.kpxe";
option routers 192.168.10.1;
}
192.168.10.100 is the storage node, the client shows that it has an appropriate IP when I run “ifconfig”, and 192.168.10.1 is the router.
@george1421 I have 2 fog servers setup. One is setup at HQ and its a FOG master node and one is setup at a remote location as a storage node. (the vpn bit my not be relevant just yet as long as routing works).
I think you understand correctly, here, but just to clear any confusing of your use of the term “master”, the server at “HQ” isn’t meant to store anything, and the storage node on the other end of the VPN is the master storage node that will be the machine holding the host’s image.
The remote site’s FOG storage node is configured as the dhcp server at the remote site. The isc-dhcp server is configured with dhcp option 66 {next-server} to the LAN interface of the FOG storage node at the remote location. DHCP option 77 {boot-file} is configured as undionly.kpxe.
Correct (although I believe you made a typo, since I believe it is option “67” not “77”).
When I pxe boot the target computer it appears to just hang waiting for a dhcp address from the FOG storage node.
It doesn’t hang, it says that it can’t find the tftp file and then goes to the next boot option (the HDD with the OS).
- Is the isc-dhcp server running? netstat -an|grep 67
- Is the tftp server running? netstat -an|grep 69
- Did you disable the firewall before you installed the fog storage node at the remote site?
Yes, just to get VPN to work I had to disable the firewall
I am trying to get FOG to work over a VPN. I have a normal FOG installation running as my VPN server (OpenVPN, also FOG 1.4.3 on Mint Linux (Serena)) on one network, which is (or at least, should be) controlling a storage FOG installation on the other end of the VPN. The storage node is a DHCP server for my test client.
I’m not really sure why it won’t go into the FOG menu on PXE boot.
It’s not finding the tftp file. I’m guessing I have the wrong IP. I thought the IP should be of the storage node though?
@Junkhacker said in Use one FOG server to control multiple other servers:
@Benjamin_D look into the location plugin. i think you should be able to do what you want to do, but i don’t think anyone has done it before.
That definitely looks like it will help, however it appears I’ll still need to set up the route over WAN so that the control server can talk to the storage nodes. What ports would I need to forward to allow communication between the control server and the local master storage nodes?
Hello,
I’ve been informed that it is possible to have FOG capture an image from a host while somebody is logged into the host, but I cannot seem to find the documentation outlining it. I saw some things referring to the FOG client and FOG Tray, but neither appear to have that functionality.
Can confirm as well that worked. Thank you!
@Tom-Elliott I ran those commands and tried to re-register, but no change in the result.
Hello,
I am running Ubuntu 16.04.2 LTS with FOG 1.4.1, and I am having what appears to be the exact same issue.
Here is the results of my ls -lhart commands:
I should note that while it appears to be the case that there are two installs of the FOG, I just installed Ubuntu today, and the only other program that I installed on this machine is isc-dhcp-server to specifically for FOG.
Hello,
I’ve been tasked with making a FOG environment whereby two FOG servers at two different sites backup/restore their respective site’s computers, and both servers are controlled by another FOG server in an Amazon EC2 instance. The EC2 FOG server is not meant to hold any images, but just be used to ease management of the other two servers at two different sites.
This appears to rule out master nodes, because images go to the master first, and are then copied down to the other nodes. I see that I can create multiple storage nodes and groups, and set images to those groups, which is a start, but if I tell the EC2 FOG server to make a new image and store it in a storage node on a site, will the EC2 FOG server do the imaging, or will it tell the server at the storage node to do the imaging?
If it will use the FOG server at the storage node to do the imaging, then that’s perfect, otherwise, how would I set it up so I can have the EC2 FOG server tell a server at a site to setup/deploy an image?
