https://github.com/FOGProject/fogproject/issues/685

On the storage node, create a .my.cnf file in root’s home directory:

sudo tee /root/.my.cnf << ‘EOF’
[client]
skip-ssl = true
EOF

MariaDB will try to connect with SSL by default but that’s not enabled on the main FOG server. This is why I had to use the --ssl=FALSE flag when I connected to mysql manually.

The installation succeeded!

This is what I had to do, was in the same boat.

Go to /opt/fog/.fogsettings

Remove the sysv-rc-conf entry from the packages line from there. (Reference: https://github.com/FOGProject/fogproject/issues/797)

Lower down in the same file, set “php_ver=‘8.2’” to “php_ver=‘8.4’”

Exit and save.

Then I had to remove symlinks in Apache that were using the old php modules:

sudo unlink /etc/apache2/mods-enabled/php8.2.conf
sudo unlink /etc/apache2/mods-enabled/php8.2.load

Then add the new links:

sudo ln -s /etc/apache2/mods-available/php8.4.conf /etc/apache2/mods-enabled/php8.4.conf
sudo ln -s /etc/apache2/mods-available/php8.4.load /etc/apache2/mods-enabled/php8.4.load

So similar to the issue that I’ve raised prior with multiple NICs and @george1421 suggested I PXE booted the system again but went into DEBUG mode. Well as it appears the unused MAC address is now showing up on the interface that I had configured to connect to the network. Seeing that I did not assign an IP address to the second mac address the system would not proceed any further. The odd thing is that BOTH interfaces show up having the same mac address. It seems that there’s an issue with the FOS with newer Dell systems with multiple NICs.

If I disable one of the two NICs in the BIOS, and do the re-imaging process everything works fine…

Really looking for a fix for this…

Cheers

Jason Naughton

This is what is happening

What to do?

Thank you

Post the results of these two commands.

lsblk
df -h

It maybe easy or harder (but not impossible) depending on how you have the disk created.

In our firewalld rules we have

“Préparation du dépaquetage de …/isc-dhcp-server_4.4.3-P1-8_amd64.deb …
Dépaquetage de isc-dhcp-server (4.4.3-P1-8) sur (4.4.3-P1-8) …
Paramétrage de isc-dhcp-server (4.4.3-P1-8) …
Job for isc-dhcp-server.service failed because the control process exited with error code.
See “systemctl status isc-dhcp-server.service” and “journalctl -xeu isc-dhcp-server.service” for details.
invoke-rc.d: initscript isc-dhcp-server, action “restart” failed.”

I tried to reinsatll isc-dhcp-server separately on my computer but it could not work

I searched for a bug in https://www.isc.org/dhcp/
and there I found that this pacakge is not maintained any more.

“ISC has announced the end of maintenance for ISC DHCP as of the end of 2022. ISC will continue providing professional support services for existing subscribers, but does not intend to issue any further maintenance releases. For resources that may help in migrating your existing ISC DHCP server deployment to our newer DHCP server, Kea, please see this page.”

Will foginstall.sh be modified, or is a by-pass possible ?

The installation is like this…

sudo mono SmartInstaller.exe

…#######:.    …,#,…     .::##::.
               .:######          .:;####:…;#;…
               …##…        …##;,;##::::.##…
                  ,#          …##…##:::##     …::
                  ##    .::###,##.   . ##.::#.:######::.
               …##:::###::…#. …  .#…#. #…#:::.
               …:####:…    …##…##::##  …  #
                   #  .      …##:,;##;:::#: … ##…
                  .#  .       .:;####;::::.##:::;#:…
                   #                     …:;###…

###########################################
               #     FOG                                 #
               #     Free Computer Imaging Solution      #
               #                                         #
               #     https://www.fogproject.org/         #
               #                                         #
               #     Credits:                            #
               #     https://fogproject.org/Credits      #
               #     GNU GPL Version 3                   #
               ###########################################
               #           FOG Service Installer         #

------------------------------------License-----------------------------------

FOG Service Copyright 2014-2023 FOG Project
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain
conditions. See your FOG server under ‘FOG Configuration’ -> ‘License’ for
further information.

----------------------------------Information---------------------------------

Version…0.13.0
OS…Linux
Current Path…/root
Install Location…/opt/fog-service
Systemd…True
Initd…False

-----------------------------------Configure----------------------------------

FOG Server address [default: fogserver]: <FOG_SERVER_IP>
Webroot [default: /fog]:
Enable tray icon? [Y/n]:                 Y

Your hostname is <MY_SYSTEM_NAME>
This exceeds the 15 character limit.
Auto registration will not run until this is fixed.
Press ENTER to proceed with installation.
Version…0.13.0

Start FOG Service when done? [Y/n]:      S…Linux

----------------------------------Installing----------------------------------

Getting things ready…[Pass]
Installing files…[Pass]
Saving Configuration…[Pass]
Applying Configuration…[Pass]
Pinning FOG Project…[Pass]
Pinning Server…[Fail]

Installation failed, cleaning system

-----------------------------------Uninstall----------------------------------

Uninstalling…[Pass]

-----------------------------------Finished-----------------------------------

See /root/SmartInstaller.log for more information.

The SmartInstaller logs are like this :

3/18/2025 3:13:20 PM Installer Settings successfully saved in /opt/fog-service/settings.json
3/18/2025 3:13:20 PM Middleware::Communication Download: http://<FOG_SERVER_IP>/fog/management/other/ca.cert.der
3/18/2025 3:13:21 PM Middleware::Communication ERROR: Could not download file
3/18/2025 3:13:21 PM Middleware::Communication ERROR: The remote server returned an error: (403) Forbidden.
3/18/2025 3:13:21 PM Installer Could not download server CA cert from FOG server

I have configured Apache as well.
I can download this certificate manually to test 403 issue and it downloads the file in the system using this link http://<FOG_SERVER_IP>/fog/management/other/ca.cert.der

But, it fails while mono installation throwing 403 error.

I’m hoping for a solution here.
Looking forward…
Thanks.

I recently transferred a perfectly working fog project server to another server and pouched the postdownload script functionality. I’ve gone through a bit of debugging. I put a /bin/bash inside my /images/postdownloadscripts/fog.postdownload so that I could shell out and see why I’m not getting the client hostinfo that I used to fetch with curl leveraging the fog-api-token and fog-user-token.

I’ve validated that my ${FOG_API_TOKEN} contains the same string that is on my configuration page of my fog server. I’ve also validated that my ${FOG_USER_TOKEN} contains the same API string for a user within my user list. Both the user and the fog settings have the api enabled.

Yet if I issue the following from my bash shell on the client after doing the pxeboot:

curl -A “” -Lks
-o /tmp/hostinfo.sh
-H ‘Content-Type: application/json’
-H “fog-api-token: ${FOG_API_TOKEN}”
-H “fog-user-token: ${FOG_USER_TOKEN}”
${web}/service/hostinfo.php
–data “mac=$mac”

Where $mac is the mac address of the pxe booted client, and $web simply contains http://192.168.1.35/fog/. Yet the contents of the file /tmp/hostinfo.sh is essentially:

No token passed to authenticate this host

I kinda need the othertag1 from the fogserver where I store some unique information about the client. Prior to my moving of my server to the new configuration this worked fine… Any insight on this matter would be greatly appreiated.

default 0
timeout 0

title BIOS iPXE Boot
    root (hd0,0)    
    kernel /boot/ipxe.lkrn

title openSUSE - Kernel 3.1.0-1.2 
    root (hd0,0)
    cedarview_gfx.modeset=0
    kernel /boot/vmlinuz splash=silent quiet 
    initrd /boot/initrd

I have tested this and it works well , but I end up in a boot-loop and I can not see a method to automatically exit a FOG session that would allow me to move on to the next menu option as all EXIT options I have tried so far end up back at the GRUB menu with a default of iPXE

Is there a way to use a custom GRUB_EXIT_TO_MENU_OPTION or maybe some better way to achieve this ?

So far I have tried the following exit options
GRUB - finds the local GRUB , but oots to the default iPXE option
GRUB-FIRT-HDD -same as above , - I have the ipxe bootloader and menu option on the HDD
REFIND-EFI - this machine is very legacy and did not manage to load REFIND neither from FOG, nor a rEFInd bootable USB for testing ( this USB was tested on more modern machines and did work)
EXIT - Still ends up back at the same grub menu with iPXE as default

I can see that there are other ways to booting to iPXE ( eg bootable USB , BIOS option etc), but this method of adding the files to the main HDD would allow me to do all this remotely, without the need for access to the machine, e.g. over ssh and the basic concept is working well. I just am not sure how to solve the boot loop EXIT issue

We only have UEFI systems so testing legacy boot is not doable.

When deploying a RHEL image it will reboot into disk without issue and the disk efi entry is already there, but with sles it is missing.

Is there some required setting on the OS I need? Maybe RHEL sets some flag on disk?

Also, is there a possibility to have the OS boot directly without rebooting the system using switch_root /sbin/init, this is what warewulf v3 did. This allowed me to run any changes before rebooting including makeing sure efi boot params were correct using efibootmgr.

I have here an old FOG installation, where I forgot the credentials. Before I install it all from 0, I wanted to look into the database (I have access to the machine, where its running at). But when I want to connect with the informations from the .fogsettings file, I just get an error (ERROR 1045 (28000): Access denied for user).

Someone knows why I can’t login?

If you run the chmod 777 /images that will make the directory world writable but not the existing files / folders under that directory. If you use chmod -R 777 /images it will change everything under that directory to world writable.

But before you do that, the linux user fogproject should have read write access to /images. The password for that user is found in the hidden file /opt/fog/.fogsettings That is the user account fog uses to move files around while imaging.

il y a environ 18 minutes

@kelocktnt look in “Pending Hosts” on the hosts page. It should be the

OMG !!!
i’ve been walking past it since the beginning without seeing it!!! too newbiees

Thank youu @)

As this is a machine upgraded from debian 11, maybe it wasn’t using systemd. Installation of 1.6 worked no problem Thanks,

If you have verified you can log into the fog server via ftp as the fogproject user using the password saved in the fog ui then it has to be a permission issue on the /images directory.

The image capture process is

FOS Engine -> connects to /images/dev NFS share and creates a directory that matches it’s mac address
FOS Engine -> Uploads the disk connect as the root user (on the FOS Engine)
FOS Engine -> Connects to the FOG server as fogproject user and issues a mv command to move the directory from /images/dev/<mac_address> to /images/<image_name>
FOS Engine -> Logs out of ftp and completes the cleanup before reboot.

Though a workaround exists, so while, it would be a bug, it may not be the biggest concern to get fixed immediately over say actual imaging issues.

That .sysvd is suspicious and very similar to the thread above.