FOG Problems

• E

  Host registration error.
  • erasp21

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• D

  Clients imaging despite recieving "Read ERROR: No such file or directory" and "ata1.00: failed command" errors
  • danieln

  14
  0
  Votes
  14
  Posts
  41
  Views

  

  @danieln said in Clients imaging despite recieving "Read ERROR: No such file or directory" and "ata1.00: failed command" errors:

  is there an easy way to update this kernel

  FOG (FOS) kernels can be downloaded from here https://fogproject.org/kernels/ download both the x64 and x32 bit kernels. Save the x64 as bzImage and the x32 ad bzImage32 (case is important). Then you can just move the files to /var/www/html/fog/service/ipxe directory on the FOG server. It probably wouldn’t hurt to rename the existing ones before you move the new kernels in. You can confirm the version of the bzImage files with file /var/www/html/fog/service/ipxe/bzImage It should print out the version of the kernel.

• P

  No configuration method succeeded
  • phm2000

  6
  0
  Votes
  6
  Posts
  12
  Views

  

  @phm2000 I don’t know that model but I did find that your switch does support “green ethernet” mode. I’m not saying that this IS the problem but if your only solution is to disable STP then I would look to see if green ethernet is enalbed on your switch. According to this article its disabled by default: https://community.hpe.com/t5/Comware-Based/How-to-disable-IEEE-802-3az-Energy-Efficient-Ethernet-feature-on/td-p/6896946# Look at the accepted solution.

  Disabling STP on user facing ports is not the best choice. You may need to get with a switch engineer to understand why turning on RSTP does not solve your problem (because turning off STP solves the net booting). From your description it sounds like the port is in standard STP mode even if you set it to RSTP. I assume (with RSTP on) placing a dumb (unmanged) cheap switch between the building switch and the pxe booting computer will also mask the problem. We will typically recommend this for people to test to see if the problem is spanning tree or not without changing the switch settings.

• M

  UEFI/BIOS Coexistence Help
  • MrAwesome987

  17
  0
  Votes
  17
  Posts
  58
  Views

  M

  @george1421 Yes, the IP is of the main (only) DHCP server.

  I removed the :UNDI:003016 policy and class, since, like you said, its redundant and too specific.

  I just confirmed the DHCP offer’s IP, and it is indeed on the same network as the policy is applied to on my DHCP server.

  I also checked my firewall to make sure it was not blocking anything. It does not appear to be blocking any traffic between the test PC and the DHCP server.

  Any other ideas? I feel like I’m missing something basic, but I have gone over the settings many times and it looks right.

• B

  Changed IP, reinstalling not an option
  • boriquaboy115

  3
  0
  Votes
  3
  Posts
  10
  Views

  S

  @boriquaboy115 Should be able to fix that without re-install. Go to the directory where you extracted the FOG installer (or cloned it via github). If you don’t have that anymore you can re-download it. Best to use the same version you installed before: https://github.com/FOGProject/fogproject/releases

  Change to root user (e.g. sudo -i or su -) and navigate to the subdirectory utils/FOGiPXE/ within the FOG installer dir. Then run the iPXE buildscript and copy over the new binaries that were generated by the build script:

  ./buildipxe.sh cd ../../packages/tftp/ find -type d -exec mkdir -p /tftpboot/{} \; find -type f -exec cp -fv {} /tftpboot/{} \;

  See if you clients are able to PXE boot again.

• X

  HTTP ipxe boot setting?
  • xburnerx00

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Edit the file /opt/fog.fogsettings and replace the IP address there.

  Then edit the /tftpboot/default.ipxe file

  in the fog settings and default storage node change the IP there.

  Finally rerun the fog installer once again to fix the rest of the bits.

• 

  Fog ProxyDHC with Fog and Pfsense on the same network
  • Sckendall

  8
  0
  Votes
  8
  Posts
  18
  Views

  

  @sckendall said in Fog ProxyDHC with Fog and Pfsense on the same network:

  Well, the question is whether it is possible to have two independent fog servers on the same network.

  Well this sentence changes everything.

  If you want to pxe boot on your laptop you will need an isolated network or if you are running a hypervisor on your laptop then you can create an internal network.

  I just think of an idea. Its possible if on your main FOG server, you create a custom FOG iPXE menu that links the fog server on your laptop. Then normal pxe booting to main fog server, then chain (ipxe command) to your FOG server. That is possible.

• P

  FOG 1.2.0 to FOG 1.5.9 import host csv error
  • pascald73

  3
  0
  Votes
  3
  Posts
  24
  Views

  P

  hello,
  I found the solution.
  looking at the databases, there are 5 fields on the fog 1.2.0 base and there are 9 fields for version 1.5.9.
  so the hots don’t appear.
  by importing the database on the new server and importing the csv host everything is ok.
  the export of the csv on the 1.2.0 server was with the separator ,
  I reworked the file with free office to put it in ;
  it works.
  I leave the solution here for old fogs who want to migrate to a new machine

• S

  Advanced Login
  • seppim

  2
  0
  Votes
  2
  Posts
  19
  Views

  S

  [push]

  Maybe someone has in idea whats wrong?

• T

  A tale as old as time: Could not mount images folder (/bin/fog/upload or /bin/fog/download) permission denied!
  • tmcwl

  7
  0
  Votes
  7
  Posts
  16
  Views

  T

  @george1421 That did the trick!

  I had previously added the images2 *(ro etc;etc;etc;) but did not run the sudo -exportfs -a command.

  I knew it was something simple. Thanks so much for your help!

• L

  SOLVED Bulk add hosts
  • LibraryMark

  6
  0
  Votes
  6
  Posts
  391
  Views

  S

  @aschaffer What do you mean by “needs to be touched”?

  By the way, this topic is years old and you might want to create a new one and post all your specific details there like version and a detailed description…

• T

  Error HTTP 5xx No master node available
  • tomtom2770

  5
  0
  Votes
  5
  Posts
  16
  Views

  

  @tomtom2770 So let me discuss what FOG needs to work in your environment.

  The master node is kind of the brains of the FOG system since it houses the fog database.

  The storage nodes are disk storage for deploy only. It needs to be in contact with the FOG server 100% of the time for the storage node to remain functional.

  So lets say you have 1 sites HQ and SiteA. You have a master node at HQ and a storage node at SiteA. At SiteA you have the dhcp options to point to the local storage node and the needed boot file.

  You pxe boot a target computer at SiteA. It downloads the boot file from the local storage node and iPXE starts up. Then iPXE reaches out to the local storage node to download default.ipxe file. That file points to your master node boot.php script which builds the iPXE Menu. If the computer isn’t registered, when you select register it will download FOS Linux (over the wan) from HQ to the target computer. (once the computer is registered and associated with a location, the storage node will be used for all other file transfers).

  Now if you have the fog client installed on the target computer it will only talk to the master node to get instructions (install snapin, update inventory, etc). If the target computer get an instruction to install a snapin, that snapin is downloaded from the local storage node.

  So the point here is that the HQ fog server is important here and must be at a fully routable location from all remote sites.

  If your site to site VPN ever goes down so does FOG imaging. Depending on your goal, number of client computers, and stability of the VPN network, you might want to install a full fog server at each location.

• 

  Issue deploying image to new Dell Latitude 5410
  • rogalskij

  5
  0
  Votes
  5
  Posts
  29
  Views

  

  @rogalskij The FOG developers are expecting the Linux kernel developers will take 5.10.x to LTS status. When they do the FOG developers will make 5.10.x the standard kernel in FOG. ref: https://www.kernel.org/

  FWIW, there was quite a few new drivers added to 5.9.x series (almost as many as was added to 5.5.x), so 5.10.x LTS can’t come fast enough because FOG will start running into that hardware soon.

• D

  ipxe/boot.php and bzImage running very slow
  • danieln

  5
  0
  Votes
  5
  Posts
  49
  Views

  D

  @sebastian-roth said in ipxe/boot.php and bzImage running very slow:

  @danieln said in ipxe/boot.php and bzImage running very slow:

  The only change was that I added one additional storage node.

  Storage node being in the same subnet as well?

  Correct. I double checked and it is on the same subnet.

• G

  ClearOS-DHCP, Fog, PXE, & dnsmasq
  • geardog

  5
  0
  Votes
  5
  Posts
  30
  Views

  S

  @geardog Two things from the tutorial I just want to point out:

  Make sure its at least version 2.76 by issuing this command at the fog server’s linux command prompt sudo dnsmasq -v. The version needs to be 2.76 or later.

  and as George already mentioned here:

  Be sure to replace <fog_server_ip> exactly with the IP address of your fog server. Be aware that <fog_server_ip> appears multiple times in the config file.

• H

  Hanging on ipxe initalizing devices.
  • Huecuva

  15
  0
  Votes
  15
  Posts
  34
  Views

  S

  @huecuva said in Hanging on ipxe initalizing devices.:

  Can those iPXE binaries be changed in the webgui?

  No because it all depends on the DHCP server you actually use in your network (quite often it’s not on the FOG server itself).

• R

  How install Debian 10.7.0 on the Fog Project
  • rubensurtfe 0

  14
  0
  Votes
  14
  Posts
  54
  Views

  

  @rubensurtfe-0 As soon as the boot files are sent to the target computer, the FOG server is no longer involved with the target computer. SO this error is with what ever OS is running.

• X

  "Please enter tftp server:" with single dhcp server
  • xcess

  18
  0
  Votes
  18
  Posts
  33
  Views

  X

  @george1421

  Now you said that isc-dhcp server worked?? The reason why I ask is that isc-dhcp server and dnsmasq do the same thing. So why would isc-dhcp server issue IP addresses and dnsmasq does not respond?

  To be honest, this is beyond me.

  Initially, when I configured the FOG server I installed isc-dhcp server, configured pool of addresses and added “next-server” and “filename”. Then I set bootprelay of the switch to point to the FOG server and everything worked (and still works if I go back to this scenario).
  Afterwards I realized that our expensive switch supports dhcp and decided to give it a shot (why use separate service for something that already runs on the switch, right?). Since then I’ve encountered this issue i.e. switch supporting only numerical option codes (66, 67 etc). Analyzing the frames turned out that my clients are unable to evaluate those options even though they do exist in the dhcp packets! Having “next-server” and “Boot file name” in the packet body seemed like the only way it works. I managed to confirm this by analyzing frames coming from my working isc-dhcp server.

  Now, you can probably see how strange it is.

• V

  How to delete images from FOG
  • vemoya

  4
  0
  Votes
  4
  Posts
  39
  Views

  

  @sebastian-roth I will probably put this in https://docs.fogproject.org/en/latest/management/image-management.html# in a new subsection for deleting images.

• A

  Missing storage
  • active-pcb

  2
  0
  Votes
  2
  Posts
  21
  Views

  S

  @active-pcb I guess the partitions were set to use a fair amount of the disk space for /home when you installed Ubuntu. Run sudo fdisk -l and post output here in the forums.