• 0 Votes
    15 Posts
    514 Views
    R

    @JCS-RVK Okay so I don’t see why this kernel wouldn’t work for you with those settings. Only difference I can think of may be the initrd version that is being loaded. I know that @BPSTravis is using the latest released version so it wouldn’t hurt to update yours too.

    I also see that you are running an older version of FOG. You could upgrade to the latest stable release and that will also download the latest initrd.

    You could also download it manually if you don’t want to update FOG:

    On your FOG server, run this command to download the latest initrd
    wget https://github.com/FOGProject/fos/releases/download/20260306/init.xz

    Move it to the correct location like this:
    sudo mv init.xz /var/www/fog/service/ipxe/

    Then you need to change the permissions and ownership of that file:
    sudo chmod 644 /var/www/fog/service/ipxe/init.xz

    Red Had based server: sudo chown fogproject:apache /var/www/fog/service/ipxe/init.xz

    Debian based server: sudo chown fogproject:www-data /var/www/fog/service/ipxe/init.xz

  • FOG Secure Boot with Shim

    Tutorials
    6
    2 Votes
    6 Posts
    3k Views
    T

    @KMEH Hi,

    I tried your method and it only partially worked. It reached the FOG menu correctly after enrolling the key, but the problem arises when I try to perform a quickreg or deploy an image. In both cases, I get the following error (it starts working again when I disable Secure Boot)fog uefi error.png

    my version is 1.5.10

  • Database Error when select a group

    Unsolved FOG Problems
    3
    0 Votes
    3 Posts
    27 Views
    D

    @Tom-Elliott Hi Tom,

    log for apache error:

    [Wed Apr 01 16:05:36.847438 2026] [proxy_fcgi:error] [pid 1232] [client 172.28.1.84:48932] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84' [Wed Apr 01 16:05:36.860169 2026] [proxy_fcgi:error] [pid 1233] [client 172.28.1.84:48946] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84' [Wed Apr 01 16:05:36.877158 2026] [proxy_fcgi:error] [pid 1234] [client 172.28.1.84:48952] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84' [Wed Apr 01 16:05:36.889945 2026] [proxy_fcgi:error] [pid 1231] [client 172.28.1.84:48968] AH01071: Got error 'PHP message: PHP Warning: session_start(): open(/var/lib/php/sessions/sess_f9273cevne2k8cci10csjt7b81, O_RDWR) failed: Permission denied (13) in /var/www/fog/commons/init.php on line 84; PHP message: PHP Warning: session_start(): Failed to read session data: files (path: /var/lib/php/sessions) in /var/www/fog/commons/init.php on line 84'

    the php-fpm error:

    [01-Apr-2026 12:57:13] NOTICE: Terminating ... [01-Apr-2026 12:57:13] NOTICE: exiting, bye-bye! [01-Apr-2026 15:57:34] NOTICE: fpm is running, pid 758 [01-Apr-2026 15:57:34] NOTICE: ready to handle connections [01-Apr-2026 15:57:34] NOTICE: systemd monitor interval set to 10000ms
  • Detected Hardware unit hang

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    23 Views
    No one has replied
  • image Multicast issue

    Unsolved FOG Problems
    6
    0 Votes
    6 Posts
    79 Views
    B

    @Tom-Elliott
    I did not update yet to 1824, but i did SELECT * FROM HISTORY;

    MariaDB [fog]> SELECT * FROM history; +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | hID | hText | hUser | hTime | hIP | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | 1 | [2026-04-01 08:33:55] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 08:33:55 | 10.10.3.116 | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ 1 row in set (0.000 sec)

    the new session i create are not shown, and dont work until i run the maintenance queries

    then it shows in history table:

    MariaDB [fog]> SELECT * FROM history; +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | hID | hText | hUser | hTime | hIP | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ | 1 | [2026-04-01 08:33:55] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 08:33:55 | 10.10.3.116 | | 2 | [2026-04-01 09:10:37] MulticastSession ID: 1 NAME: test has been successfully updated. | fog | 2026-04-01 09:10:37 | 10.10.3.116 | +-----+----------------------------------------------------------------------------------------+-------+---------------------+-------------+ 2 rows in set (0.000 sec)
  • Boot and Nuke/Disk Wipe PXE Menu - Any Method Welcome!

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    847 Views
    P

    Hello @jrajra,
    I got this to work on my instance using ShredOS by doing the following:

    Log in to your Fog web portal Go to “Fog Configuration” Click the “iPXE New Menu Entry” button Enter the following details:
    * Menu Item=ShredOS
    * Description=Boot and Shred (AutoNuke)
    * Menu Show with=Not Registered Hosts
    * Parameters= kernel https://${fog-ip}/shredos/boot/shredos console=tty3 loglevel=3 shredos_exclude_boot_disc="yes" nwipe_options="--autonuke --nowait --method=zero --noblank --nousb --PDFreportpath=noPDF --autopoweroff" boot Log into your Fog Linux server Open the terminal Run the following commands: mkdir /iso mkdir /var/www/html/shredos wget -O /iso/ShredOS.iso https://github.com/PartialVolume/shredos.x86_64/releases/download/v2025.11_28_x86-64_0.40/shredos-2025.11_28_x86-64_v0.40_20260204.iso sudo mount -t iso9660 -o loop /iso/ShreadOS.iso /var/www/html/shredos chmod -R 777 /var/www/html/shredos

    Doing these steps should create a “New Menu Entry” for ShreadOS and specify to shred upon boot, don’t write a completion file, & then turn off the device. (For safety in our environment, I have this option only appear if the device is not registered.)
    It then downloaded the ShreadOS file from Github & then mounted the iso as an accessible boot file in the Fog URL. (You can manually download the file & put it in the “/iso” folder instead if you want.)

    I have tried this with dban as well, but that only worked for old BIOS based computers. This one on the other hand works for UEFI computers.
    I also found this article that might help you: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images
    I hope this helps you,
    Preston

  • Sysprep in FOG?

    General
    2
    0 Votes
    2 Posts
    35 Views
    T

    I think I figured it out. I need to run sysprep on the machine I am imaging before capture the image.

  • Schedule Multicast Tasks Issues

    Unsolved FOG Problems
    10
    1 Votes
    10 Posts
    355 Views
    Tom ElliottT

    @devle I’ve made a couple of edits, though I still cannot replicate the problem you’re seeing.

    You shouldn’t see the errors any more (just saying), though I don’t know if these things will fix whatever problem you’re seeing.

  • FOG ubuntu image fails to update database

    Unsolved FOG Problems
    29
    0 Votes
    29 Posts
    1k Views
    JGeearJ

    @Tom-Elliott All good the last update fixed the issue!

  • upload failed to set permissons (prepareUploadLocation)

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    146 Views
    No one has replied
  • Windows 11 | 65x HP Z2 Tower G1i

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    245 Views
    K

    Can I specify in FOG which hard drive to clone to? For example, using the serial number? That could be stored in the host entry

  • Linux Mint, ran updates and now get HTTP 500 errors

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    192 Views
    No one has replied
  • Image creation and network connection

    Unsolved FOG Problems
    5
    0 Votes
    5 Posts
    383 Views
    R

    @BLT I don’t necessarily have a timeline for the final release but I did just release an experimental kernel with a newer nic driver. It may work for you if you want to give it a try.

  • Host Service Settings not Saving after changes

    Unsolved FOG Problems
    1
    0 Votes
    1 Posts
    241 Views
    No one has replied
  • Slow computer listing and high CPU with version 1.5.1.01798

    Solved FOG Problems
    34
    1 Votes
    34 Posts
    959 Views
    I

    @Infojoe And a real question : How can I mark this as “solved” ?

  • issue with updating / isntall script

    Unsolved FOG Problems
    2
    0 Votes
    2 Posts
    327 Views
    P

    My workarounds for update on Debian Trixie are:

    A)
    git checkout master ; git pull
    userdel fogproject
    cd bin ; ./installfog.sh

    or
    B)
    apt install lastlog2
    git checkout master ; git pull
    ln -s /usr/bin/lastlog2 /usr/bin/lastlog
    cd bin ; ./installfog.sh

    Peter

  • Kernel Update Failed transfer

    Solved FOG Problems
    17
    0 Votes
    17 Posts
    3k Views
    P

    @george1421 I probably found the reason of disSYNC of fog password and FOG settings. My old fog generated password included an & char (password looked like q&Y**********) but after some updates I found q&#38#38#38…********** in FOG_TFTP_FTP_PASSWORD and Storage Management Password.

    To solve thi issue , I used https://forums.fogproject.org/topic/11203/resyncing-fog-s-service-account-password bit first I changed password in /opt/fog/.fogsettings.

    Then update

    update FOG_TFTP_FTP_PASSWORD update Storage Management Password, delete fogproject user (debian 13 installer bug lastlog vs. lastlog2) rerun installfog.sh

    Now kernel update (tftp access) is working again.

  • Issue with active directory

    Unsolved Windows Problems
    1
    0 Votes
    1 Posts
    56 Views
    No one has replied
  • FOG hangs on "... free base memory after PXE unload"

    Unsolved FOG Problems
    4
    0 Votes
    4 Posts
    1k Views
    R

    @jas777 Hi sorry for the delay. I believe I have the solution for this issue.
    I haven’t been able fully test these changes on physical hardware, so I pushed them to another branch. Please clone the repository and change the branch like this before installing:

    git clone https://github.com/fogproject/fogproject.git cd fogproject git switch ipxe-bios-test

    Let me know if it works out for you.

  • 0 Votes
    1 Posts
    100 Views
    No one has replied