NFS appears to be running.
My /etc/exports look like this:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
I just tried to run rpcbind and come to find out, it was not installed.
I just did a quick sudo apt-get install rpcbind. Let’s see if that worked!
Hello,
I’ve been posting a lot recently and I apologize but I am running out of time.
My latest issue is that whenever I attempt to upload an image, I get:
“RPC remote system error connection refused” and something similar to NFS share could no be mounted.
Does anyone have any ideas on how to solve this?
Thanks!
–
VMware ESXi - Ubuntu 10.04 (x64) - Fog
VMware ESXi - Windows Server 2012 (x64) - DHCP/DNS Server
Physical PCs across multiple subnets (subnets other than what the DHCP server and the Fog server are on)
I reinstalled Fog and put my DHCP server as the router’s address. This got me past the bad descriptor file error.
Now, I get: “RPC remote system error connection refused.”
Who knows if I’ll ever get this working. It’s just one error after another.
Alright, somehow, I made progress today. I can now successfully PXE boot in two out of eight labs.
I’ve been attempting to upload an image and when it gets to mounting the NFS share, I get the error: Bad descriptor file and then it restarts. Once again, I’m lost.
Here’s something else that is interesting:
When I’m booting a PC on the same subnet as my Fog server (10.200.200.203) and I choose to get IP information once I’m inside Fog, it shows that DHCP gave out the correct address.
It has to be something to do with my other PCs being outside of that subnet. We divide each lab into a different subnet so there’s no way that I can really join them all together.
On a Windows box in the 10.110.100.x subnet, the OS pulls this from my DHCP server:
DHCP Enabled: Yes
Autoconfiguration Enabled: Yes
IPv4 Address: 10.110.100.92
Subnet Mask: 255.255.254.0
Default Gateway: 10.110.100.254
DHCP Server: 10.200.200.3
However, if I PXE boot, it never gets DHCP so it doesn’t continue into PXE.
I use to use Alitirs and it worked just fine. We had its PXE server set to “Use the DHCP port.”
The pool is definitely not exhausted. If it boots to Windows, it gets its DHCP address.
Yes (to your second post).
In my internal network, there is no firewall whatsoever.
On the subnet where I have my Fog server setup, it PXE boots just fine. On any other subnet, it will not get a DHCP address which leads it to be unable to PXE boot.
Here is /tftpboot/pxelinux.cfg/default:
DEFAULT vesamenu.c32
MENU TITLE FOG Computer Cloning Solution
MENU BACKGROUND fog/bg.png
MENU MASTER PASSWD $1$0123456789
\n
menu color title 1;36;44 #ffffffff #00000000 std
\n
LABEL fog.local
localboot 0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive.
If you are unsure, select this option.
ENDTEXT
\n
LABEL fog.memtest
kernel fog/memtest/memtest
MENU LABEL Run Memtest86+
TEXT HELP
Run Memtest86+ on the client computer.
ENDTEXT
\n
LABEL fog.reg
MENU LABEL Quick Host Registration and Inventory
TEXT HELP
Automatically register the client computer,
and perform a hardware inventory.
ENDTEXT
\n
LABEL fog.reginput
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mode$
MENU LABEL Perform Full Host Registration and Inventory
TEXT HELP
Perform a full host registration on the client
computer, perform a hardware inventory, and
optionally image the host.
ENDTEXT
\n
LABEL fog.quickimage
MENU PASSWD $1$0123456789
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Quick Image
TEXT HELP
This mode will allow you to image this host quickly with
it’s default assigned image.
ENDTEXT
\n
LABEL fog.sysinfo
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Client System Information
TEXT HELP
View basic client information such as MAC address
and FOG compatibility.
ENDTEXT
LABEL fog.debug
MENU PASSWD $1$0123456789
kernel fog/kernel/bzImage
append initrd=fog/images/init.gz root=/dev/ram0 rw ramdisk_size=127000 ip=dhcp dns= mod$
MENU LABEL Debug Mode
TEXT HELP
Debug mode will load the boot image and load a prompt so
you can run any commands you wish.
ENDTEXT
\n
PROMPT 0
TIMEOUT 30\n
Syslog says this:
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: error 0 TFTP Aborted received from 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: failed sending /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.0 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/c9a90b22-2b83-11dc-9346-00e01$
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/01-00-07-e9-1a-82-98 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786429 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78642 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7864 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A786 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A78 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A7 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0A not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: file /tftpboot/pxelinux.cfg/0 not found
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/vesamenu.c32 to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/pxelinux.cfg/default to 10.120.100.41
Aug 17 02:41:08 Fog dnsmasq-tftp[885]: sent /tftpboot/fog/bg.png to 10.120.100.41
The service is still not running. ps -A|grep tftp comes back with nothing.
I tried to find a log in /var/log that looked like tftp but I could not find one.
Well, unfortunately the sleep 30 did not make a difference. Instead of waiting until morning, I remoted into my work PC, which remoted into an old imaging server, which remoted into a computer on a different subnet that had VMware Workstation on it.
Even with the sleep 30, Fog is still not working for other subnets outside of its own.
I just remoted in and ran “ps -A | grep tftp” and I get back nothing. I guess I’ll try the “sleep 30” tomorrow.
I’ll keep you posted!
Yup, my DHCP options 66 and 67 are set correctly. I can try to “sleep 30” and see what happens but if that was the case (that TFTP starts too early), wouldn’t I not be able to PXE boot into Fog at all?
I can PXE boot into Fog if I’m on the same subnet as the Fog server.
I cannot PXE boot into Fog if I’m on a different subnet as the Fog server.
Either way, I’ll try in the morning and post how it went!
Thanks!
Alright, I’ve managed to clear this up by setting option 60 of my DHCP server to “PXEClient.”
The only issue now is that the computers get stuck at getting a DHCP address.
The weird thing is: a VM will pxeboot just fine but my physical machines wait for a DHCP address that they never get.
Again, I’m running Fog on Ubuntu 10.04 and on a separate machine, I’m running my DHCP server on Windows Server 2012.
*EDIT: Anything on the same subnet as the fog server will get DHCP fine. Anything outside of that subnet will not. I’ve tried to configure dnsmasq by doing: “dhcp-range=IP of my Fog Server,proxy,255.0.0.0” with no luck.
Hello,
I’m back with a new question!
I’m running Fog alongside my DHCP server (Windows Server 2012) and for some reason, TFTP keeps timing out at PXE boot.
I’ve captured traffic using Wireshark and it looks something like this:
Server sends data packet “Block 0” to client
Client tells server “Fragemented IP protocol”
Server sends data packet “Block 1” to client
Client tells server “Acknowledgement, Block: 0”
And this repeats until it times out. Just sending block 0 and 1 back and forth.
I’m completely lost and any help would be greatly appreciated!
Thanks!
Never mind! I figured it out finally!
I was changing the global scope options on my DHCP server but each individual scope still have option 67 going to our old imaging server’s PXE boot file.
Hello,
I work in a lab environment that is controlled by a Windows Server 2012 DHCP server.
I currently have Fog installed on an Ubuntu 10.04 box and have been attempting to PXE boot off of it.
For some reason, I continually receive: “File not found” during PXE boot and am unable to proceed any further.
I have done (on another box): tftp [my server’s IP] and then get pxelinux.0 with success.
I don’t understand why my PC’s can’t PXE boot if I can pull the file manually.
In Server 2012, I have configured option 66 to my server’s IP and option 67 to pxelinux.0.
Any help would be [B]greatly[/B] appreciated!
Thank you!