I had changed the virtual network on my xp virtual computer which caused the freeze up error. When I change it back to the intel virtual nic the virtual xp connected to fog and I created and restored an image with no issues.
Thank you everyone. Hopefully this will help someone else in future. My distribution was Centos 6.5 and FOG 1.20.
Made some progress today. In my research on creating custom pxe boot file for Linux images I found another post talking about customizing ipxe boot files. Interestingly he mentioned adding two lines in the dnsmasq.conf file. In Centos 6.5 this file is in the /etc folder. When I examined the file the two lines where there, but remarked out.
# Include a another lot of configuration options.
conf-file=/etc/dnsmasq.d/ltsp.conf
conf-dir=/etc/dnsmasq.d
After I un-remarked and added the lines above restarted the service and my test system promptly displayed my ipx option option screen 30 second countdown: A network boot, B hard drive boot.
I selected network boot and I was shocked to see the standard fog screen come up. This may have fixed it?
Unfortunately when I tried to register the computer the process jammed with an error
/bzImage32… 21%
I am very close now though and with some more work I think this will work in Centos 6.5 not using fog as a dhcp server but as a proxy dhcp server with the fog pxe boot options.
I am happy. Hope this helps someone else this was painful to figure out. I now understand the .0 automatically being added. I still don’t understand the difference between the undionly.pxe file and the unkionly.kpxe file, but I am taking this as a win!!!
Thanks for your help guys.
I use Centos 6.5 and had a similar problem. This is what was wrong with my setup.
https://forums.fogproject.org/topic/5518/fog-ftp-login-fails-after-image-creation
I think this is what is going on. I am going to try it again tonight. I think I am very close. PXE is very cool. People are booting operating systems, and linux install images with it. Very cool. I did not know it was so powerful.
Thanks for your help guys. I am learning so much from this.
https://forums.fogproject.org/topic/4915/unidonly-0-question
Also changed this line to reflect the ip address of the server
dhcp-boot=undionly.kpxe,x.x.x.x
Sorry about the giant font.
ltsp.conf file contents.
# Don't function as a DNS server:
port=0
# Log lots of extra information about DHCP transactions.
log-dhcp
# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp
# Set the root directory for files available via FTP.
tftp-root=/tftpboot
# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,x.x.x.x
# rootpath option, for NFS
#dhcp-option=17,/images
# kill multicast
#dhcp-option=vendor:PXEClient,6,2b
# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override
# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 30
# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", undionly
# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
#pxe-service=X86PC, "Boot from local hard disk", 0
# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1
# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses. Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
Mod edited to use code box.
tftp looks to be good. I can transfer file from linux and windows 10 hosts from the server with no isues.
Result from permissions of /tftpboot.
$ ls -laht /tftpboot
total 2.6M
dr-xr-xr-x. 26 root root 4.0K Aug 11 12:57 …
drwxrwxr-x 2 fog root 4.0K Aug 11 11:48 .
lrwxrwxrwx 1 root root 23 Aug 11 11:48 undionly.0 -> /tftpboot/undionly.kpxe
-rw-rw-r-- 1 root root 294 Aug 10 15:54 default.ipxe
-rw-rw-r-- 1 fog root 145K Aug 10 15:54 vesamenu.c32
-rw-rw-r-- 1 fog root 100K Aug 10 15:54 undionly.pxe
-rw-rw-r-- 1 fog root 374K Aug 10 15:54 undionly.kpxe.INTEL
-rw-rw-r-- 1 fog root 100K Aug 10 15:54 undionly.kpxe
-rw-rw-r-- 1 fog root 100K Aug 10 15:54 undionly.kkpxe
-rw-rw-r-- 1 fog root 162K Aug 10 15:54 snponly.efi
-rw-rw-r-- 1 fog root 17K Aug 10 15:54 pxelinux.0.old
-rw-rw-r-- 1 fog root 25K Aug 10 15:54 memdisk
-rw-rw-r-- 1 fog root 380K Aug 10 15:54 ipxe.pxe
-rw-rw-r-- 1 fog root 379K Aug 10 15:54 ipxe.krn
-rw-rw-r-- 1 fog root 380K Aug 10 15:54 ipxe.kpxe
-rw-rw-r-- 1 fog root 380K Aug 10 15:54 ipxe.kkpxe
-rw-rw-r-- 1 fog root 840 Aug 10 15:54 boot.txt
dnsmasq is running, when I issue the restart command I get an dnsdomainname:Unknown host message, but the service does restart and shows as running.
Made the changes to the ltsp.conf file as you suggested and then restart the server.
dnsmasq.d.conf file is all remarked out nothing happening in that conf file.
Same error:
ipxe boot pulls a dhcp address then gets the error:
Nothing to boot: No such file or directory (http://ipxe.org/2d03e13b) No more network devices
Fatal: Could not read from the boot medium! System halted.
Sorry for the large font, not sure what happened when I pasted the text from gedit?
ltsp.conf file. I took it off the wiki page and put my ip address in on the bottom. I am using Centos 6.5, but most of the documentation on this I can find is for ubuntu.
ipxe boot pulls a dhcp address then gets the error:
Nothing to boot: No such file or directory (http://ipxe.org/2d03e13b) No more network devices
Fatal: Could not read from the boot medium! System halted.
Almost looks like it is not reading the pxe file or config right?
# Don't function as a DNS server:
port=0
# Log lots of extra information about DHCP transactions.
log-dhcp
# Set the root directory for files available via FTP.
tftp-root=/tftpboot
# The boot filename, Server name, Server Ip Address
dhcp-boot=undionly.kpxe,,x.x.x.x
# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override
# PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 30
# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", undionly
# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses. Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=192.168.15.50,proxy
Mod edited to use code box.
I was able to get fog working in virtual box on an isolated virtual network on Centos 6.5 and create and drop images on virtual computers. I now want to setup a real fog server which is on the standard network and can image actual computers via pxe boot in the bios. The issue is that the dhcp server where I am can not be modified with the pxe information. I know I have to use proxy dhcp and have tried to use the write up for ubuntu, but I am stuck. The computer is getting dhcp address, but not reading (says the pxe file is missing) the pxe image file and erroring out.
Is there a step by step write up for Centos 6.5. What config files should I focus on to diagnose the issue?
Thanks for your help.
Everyone this was my problem. You have to take the user and password from the fog storage nodes under the fog system settings and put them into a hidden file in the opt/fog directory .fogsettings config file. After I did this the image created successfully without complaining about the ftp password. I will now try to drop the new image onto a new computer and see how I make out, but I think this will do it for me. Wow I have struggled with this for two weeks now. I like the concept of the fog imaging server and will now be able to really test it out.
Like everything else in life if you don’t struggle with it you will never learn anything. I learned a lot about linux by setting this up.
Thanks again.
/opt/fog/.fogsettings -> storageftpuser & storageftppass
I did not realize the .fogsettings file was invisible. Once I figured out how to see the invisible file I found the
snmysqluser=" "
snmysqlpass=" "
In the web page there are values for this which are automatically generated. I put these user and password values in and now I am able to erase the image from the web page. I am in the process of creating a new image now to see if this was the missing piece. Thanks for your help with this. I will post back if this works.
Fog FTP login fails after image creation, complains the ftp userid and password are not correct. Image creation is showing the user name and password which is the fog user id and password and the user id and password under storage management and tftp server.
I am using Centos 6.5 Fog 1.2.0. Passwords have all been confirmed. Ftp is working with the fog and fog created password from a windows client, can create, copy to and read from ftp:\images folder. Folder access rights look correct and seem to be working.
Something is not working after the image successfully creates. Also after the failure under image management I see the image but get a fogftp:login failed username fog Password (system generated password). Error also happens when I try to delete the created image from the image management screen. Image will not delete.
I have logged into Centos with the fog id and password from the tftp and storage screens which are the same in the web page, and I am able to go into the /images directory and erase the image folder with no issues. There must be a password which is not correct somewhere, but I can not find it. I went though the wilki on this and am still having a problem. Both firewall and seliunux are disabled. FTP from windows works, and I can get into the /images directory and erase the 99.5% complete image. I can not delete the image from the web page though with out getting the ftp log on error?
I originally posted this under another users problem by mistake, but I have moved it out to the root. Thanks for any help you can give.
I am having the exact same problem. I am using Centos 6.5 Fog 1.2.0. Passwords have all been confirmed. Ftp is working with the fog and fog created password from a windows client, can create, copy to and read from ftp:\images folder. Folder access rights look correct and seem to be working.
Something is not working after the image successfully creates. Also after the failure under image management I see the image but get a fogftp:login failed username fog Password (system generated password). Error also happens when I try to delete the created image from the image management screen. Image will not delete.