FOG Problems

• H

  UNSOLVED Replication Bandwidth
  • Hanz  

  6
  0
  Votes
  6
  Posts
  4
  Views

  H

  @george1421 The weird and suspicious part is that 1.5.5 was last known working version, 1.5.7…I’ll also note that the parrallel behavior has always performed that way, at least for quite some versions now. I could actually transfer a single new captured image to all nodes at the same time and they would all run at their perspective top speeds (I have 4 schools that only have 100Mb connection and the rest are all gigabit. This speed is definitely new though.
• 

  UNSOLVED Full C:\ After Imaging Inconsistent
  • imagingmaster21  

  23
  0
  Votes
  23
  Posts
  89
  Views

  

  @Sebastian-Roth We have imaged 20 computers of different models without the issue. So far so good.
• M

  UNSOLVED TFTP PXE-E32 Time OUT
  • Mammadoff  

  5
  0
  Votes
  5
  Posts
  11
  Views

  M

  Dear george1421 , Finally i solved my problem. For Future guys , you need to add this line also to your /etc/dhcp/dhcpd.conf file . next-server and some ip address , like : next-server 192.168.x.x. my mistake was that i was writing it with “option” word . But next-server is string and it must be without option word. :-) Thank you for your support , This can be marked as solved . Good Luck to all.
• S

  UNSOLVED Unable to register Host on Fog
  • sehume  

  8
  0
  Votes
  8
  Posts
  20
  Views

  

  @sehume Well this is an interesting issue… The next steps are to see what the pxe booting client is seeing, because something is going on there. I have a suspicion, but lets test it. Manually register this host from the picture. Schedule a debug capture or deploy (don’t care). Before you schedule the task, tick the debug checkbox, then schedule the task. PXE boot the target computer. After a few screens of text where you have to clear with the enter key you should be dropped to a linux command prompt. You may get the same error message about connecting to the fog server, just press enter like you did before. At the FOS Linux command prompt, on the target computer, key in ip addr show confirm that eth0 has an IP address. Please post a clear picture of the output of that command here. Ping the fog server from the target computer. Post the results of the test. Next we are going to do the http test from the target computer. Key in the following command curl -Ikfs http://10.245.220.30/fog/management/index.php --connect-timeout 5 The success response will start out with HTTP/1.1 200 OK Lets see what info those tests provide.
• R

  UNSOLVED Inventory Report is blank, host list contains hundreds of entries with full inventory
  • Rivybeast  

  23
  0
  Votes
  23
  Posts
  63
  Views

  R

  Yep. I apologize. The entire page is not blank, just that it doesn’t show any data:
• C

  UNSOLVED FOG 1.5.7 Update Database Issue
  • chaonatic  

  10
  0
  Votes
  10
  Posts
  55
  Views

  S

  @chaonatic Try to manually connect to the DB and see if that works: mysql -u root -p (just hit ENTER when it asks for a password if yours is empty) As well you might want to read this one: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy
• D

  UNSOLVED Can't replicate image to other node
  • DJGRP  

  2
  0
  Votes
  2
  Posts
  9
  Views

  S

  @DJGRP Replication between a master node and a storage node is all done by the master node’s FOGImageReplicator service. This services also runs on the storage node but you can completely ignore that. Although the log for the 1st node is missing a fair amount of information at the beginning we still see a piece of information that points to it replicating images (Started sync for Image win10v1903 - Resource id #1976). To be able to diagnose this we need the full log of the 1st node. As well I am wondering which version of FOG you run. There were some major fixes and changes in the replication code in FOG 1.5.6! If you still run an older version I can imagine this causing trouble if you have huge images going through a link with little bandwidth.
• T

  SOLVED Fog Startup and Log in issue
  • techadmin  

  5
  0
  Votes
  5
  Posts
  12
  Views

  T

  Never mind I have found the answer at https://www.youtube.com/watch?v=QSpGaeHlkoE Made it so easy even a cave man could do it
• J

  UNSOLVED TFTP Not Working
  • jconway1006  

  8
  0
  Votes
  8
  Posts
  15
  Views

  

  @jconway1006 So you have ping connection but you can’t get to the fog ui externally. Do you (from your workstation) have direct internet access or do you need to go through a proxy server to get to the internet? From your workstation can you ftp to the fog server? The login is fog or fogproject depending on what version of fog is install < 1.5.6 is fog >= 1.5.6 is fogproject and the password is located in the hidden file /opt/fog/.fogsettings If ftp works then we need to understand why http is not working because you will have tested tcp connectivity with ftp.
• A

  SOLVED How to monitor Snap-in activity
  • altitudehack  

  13
  0
  Votes
  13
  Posts
  28
  Views

  A

  @Sebastian-Roth Got it. Thank you very much!
• A

  SOLVED Adding normal wipe to PXE boot menu
  • ayoward  

  9
  0
  Votes
  9
  Posts
  279
  Views

  

  @londonfog I don’t specifically know the wipe function, but I might guess it would only wipe the target (defined) hard drive in the host configuration. If you were ok with scripting it wouldn’t be that difficult to update the fog.wipe module to just loop through the disks instead of the one pointed to by getHardDisk function. ref: https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog.wipe patching FOS is pretty simple to do too without needing to unpack and pack the inits.
• 

  SOLVED Error trying to restore GPT partition tables. Exit returned code 4
  • Matthieu Jacquart  

  36
  0
  Votes
  36
  Posts
  237
  Views

  

  @Sebastian-Roth Hi, thanks so much for your work and help, I’ll test as soon as I came back to work, after 19th August.
• M

  SOLVED Unable to deploy images on 1.5.7
  • Mx7Nine  

  11
  0
  Votes
  11
  Posts
  74
  Views

  M

  Just got round to reapplying the upgrade and testing. Everything seems to working perfectly now. Thanks for the quick response and fix.
• A

  SOLVED Fog image size too big (500 GB/takes around 2hours to capture and deploy)
  • azra  

  13
  0
  Votes
  13
  Posts
  62
  Views

  S

  @azra So what does manage-bde -status C: show now on this system? As well, please schedule a debug capture task (just as you would normally schedule a task but before you actually click “create task” there is a check box for debug). Boot up the machine and hit ENTER a couple times to get to the command prompt. Here run parted -l, take a picture of the output and post here. EDIT: Tom just had a great idea. Maybe it’s not sda1 or C: that captures as RAW anymore but one of the other partitions?! Please pay attention to the partition numbers (sda1, sda2, sda3) on the blue partclone window.
• A

  SOLVED Printer Management Not adding printer unless one is added manually
  • awellis  

  7
  0
  Votes
  7
  Posts
  142
  Views

  A

  OK thanks! I really appreciate how active you guys are here!
• J

  UNSOLVED Windows 10 Error on deployment only on 1st attempts...
  • jflippen  

  14
  0
  Votes
  14
  Posts
  57
  Views

  J

  @george1421 Here is what shows up as mounted on the storage node: Firewalld stopped and disabled. sestatus is in permissive mode.
• M

  UNSOLVED 1.5.6 : Small local disk and the rest unallocated
  • marcolefo  

  7
  0
  Votes
  7
  Posts
  87
  Views

  S

  @marcolefo New inits are ready for testing. Download 64 Bit and 32 Bit and put those in /var/www/html/fog/service/ipxe/ dir on your FOG server. Probably good to rename the original ones instead of overwriting. As well you need to check the RAM SIZE option in FOG configuration, FOG settings. Need to be 275000 with the newer inits.
• B

  UNSOLVED GPT Partition Tables Error
  • Bullet  

  15
  0
  Votes
  15
  Posts
  82
  Views

  S

  @Bullet I suggest you update to the latest FOG version 1.5.7 we just released. There is a chance this might help you here.
• L

  UNSOLVED Wipe destination drive(s) prior to deploying image
  • londonfog  

  2
  0
  Votes
  2
  Posts
  14
  Views

  S

  @londonfog There is a long story about NVMe drives swaping around possibly on every reboot as the kernel does not seem to enumerate the drives always in the same order as it does with ATA/SCSI drives. For more details see here: https://forums.fogproject.org/topic/12959/dell-7730-precision-laptop-deploy-gpt-error-message For your situation: I am not sure what we can do to help you work around this. Please read through the other topic and see if you can get an idea on this.
• K

  SOLVED Image sharing between sites
  • KennethJ  

  15
  0
  Votes
  15
  Posts
  80
  Views

  K

  @Quazz Thank you. I’ll look into the API. This issue could probably be closed now. The image “export/import through API”-issue seems to me is a new and separate, though closely connected, issue. For future readers the best solution, if FTP is possible over your network, would be to set up the remote servers as a “storage node” with “Is Master Node” unchecked. When this is done you simply check the “Replicate?” field for the images you want to be synchronized across all sites. You will still need to use the import/export functionality to make the images available at the remote sites. However if FTP is not possible over your network you need to use rsync or scp or your preferred file transfer method, to transfer the images. (More examples can be found here: https://wiki.fogproject.org/wiki/index.php?title=Migrate_images_manually) This also requires the use of the import/export functionality.