FOG Problems

• R

  UNSOLVED Fog 1.2 to Fog 1.58 mysql export, after fog.sql import everithing ok, but no hosts in Web Ui
  • robo  

  6
  0
  Votes
  6
  Posts
  8
  Views

  R

  @Sebastian-Roth Thank you for your effort. Last night i v tested a new configuration. The problematic one where ;ubuntu 19.10 amd64 srv from scratch + git branch fog 1.5.8 + mysql import The configuration from last night; ubuntu 18.04 LTS amd64 srv, from scratch + manual install fog 1.3+ mysql import + upgrade thru git on the latest master branch fog 1.5.8. With the second configuration, no problems for now, i must deeply check, but it seems there is no issues. If there is another issue i v ask for help. Thank you Sebastian MfG Boris
• A

  UNSOLVED Windows 10x64 does not boot after restore (sporadically)
  • abulhol  

  7
  0
  Votes
  7
  Posts
  29
  Views

  A

  @JJ-Fullmer Just a short update on this issue: The NUC’s BIOS was outdated, and updating it failed for unknown reasons. We now replaced the NUC with a brand new one and hope to see the issue gone.
• C

  UNSOLVED PXE boot problems, TFTP, No configuration methods succeeded
  • c70m83  

  5
  0
  Votes
  5
  Posts
  9
  Views

  S

  @c70m83 Just to try and see why exactly those three (PC24, PC08 and PC12) seem problematic you might try to connect those to other ports on the switch where you know that other PCs work. As George said, PXE boot does not depend on Windows or any operating system. No matter what you have installed on disk PXE does work!! So if it used to work then something within your network / DHCP setup changed!
• A

  UNSOLVED No such file or directory (http: //ipxe.org/2d03e13b)
  • anon01013  

  6
  0
  Votes
  6
  Posts
  8
  Views

  S

  @anon01013 Possibly the VirtualBox VM is set to UEFI but pfSense might not provide PXE boot information for UEFI clients? Note for everyone: As far as I see in the picture this output we see here from iPXE is NOT the one delivered from the FOG server but the one build into VirtualBox.
• J

  UNSOLVED Fog 1.5.5 to 1.5.8 - Creating SSL Certificate - FAILED
  • JYost  

  3
  0
  Votes
  3
  Posts
  8
  Views

  S

  @JYost said in Fog 1.5.5 to 1.5.8 - Creating SSL Certificate - FAILED: Creating SSL Certificate …FAILED Please check the installer error log (/root/fogproject/bin/error_logs/) and post it here. Probably the last 15 lines will do. Don’t need the whole lot.
• 

  UNSOLVED proxydhcp offers were received, no dhcp offers were received
  dnsmasq fog 1.5.8 • • FuriousGamer065  

  2
  0
  Votes
  2
  Posts
  6
  Views

  

  This one is a bit hard to diagnose since you’ve provided so little information. Assuming all other systems pxe boot like you say, the fog server can probably be ruled out, as well as dnsmasq. The PXE rom lives on the network card/LOM so the PXE rom driver knows how to reach the network. So I would say network cable or you have 2 network adapters in that computer and you are trying to pxe boot from the wrong network adapter compared to where the pxe rom is running from.
• A

  UNSOLVED High CPU Usage
  • Arrowtron  

  30
  0
  Votes
  30
  Posts
  158
  Views

  

  @Arrowtron In addition to increasing your fog client checking time as was suggested by @Sebastian-Roth, and in addition to moving the database to InnoDB as suggested by @george1421 I’d recommend you go to 4 CPU cores.
• E

  SOLVED Authenticate on FOG API
  api help • • eseo-fcolas  

  5
  0
  Votes
  5
  Posts
  19
  Views

  

  What OS are you using to connect to the api? Shameless plug here for the api powershell module. I have a function called Set-FogServerSettings that helps with just inputting the api keys and it will handle the authentication from there with any function call. See the links in my signature. I originally made it cross-platform but it’s currently more windows oriented. Due to COVID-19 I am not working, which means I might have some free time (I say might because I also have a new baby). If you’re not running on windows I can dedicate some time to adding more linux support to the module since powershell core 6 and 7 are both cross platform on linux, mac, and windows. The module takes that simplified documentation and creates tab completable functions from the structure outlined in the documentation.
• A

  SOLVED Does FOG check free disk space before starting capture?
  • abulhol  

  2
  0
  Votes
  2
  Posts
  7
  Views

  S

  @abulhol FOG doesn’t check the free disk space before capturing an image. We consider this something the admin needs to take care of. As well we can’t be really sure how much space a new image would actually take.
• P

  SOLVED Loop during upgrade from 1.5.7 to 1.5.8
  • plegrand  

  10
  0
  Votes
  10
  Posts
  61
  Views

  S

  @plegrand Ops, I forgot to post here. This should be fixed in dev-branch now…
• B

  UNSOLVED Mysql Default password
  • bfriconneau  

  6
  0
  Votes
  6
  Posts
  18
  Views

  S

  @Wayne-Workman Thanks heaps for mentioning this here! We should really update that wiki page to help people fix this. Newer versions of MySQL/MariaDB behave very different and we have changed the old way of using an empty DB password.
• 

  SOLVED FOG FOS Drive Error (No Such file/directory)
  • imagingmaster21  

  5
  0
  Votes
  5
  Posts
  16
  Views

  

  @Sebastian-Roth Machine was working fine after re-image and then started having performance issues mainly with Office and did Office repair. We are probably going to pull machine back and do another RAM test along with Lenovo diagnostics. Maybe just even replace RAM. We do want to upgrade but we have been pretty swamped withe people working from home, so hopefully we can do this when things settle down :)
• M

  SOLVED Upgrade Debian 9 to Debian 10 FOG 1.5.7 and FOG 1.5.8
  • mousepl  

  3
  0
  Votes
  3
  Posts
  43
  Views

  S

  For anyone running into this. We’ve just pushed some changes to dev-branch and working-1.6 to make updating from Debian 9 to 10 easier. You should not be able to do this following the steps outlined here: sudo -i apt-get update && apt-get upgrade apt-get dist-upgrade reboot sed -i 's/stretch/buster/g' /etc/apt/sources.list apt-get update && apt-get upgrade apt-get dist-upgrade reboot apt-get --purge autoremove cat /etc/debian_release cd fogproject git checkout dev-branch git pull cd bin ./installfog.sh
• M

  SOLVED Hosts are looking for tftp server.
  • marted  

  51
  0
  Votes
  51
  Posts
  124
  Views

  S

  @marted Just want to keep this topic up as it might be very helpful for others. Not sure if you have time and access to systems right now though.
• K

  SOLVED chainloading failed hit s for the ipxe shell
  • kstrout  

  11
  0
  Votes
  11
  Posts
  35
  Views

  K

  It is working now so with Bios set to Auto (legacy First) and the exit mode set to GRUB_FIRST_HDD it boots!!! I tried it with UEFI and it didn’t work which is why I went to auto. Thanks for the help I appreciate it!
• A

  UNSOLVED FOG Image Tasking "Force Task"
  • alansopro  

  6
  0
  Votes
  6
  Posts
  24
  Views

  S

  @alansopro Somehow lost track of this and forgot about it, sorry! Now that I am starting to tackle this I see that it’s not as simple as I’d hoped. In a basic setup (single FOG server, no storage node, clean install, no plugins, unicast deploy) I don’t see the issue as described. So we need some more details of your setup: What does your storage setup look like, what nodes do you have? Any plugins you have enabled? When this happened, did you do a unicast or multicast deploy? As well I may ask you to do DB maintenance and try forcing a deploy task again. Just to make sure we are not hunting down a dead rabbit. I’ve already looked at the “force task” code and I have to say that I can imagine something can go wrong here if a plugin goes astray.
• T

  UNSOLVED directory listings enabled in fog-installation
  • Tywyn  

  6
  0
  Votes
  6
  Posts
  24
  Views

  S

  @astrugatch @Kiweegie Looking at this topic again after a while I am wondering if we’d just use a simple redirect as mentioned before. I just tested adding the following line in FOG’s apache config: RedirectMatch "^/$" "/fog/" Fairly straight forward and I would hope this doesn’t cause issues for existing installs. Though I am not exactly sure as many people use their FOG server for booting Live distros and we don’t know for sure how they setup it up. But the rule is very distinct and shouldn’t cause problems I would think. Except if you use the apache webserver to serve another website on that same server.
• D

  SOLVED Unable to reboot into FOG
  error fog 1.5.8 reboot • • dirtysoc  

  2
  0
  Votes
  2
  Posts
  7
  Views

  S

  @dirtysoc Good news, this is a known issue with VirtualBox. Switch to ipxe.pxe boot file and the issue will be gone.
• K

  UNSOLVED Equipment loans - how to assign loan to a user (and ideally integrate with AD)?
  • Kiweegie  

  3
  0
  Votes
  3
  Posts
  18
  Views

  K

  @Sebastian-Roth Hey Sebastian (and all other FOG devs and users out there) hope you and yours are staying safe and sound with whats going on in the world. I’d forgotten about this post myself I confess - I’ve been busy trying go setup our entire workforce across several sites to work from home. I know our service desk team would find this feature of great benefit as keeping reliable track of who was given a loaner laptop and when can be difficult without the right tool to do it. Excel sheets or even the ticketing system don’t manage this very well. But given whats going on just now for everyone its very much on the distant, nice to have when the worlds in a better place list. Stay safe everyone. Kiweegie.
• 

  UNSOLVED Upgrade from 1.5.7 to 1.5.8 issues
  • Chris Whiteley  

  42
  0
  Votes
  42
  Posts
  134
  Views

  S

  @Chris-Whiteley @george1421 Just wanna keep this topic up on the screen…