FOG Problems

• T

  Solved Service Settings revert to "all unchecked"
  • Taspharel

  5
  0
  Votes
  5
  Posts
  61
  Views

  T

  Solved by Tom Elliot as per this thread: https://forums.fogproject.org/topic/11717/fog-1-5-2-host-module-settings-don-t-save/7
• X

  Solved API broken after update to 1.5.2
  • Xenorites

  3
  0
  Votes
  3
  Posts
  66
  Views

  X

  Working branch appears to have fixed the issue. Thanks!
• Z

  Unsolved PXE Background Image and Screen Resolution?
  • Zer0Cool

  3
  0
  Votes
  3
  Posts
  49
  Views

  P

  If it helps, I remember changing bg.png in a past version by using the GIMP and then compressing it to minimal filesize (an online tool like compresspng.com/tinypng.com gave the best results back then)
• H

  Unsolved UEFI resizing
  • Hammett131

  5
  0
  Votes
  5
  Posts
  64
  Views

  H

  @george1421 It did work thanks! But now after I deployed it on the same model computer Fog keeps trying to run maintenance restart and also never changed the name If you want I can make a different post instead of in here.
• B

  Unsolved Hard Drive, SSD, & M.2
  • BREIT

  29
  0
  Votes
  29
  Posts
  306
  Views

  B

  @breit said in Hard Drive, SSD, & M.2: b3:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 [144d:a804] Subsystem: Samsung Electronics Co Ltd Device [144d:a801] Kernel driver in use: nvme Kernel modules: nvme I haven’t done a full comparison of the two lspci files yet but just a quick look the last line above is missing from the FOG lspci data. Maybe its not loading that controller and Fedora is?
• S

  Cant boot to fog UEFI or Legacy
  • Snaggel

  3
  0
  Votes
  3
  Posts
  42
  Views

  S

  ok uploading it did say 100% sorry about that. here is a new one.[0_1524250529919_output2.pcap](Uploading 100%) it was a pcap i will change the EXT. changed ext to txt. 0_1524250667836_output2.txt
• J

  Unsolved Error returned: Type: 2 (already checked permissions/credentials)
  • JoshuaIan

  1
  0
  Votes
  1
  Posts
  18
  Views

  No one has replied

• L

  Unsolved Upgrade to 1.5.2 can't copy binaries where needed
  • LibraryMark

  2
  0
  Votes
  2
  Posts
  50
  Views

  

  @librarymark said in Upgrade to 1.5.2 can't copy binaries where needed: Where do I need to look to figure out this problem? In the bin directory where the installfog.sh is, you’ll find a new directory with all the error output from the installer in it. The actual error will be in there typically at the bottom.
• J

  Unsolved Can't update kernel
  • Jfulton

  2
  0
  Votes
  2
  Posts
  32
  Views

  

  @jfulton FOG version?
• T

  Unsolved Problems adding storage node
  • Tiagoluz

  9
  0
  Votes
  9
  Posts
  108
  Views

  

  @Tiagoluz we need more information, like the OS your main fog server is using. Concerning that problem, If it’s Ubuntu, odds are you simply need to enable remote access for the fogstorage mysql user. Also, this article outlines all of that as well as other troubleshooting.: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Easy_.26_quick_MySQL_test
• A

  Unsolved Black screen at registration
  • Arcfury

  5
  0
  Votes
  5
  Posts
  41
  Views

  A

  @george1421 because of the VM i’m letting fog do the dhcp. I get the white fog screen with the options and when i pick quick reg i get the bzImage and init.xz ok on screen and after it shows this it goes black.
• T

  503 Service Unavailable Error
  • Troye Johnson

  52
  0
  Votes
  52
  Posts
  433
  Views

  C

  @george1421 Hey George. My www-error.log is not very useful. Only has one line in it. "[15-Apr-2018 03:45:01] NOTICE: error log file re-opened" just to be cleat the error I get when running a user tracking report in chrome is "This page isn’t working 10.214.14.27 is currently unable to handle this request. HTTP ERROR 500" should i still go ahead and perform the changes you asked for?
• Z

  Unsolved UEFI PXE not downloading ipxe.efi file
  • zacadams

  5
  0
  Votes
  5
  Posts
  47
  Views

  H

  @zacadams It will boot to legacy bios but you download your uefi image then just changed to uefi after the imaging is done. Or are you trying to upload an image?
• R

  Unsolved Image task ignoring location settings for nodes and hosts
  host node location • • rhyspowell

  8
  0
  Votes
  8
  Posts
  103
  Views

  R

  Thank you for your help Tom. I am going to re-build with a fresh OS install and install the working branch directly tomorrow morning. After downgrading to 1.4.4, I was still having issues. I looked in the SQL database, found some entries in the location and locationAssist tables which were incorrect. I cleared these entries after uninstalling the plugin. I reinstalled it and still had the issue with the wrong node being selected. I will let you know if I continue to have issues after a fresh rebuild on all nodes.
• B

  Unsolved MacBook(s) and FOG:
  • BardWood

  2
  0
  Votes
  2
  Posts
  47
  Views

  

  @bardwood Generally we want to know exact FOG versions because you saying ‘latest FOG’ does not help the next person who reads your thread. Please provide an exact version. FOG has had an isc-dhcp configuration that supports Macs for a year or two now. You may need to play around with the boot file to find one that works. All of the available boot files are in /tftpboot. You will find this article of interest: https://wiki.fogproject.org/wiki/index.php?title=FOG_on_a_MAC Also asking @Sebastian-Roth to take a look at this thread when he has some time.
• L

  Unsolved Client does not communicate with Fog server
  • Lemeunier

  7
  0
  Votes
  7
  Posts
  115
  Views

  L

  @joe-schmitt Tkx… ;)
• 

  Solved Fog 1.5.2 Plugin system broken.
  • Greg Plamondon

  2
  0
  Votes
  2
  Posts
  44
  Views

  

  I’m aware of the issue and have already fixed this in the working branch.
• B

  FOG 1.5.2 Canges in FOG-Settings will not be stored and AD-Settings are wiped out
  • BB-IKT

  1
  0
  Votes
  1
  Posts
  31
  Views

  No one has replied

• 

  Solved Error when capturing image
  • Matthieu Jacquart

  23
  0
  Votes
  23
  Posts
  1906
  Views

  

  Hello, excuse-me for awakening a quite old post, I’m not asking for help but adding some contribution in case of someone else has same problem. I also had yesterday the same message when trying to capture a syspreped Windows 10 pro 1709 image (with Virtual Box) I tried several basic steps suggested in this post, but the thing that simply worked for me was tu upgrade fog server… (It was not updated since two or three months) I can’t reproduce the issue, but it can be a step to try before recreating a new Windows sysprep image :)
• T

  Unsolved UEFI - No fog menu
  uefi • • totoro

  11
  0
  Votes
  11
  Posts
  168
  Views

  T

  @Quazz True, but I wan’t to see what can be done with UEFI. In the future I will make almost all my deployment by UEFI boot. So I hop it will work find, I see than UEFI is not standardize as Legacy. So it was to understand.