Categories

  • 12k Topics
    114k Posts
    C

    @Tom-Elliott apologies for the delay but I now had time to test and found the following:
    I am using Ubuntu 24.04
    I updated FOG to version: 1.5.10.1732

    I then tested a multicast and confirmed that partclone is still stuck at the first screen.

    When I run:

    sudo systemctl -l status FOGMulticastManager.service

    I see the following:

    Nov 03 13:22:12 fog-syd001 systemd[1]: FOGMulticastManager.service: Scheduled restart job, restart counter is at 1. Nov 03 13:22:12 fog-syd001 systemd[1]: Started FOGMulticastManager.service - FOGMulticastManager. Nov 03 13:22:13 fog-syd001 env[24152]: PHP Fatal error: Uncaught Error: Call to undefined function int() in /var/www/fog/lib/service/multicasttask.class.php:460 Nov 03 13:22:13 fog-syd001 env[24152]: Stack trace: Nov 03 13:22:13 fog-syd001 env[24152]: #0 /var/www/fog/lib/service/multicasttask.class.php(689): MulticastTask->getCMD() Nov 03 13:22:13 fog-syd001 env[24152]: #1 /var/www/fog/lib/service/multicastmanager.class.php(322): MulticastTask->startTask() Nov 03 13:22:13 fog-syd001 env[24152]: #2 /var/www/fog/lib/service/multicastmanager.class.php(639): MulticastManager->_serviceLoop() Nov 03 13:22:13 fog-syd001 env[24152]: #3 /opt/fog/service/FOGMulticastManager/FOGMulticastManager(37): MulticastManager->serviceRun() Nov 03 13:22:13 fog-syd001 env[24152]: #4 {main} Nov 03 13:22:13 fog-syd001 env[24152]: thrown in /var/www/fog/lib/service/multicasttask.class.php on line 460
  • Get the latest news on what's happening.
    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!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Cire3C

    @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 🙂

  • Report bugs, request features, or get the latest progress.
    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?

145

Online

12.4k

Users

17.4k

Topics

155.9k

Posts