Posts made by george1421

@jjcjr With your concerns then the remote site will need to have a stand alone storage node, just for the reason you cited. If the master node is unreachable then imaging isn’t possible.

What you are asking for is not currently available in fog (what I’ve been calling a multi master node setup. I’ve personally had a feature request in for this for over 2 years). The developers have just added a restful api interface that was on the roadmap to provide what you are asking. But its not there just yet.

With your current setup, you only need to export from the master node and import into the remote node when you have a new image definition. If you update an existing image definition, the new files will be replicated to the remote fog server and nothing else is needed. This is how I run my multi-master fog setup.

@sgwk OK so you are on the FOG iPXE menu and your keyboard doesn’t work. You have the latest stable version of FOG. This means there is an incompatibility between the iPXE kernel and this keyboard hardware.

1. Are these target computers in UEFI or BIOS (legacy) mode?
2. Can you get the keyboard to work if you plug it into a USB-2 port vs a USB-3 port? Or to say it another way, does the keyboards work when plugged into the black usb ports vs the blue usb ports?

I’m not sure I understand here.

I think what you are saying is that they keyboard on these computers are not functioning in the FOG iPXE menu (where you can select to register)??

If that is the case, what target computers are these? What manufacturer and model?

@jjcjr Yes you can. The fog storage node is a full FOG server, just without the database. It uses a sql server back to the master fog server to use its database. Replication works as it should and so does pxe booting. BUT, i have to tell you the clients must be able to connect to the master node during booting to pick up instructions on how to find “its” storage node.

The connection to the master node only downloads a small … text file (really a iPXE menu file) from the master node then pulls everything from the local storage node.

Is there a reason for not using a fog storage node at the remote location?

@dew12 If you are running 2.76, then use my ltsp.conf file from the tutorial. Your config is missing some bits at the end (and in the middle too).

What version of dnsmasq are you using?

For dynamic support of bios/uefi you must use dnsmasq version 2.76 or later. I have instructions and a sample ltsp.conf file in the following post that is working: https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support

Just follow my posts since there was some discussion between my instructions.

@aksl said in Imposible to boot from hard drive:

Problem between UEFI and Legacy?

The problem is that there is something new/unique that Microsoft has done with 1703 -OR- the iPXE developers changed something so that the iPXE kernel can’t find the hard drive when sanboot exit mode is picked.

This is now the fourth post in the last several weeks where 1703 is not behaving well on exit from iPXE. There must be some change with Win10 1703 that iPXE is not aware of.

https://forums.fogproject.org/topic/10652/windows-10-1703-won-t-boot-on-sanboot

@msi said in Remove and stop FOG to act as a DHCP server:

@george1421 I am sorry that I am asking a lot. Can you tell me more about how to configure dnsmasq? I heard about before and failed to configure it in right way when I tried to use cobbler.

Wow, I apologize. I copied the link and never pasted in my post. Sebastian has the link in his post. That link contains the instructions on compiling dnsmasq 2.76 (minimum version required for dynamic bios/uefi support). It also contains a sample config file that does work.

@msi So lets work with option 2. We can go back to option 1 if we run into a road block with option 2.

For option 2:

1. Remove the next server and boot file entries from your cisco router. Also remove dhcp options 66 and 67 from your dhcp server. We ar e going to use dnsmasq to provide these dynamic boot file names.
2. Follow my posts here to download and compile dnsmasq version 2.76 (actually 2.77 has been released and if you want to attempt that the instructions should be the same).
3. Install dnsmasq on your fog server using the ltsp.conf file listed in that post. Don’t forget to update the fog server IP every place in that file (there are quite a few).
4. Start the dnsmasq service and pxe boot a target computer on the same vlan as your fog server. If your pxe client computers are going to be pxe booting on a different subnet than your fog server you will need to add your fog server listed last in your dhcp-helper / dhcp-relay service on your vlan router.

@msi Well we have two directions to move in here.

1. Debug what is wrong with your cisco setup.
2. Because you asked can we support both, change plans a bit to support both.

Option 2 would give you the most flexibility.

@jarl2-0 well your pastbin file shows that the firewall rules are loaded into iptables.

You should see this if the firewall has been disabled.

# iptables -L -n -v

Chain INPUT (policy ACCEPT 2968 packets, 899K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 3137 packets, 471K bytes)
 pkts bytes target     prot opt in     out     source               destination         

@jarl2-0 OK from the fog server linux console key in the following command.

curl "http://127.0.0.1/fog/management/index.php"
This is going to return a screen full of html code. This is a good thing. If we get a timeout then that will tell us something else.

Then repeat the same process with the fog server’s IP address.
curl "http://<fog_server_ip>/fog/management/index.php"

@jarl2-0 This is really strange.

Apache is running, its listening on port 80 and yet you are getting a connection timeout. Something is not adding up. For the management gui access are you using the ip address of the fog server or a conical name?

I’m going to confirm a curl call to see if we can call the management page from the linux server console. One sec while I confirm it does what I think I want it to.

@jarl2-0 Ah, OK then lets try this.

ps aux|grep apache to confirm that the apache process is running
You should see something like this

www-data 21806  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 21807  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 21808  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 21809  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start
www-data 21810  0.0  0.7 106732  7236 ?        S    06:25   0:00 /usr/sbin/apache2 -k start

netstat -an | grep 80 to confirm that the apache server is listening
You should see something like this:

tcp       0      0 :::80                   :::*                    LISTEN   

systemctl status firewalld to see if the firewall is on by chance.

@jarl2-0 Well that’s pretty unimpressive. It just tells me the http server was shutting down. If you start the http server up again and try to access the management console does it append anything to the error log? It should be throwing some errors if you try to access the management page but only get a white (blank) page.

I believe this was fixed in one of the 1.5.0 RC releases.

I’m going to move this to bug reports forum so the developers can take a look to ensure it was resolved once they return from holiday.

Thank you for reporting this.

Lets see what the apache error log states (the above post doesn’t really tell me anything). The error log should be in /var/logs/apache2/error.log. Tail that file. If it gives you the indication of a database communication error AND it was working then magically stopped THEN this post is probably relevant: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

@sgwk So if you remove the nic from the network boot order does it boot correctly?

Since this is a gen 1 VM, what host OS are you using for this VM? Is that up to date? I assume that since it is a gen1 then bios mode is the only option? (sorry I’m a vmware guy).