fog problem ?
-
Hmmm… interesting.
So lets see where you are at.
The device PXE (ROM) booted and downloaded iPXE. iPXE is running and detected your network adapter as a pcnet32 and then started a dhcp discovery again. This is all normal so far, but now you get a connection timeout. This makes me think there is a STP or spanning tree issue. Can you ensure your network switch has port fast or RSTP enabled on the link to this device?
It also appears that you are using the 1.2.0 version of fog. If this is a new fog installation, I would highly recommend you upgrade to the trunk version of fog (i.e. per 1.3.0).
One last bit of info, what device are you trying to pxe boot. Make and model.
-
@Quazz @george1421
so following the instruction of my supervisor, i’ll try to install once again fog but with dhcp managed by fog.
i will make a copy of the vm i actually have with the fog server and try the 2nd install on it and if it still don’t work an upgrade on trunk.
My supervisor don’t think that fog have a personnal firewall because we do nothing on it. If it’s the firewall of the network i don’t think it will be possible x) -
and now after trying a second install of fog i have this
-
This post is deleted! -
@Varion said:
@Quazz @george1421
so following the instruction of my supervisor, i’ll try to install once again fog but with dhcp managed by fog.FOG DHCP is not required. This is not your issue.
The target computer is getting the iPXE operating system. So dhcp is working as it should. DHCP is telling the target computer go to the fog computer at IP address (dhcp option 66) and get file undionly.kpxe (dhcp option 67). I can see that this file runs on your target computer because I see the iPXE status line. For this DHCP is good and not your problem.
The issue is the iPXE kernel can not get an IP address. This is typically because of one of two problems. 1) The device has a network adapter not supported by the iPXE kernel. 2) The problem is with your network switch in that it takes too long to start forwarding data, which is a problem with spanning tree settings.
Now from what I understand you are trying to pxe boot a virtual machine, that is why I see pcnet32 (which is an old internet adapter).
- What version of esxi are you trying to boot?
- I would strongly recommend that you upgrade your fog installation to the trunk version (pre 1.3.0) so if you have problems the developers can help fix the issue. https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
- You must confirm that you have disabled selinux and disabled the iptables firewall according to the FOG prerequisites or FOG server will not work as required.
-
Hi,
sorry this week-end i haven’t the time to work on it.
I start my VM with the fog server on it this morning and it work perfectly
i’ve upload an image 2min earlier.
I don’t know what happened during this week-end but it’s cool if it’s work now let see if it continue =pedit:
okay i’ve speak too quickly i have the same bug as before…
can an other computer create a bug like this ? ( my supervisor wasn’t here and his computer was off and when i came and start his computer it bug again ) it’s just a supposition. -
@Varion Which IP address does your FOG server have? Is it configured as static IP or does if get it’s IP via DHCP as well? On your FOG server run
ip addr show(maybe you need to runsudo ip addr showdepending on the host OS you have) and post the full output here in the forum.Is it possible that your supervisor’s machine is running a DHCP server or proxy service? This could actually cause problems (only when that machine is on!).
-
@Varion Try using a different boot file other than default.ipxe. Try using undionly.kkpxe, or if your are using newer UEFI devices, try ipxe.efi.
-
Okay, so my supervisor was thinkng that it could be a problem from virtualbox (where i create my fog server) and i create the fog server on the computer. It looks like it work for now i will see if it keep going like this.
-
So it work now but i have a problem with the upload of the image.
i try to upload an image and it copy the entire disk (even the space not used)
I’d like know if it’s normal or not and if their is a solution if it’s a problem from me.
i try to upload a debian 7.3
thanks guys
edit:
-
@Varion Keep going like what?
What did you do that got it operational for you? What changed, how did it get fixed?
Why would your fog server need to handle DHCP? You just edit the boot file that your dhcp server is currently handing out and you should be operational. Of course, that all aside, you would need to make sure that the switches you’re using are not in STP - Plain mode. If you MUST use STP, make sure it’s possible to use Rapid STP or PortFast (or the equivalent setting as defined for your network switches/routers).
No such file or directory as described only a few posts earlier would indicate, to me, that it cannot find the FOG Server by the IP Address (192.168.3.79). If FOG is handling the DHCP at that point, what’s giving FOG the IP address? Even if it’s statically defined it does not automatically mean it will operate.
What is your supervisor’s system doing? Is it handling DHCP (AKA proxy dhcp or a rogue dhcp server?)
-
@Tom-Elliott
keep going like that --> keep working
I have just install the fog server on a physical computer not a VM (with virtualbox) i have change nothing during the installation or anything else.
We have a switch that use STP but it’s not the problem (we have the server on the physical computer which work)
We have DHCP server but looks like it’s not the problem because our server work now.The only problem we have right now is that when we want to upload an image it take the full disk instead of just the occupied space.
My supervisor have a question, does the fog version 1.2.0 support LVM and did the upload take just the disk space occupied or the entire disk? -
@Varion said:
The only problem we have right now is that when we want to upload an image it take the full disk instead of just the occupied space.
My supervisor have a question, does the fog version 1.2.0 support LVM and did the upload take just the disk space occupied or the entire disk?FOG supports LVM disks, but only as non-resizable. That said, the free space on the disk compresses down to almost nothing. FOG currently supports resizing for Ext4 and NTFS.
-
@Wayne-Workman okay thank’s
Does the version of FOG 1.2.0 allow to choose the partition that we want to upload or not ?
Or how did we can upload an debian os install on lvm with some logic volume like swap of 4g, logic volume home of 300g (1% used)… or we have an other solution (like an other os or things like that), how can we make an efficient save with fog ( just the disk space used, without copy the 300g from the volume home which are useless for us). We just want to copy the OS for deploying it to new computer. -
i have "fatal error: failed to mount nfs volume when i want to upload
-
@Varion For the NFS issue, we need more details. What’s the image path inside that node’s storage management? What’s the contents of
/etc/exports? Have you ran through the Troubleshoot NFS article? -
@Wayne-Workman
/images
the server try to mount the nfs volume with the old server address. Where can we change that if it’s possible ?
mounting file system … mount: mounting 192.168.3.79:/images/dev/ on /images failed: No route to host
and the ip address of the fog server is 3.95
-
@Varion Changing a FOG server’s IP is not as easy as it might seam. Here are instructions on this: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
The error (wrong IP) you are seeing at this stage is caused the storage management settings in the web gui (Storage Management -> DefaultMember -> IP Address). But please make sure to follow the instructions in that wiki article and get it all corrected!
-
The default storage ip address is good, i’ve checked all the instructins in your link but nothing happen. The error message is still here
-
@Varion said:
@Wayne-Workman
/images
the server try to mount the nfs volume with the old server address. Where can we change that if it’s possible ?
mounting file system … mount: mounting 192.168.3.79:/images/dev/ on /images failed: No route to host
and the ip address of the fog server is 3.95What do you mean by:
@Varion said:
The default storage ip address is good, i’ve checked all the instructins in your link but nothing happen. The error message is still here
THe first picture doesn’t show anything the a directory contents of what appears to be the home folder of the user currently signed in.
What Sebastian is talking about is the IP Address within the Storage nodes under Storage Management Page. If your fog server is still looking at the “old” IP address for handling NFS this would explain the IP Address issue you’re describing. That OR your “old” fog server is still up and running under 192.168.3.79, and all of your bootup settings (TFTP Option 66/67) are still looking at the “old” fog server.
