Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  12k Topics

  114k Posts

  A

  @george1421 Well one of the reasons we run a windows server is because we run them in HA mode, but there doesn’t seem to be another DHCP server present from my testing. Tis very odd! But thank you for your help, at least you’ve confirmed we are doing the right things.

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  184 Topics

  825 Posts

  A

  @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  C

  @youzersef What if your router providing next server is pfsense.

  What needs to be changed in pfsense? My current settings are that of fog.

  Pfsense : 10.22.24.1 : (controls DHCP, next server, etc)
  Fog 10.22.24.5 : (Working flawless)
  iVentoy : 10.22.24.13

  Everything I try is sending client back to pfsense, and then errors because it’s getting the boot file for fog, when it’s expecting iventoy_loader_16000

  Thanks ! Time to get this project wrapped up 🙂

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  C

  I think I have found a bug.

  I registered a new host. I then created a deploy task against this host. I then delete this host via the webUI.

  My task list empties as it should, however if I look at my storage group activity on the dashboard there are still tasks queued:
  fcf286d6-a906-418c-a217-703b0ec8d363-image.png

  There is no tasks scheduled, queued or checked-in.

  Looking at the database I find the following:
  a06cf4fd-ee06-4f68-85eb-8efa8d0efde9-image.png

  There are tasks still queued for hosts that no longer exist in the host table.

  2 fixes needed:

  When host is deleted, all currently queued or checked-in tasks should be set to a taskStateID 5 or cancelled If there are tasks that are not set as canecelled for hosts that do not exist, then these tasks should be cancelled

  1 question:

  I have 24 queued tasks for hosts that do not exist. I see 4 on the webUI. I assume this is because there are 20 tasks with taskNFSGroupID and taskNFSMemberID set to 0. How do groups that do not exist get marked against a host / task?