FOG Problems

• J

  Fog Exit Windows 10
  • J-Fog

  28
  0
  Votes
  28
  Posts
  2624
  Views

  S

  @dbrilliant Can’t see what your post has to do with the original indeed very old topic. We have enough room in our forums for everyone to open fresh specific topics and I ask you to do so. Tell us about your setup, FOG version, OS and so on…
• T

  Unsolved Unable to PXE Boot to Fog Menu.
  • Technolust

  19
  0
  Votes
  19
  Posts
  134
  Views

  

  @Technolust I would set the default dhcp options to undionly.kpxe to cover all bios machines, then create a filter for arch 0007 and 0009 that will cover all of the common uefi systems. We have seen some tablets that are 64 bit processors but pinned to 32 bits and report as 32 bits during pxe booting. If you don’t plan on any 32 bit processors then don’t add the filter. Just be aware of some of the tablets if you ever get one.
• W

  Unsolved Snapin replication no working
  • wanderson

  8
  0
  Votes
  8
  Posts
  117
  Views

  S

  @wanderson Sorry for the long deply!! Re-reading your postings I am wondering why you use FOG 1.4.0. This is years old and there have been many changes since. We do not have many people working on FOG at the moment and therefore can’t support older versions. If you upgrade to 1.5.4 and still see the same issue we might be able to help you out. Don’t get me wrong. If I could see why this is not working I would surely tell you. It’s just too little information and the version gap that I tell you we won’t be able to help just like this.
• F

  Unsolved Host Issues
  • Fithian

  5
  0
  Votes
  5
  Posts
  12
  Views

  S

  @Fithian Sorry if I wasn’t clear enough. Those are two different things. Database is holding all the host, image definitions and FOG settings. If this is lost you will have to create those things manually again. Either register clients through the FOG menu or manually add clients in the web UI. The other thing is the fog client being installed on the client computers. They won’t connect to your new FOG server unless you are able to recover the SSL certs/keys from your old server and put in place on the new one. Read the article I posted. As you have not told us much about what is lost and what is still left I am just doing guess work here. If your old server is totally gone and you can’t get hold of the SSL files you will probably need to re-deploy the fog-client to your hosts. Any deployment tool will do that job I reckon.
• K

  Solved Unable to reset web login
  • Karl_MCS

  2
  0
  Votes
  2
  Posts
  10
  Views

  

  The wiki page you linked earlier should allow you to log into the web console. You might have to reboot he FOG server after you reset the password in the database because of the way FOG cache’s recent activity. https://wiki.fogproject.org/wiki/index.php?title=Reset_WebUI_FOG_password From the wiki this command should do it for you. UPDATE users SET uPass = MD5('password') WHERE uName = 'fog'; exit; I do have to say FOG 1.2.0 running on ubuntu 12.04 is really old. Unless you really need access to the images stored on that server, I (personally) would just spin up a new FOG server using a current build. FOG 1.2.0 doesn’t support win10, uefi firmware, nvme disks, or current hardware. If you need the images from the FOG 1.2.0 server you can copy them over to a new fog server and use them.
• M

  Unsolved Replication Issue
  • mronh

  25
  0
  Votes
  25
  Posts
  278
  Views

  M

  @Sebastian-Roth ok, theres some defunct processes in the fog server after some replication ( delete parts and etc… ) 17914 ? Z 0:00 [sh] <defunct> 20702 ? Z 0:00 [sh] <defunct> 21632 ? Z 0:00 [sh] <defunct> 24658 ? Z 0:00 [sh] <defunct> 27305 ? Z 0:00 [sh] <defunct> 28423 ? Z 0:00 [sh] <defunct> 31260 pts/0 S+ 0:00 grep defunct
• J

  Unsolved WI-FI mac as default mac address
  • John L Clark

  2
  0
  Votes
  2
  Posts
  38
  Views

  S

  @John-L-Clark This is out of FOGs scope as we find WIFI not to be a reliable connection for deploying or capturing an image to/from a PC. So years back it was decided to ignore WIFI adapters altogether. We don’t have drivers for WIFI enabled in the iPXE boot nor have we included drivers in the Linux kernel that we use in our FOS imaging environment booted on the client machines. Would be a huge task to add this and make it work reliably in most cases (thinking about different WIFI standards, driver issues and encryption stuff). Why do you want WIFI to be the default/primary MAC?
• S

  Unsolved Error joins domains and change name
  • sapeurorca

  2
  0
  Votes
  2
  Posts
  16
  Views

  

  @sapeurorca Try to reset encryption for that host, try to re-install the fog client on that host.
• 

  Unsolved FOG API AD JSON Settings
  active director powershell api help • • RobTitian16

  2
  0
  Votes
  2
  Posts
  48
  Views

  S

  @RobTitian16 Sorry for the late reply. Your topic is pretty advanced and I do not seem to find the time to dive into it or even test this out myself. So you are saying the host is created and you can see it in the web UI, right? What exactly do you mean by “when checking the FOG client AD settings, I see everything is left unchecked”? Are the fields like ADDomain, ADUser and such empty or is it “just” the checkboxes useAD and enforce not being populated? If it’s the later I can imagine that it’s some kind of type conversion thing. If you send true in PowerShell way of boolean variable then this might not turn out to be properly transfered to the database. I have not played much with the API Tom created yet but I guess it should understand 1 as true. But that’s just a guess. Have you tried different values yet? The other thing that jumped at me is the message in the fog client log: Module is disabled globally on the FOG server
• F

  Unsolved {fogip}/fogservice/Pre_stage1.php not found
  • Fimlore

  3
  0
  Votes
  3
  Posts
  18
  Views

  F

  It is a fresh install, on that part. I did mess with settings on the Imaging section (changed the DefaultMember to /images/FOGimages) I did not change the FOG settings
• D

  Unsolved NFS versus SunRPC
  • DJ...

  13
  0
  Votes
  13
  Posts
  233
  Views

  S

  Why does a switch block such packets?? It’s not a switch’s business to do so!!! ;-) As we use Buildroot which might be a bit more minimalistic in some places. On the other hand it could be Ubuntu using a patched version of NFS mount that does the special call on port 2049. Not sure though.
• J

  Solved Multicast data address not change from one task to another one
  • Jose Cacho

  16
  0
  Votes
  16
  Posts
  786
  Views

  

  @Fernando-Gietz said in Multicast data address not change from one task to another one: Se añade esta linea para que asigne direcciones IP diferentes a cada tarea multicast I’ve added the patch, but a little more checking involved. This has been added to both the working and working-1.6 branches. It tests the set value for the $address variable. If this variable is set, it will calculate the address. Here’s the snippet of lines: if ($address) { $address = long2ip( ip2long($address) + ( ( $this->getPortBase() / 2 + 1 ) % self::getSetting('FOG_MULTICAST_MAX_SESSIONS') ) ); } Hopefully this will address the problem people have been seeing and allow the use of multiple sessions.
• T

  Unsolved Multicast sometimes fast sometimes extremely slow
  • tesparza

  5
  0
  Votes
  5
  Posts
  47
  Views

  

  Just in the fwiw bucket, we recently found out that if you have 2 or more simultaneous multicasts streams going at one time, the trasfer rates drop off quite a bit. I do remember seeing someone create a patch to change the multicast base IP address with each new stream. That seemed to resolve the issue. [edit] Updated info: https://forums.fogproject.org/topic/12300/multicast-data-address-not-change-from-one-task-to-another-one/16
• T

  Unsolved Windows 10 Automatic Repair being caused by FOG
  • tesparza

  4
  0
  Votes
  4
  Posts
  54
  Views

  S

  @tesparza Which version of FOG do you run? I know we have a fair amount of users doing Win 10 with FOG and don’t see all of them reporting this issue. Not saying that FOG isn’t doing this but I guess it’s more likely something with your image. Is bitlocker turned off? manage-bde -status manage-bde -off C:
• B

  Solved It takes longer Time (More Than 5 Minutes) Erasing current MBR/GPT tables.
  • Basavarajnc

  16
  0
  Votes
  16
  Posts
  709
  Views

  S

  @Nicolas-T @phil-dosi @Basavarajnc @compman @Tywyn Good news to all of you, we have figured out what is causing the slowness and fixed it. It’s been a longer story [ref] - thanks again to @Quazz for doing lots of testing and finding very helpful stuff to figure this out! As we have not had enough time to push for a new release yet you can simply update to the latest kernel and inits like this: sudo -i cd /var/www/fog/service/ipxe mv bzImage bzImage.orig wget https://fogproject.org/kernels/bzImage mv bzImage32 bzImage32.orig wget https://fogproject.org/kernels/bzImage32 mv init.xz init.xz.orig wget https://fogproject.org/inits/init.xz mv init_32.xz init_32.xz.orig wget https://fogproject.org/inits/init_32.xz
• Y

  Solved Erasing current MBR/GPT table issue
  • ykarami

  12
  0
  Votes
  12
  Posts
  907
  Views

  S

  @fogmania @ykarami Good news to all of you, we have figured out what is causing the slowness and fixed it. It’s been a longer story [ref] - thanks again to @Quazz for doing lots of testing and finding very helpful stuff to figure this out! As we have not had enough time to push for a new release yet you can simply update to the latest kernel and inits like this: sudo -i cd /var/www/fog/service/ipxe mv bzImage bzImage.orig wget https://fogproject.org/kernels/bzImage mv bzImage32 bzImage32.orig wget https://fogproject.org/kernels/bzImage32 mv init.xz init.xz.orig wget https://fogproject.org/inits/init.xz mv init_32.xz init_32.xz.orig wget https://fogproject.org/inits/init_32.xz
• L

  Solved Erasing current MBR/GPT tables.... taking about 5-10 minutes
  • Lemeunier

  27
  2
  Votes
  27
  Posts
  2201
  Views

  S

  @Lemeunier @andreiv @benc @matijn @dbettens @MCSDFog @JGallo @jclumbo33 @luco60 Good news to all of you, we have figured out what is causing the slowness and fixed it. It’s been a longer story [ref] - thanks again to @Quazz for doing lots of testing and finding very helpful stuff to figure this out! As we have not had enough time to push for a new release yet you can simply update to the latest kernel and inits like this: sudo -i cd /var/www/fog/service/ipxe mv bzImage bzImage.orig wget https://fogproject.org/kernels/bzImage mv bzImage32 bzImage32.orig wget https://fogproject.org/kernels/bzImage32 mv init.xz init.xz.orig wget https://fogproject.org/inits/init.xz mv init_32.xz init_32.xz.orig wget https://fogproject.org/inits/init_32.xz
• D

  Unsolved Fog server needs updating-not working correctly
  • Dee

  2
  0
  Votes
  2
  Posts
  19
  Views

  S

  @Dee Updating to the latest version is a good idea in general but as you seem to not have much experience with FOG and possibly Linux yet I am wondering if we better try to fix your issue before diving into a full upgrade. I’m hoping that updating it will fix the issue of it not capturing images. Please explain in more detail what’s happening. Error messages? Please take pictures and post here.
• 

  Solved FOG Kernel panic at startup with some systems
  kernel panic • • mckayj

  12
  0
  Votes
  12
  Posts
  70
  Views

  S

  @mckayj @Quazz Great this has turned out to fix the issues on those CPUs. Thanks heaps!! Will add x2apic to the official FOG kernel build. Let’s hope this is not going to cause any trouble for other devices. ;-) Edit: Added the option, will be in the official binaries soon: https://github.com/FOGProject/fos/commit/34967bf3f42fe56d835e1e179cdea78213ab3b6b
• M

  Solved Image files and Snapin files not deleted
  • MarkG

  8
  0
  Votes
  8
  Posts
  53
  Views

  S

  @MarkG said in Image files and Snapin files not deleted: Bug in 1.5.0? Possibly. 1.5.0 is long away and I don’t have all the changes in the back of my mind… ;-) So updating to the latest will fix the issue, that’s good!