@georgebells OK I have a proof of concept code for you to try.

Move the existing FOG sourced file out of the way

download the file from the google drive and upload this file on the fog server to /var/www/fog/lib/plugins/persistentgroups/class/ as persistentgroupsmanager.class.php

https://drive.google.com/file/d/1kbZqDKegvnGymQ_iY8oJYRyXsLw-RZZU/view?usp=sharing

Once the file is in place. Uninstall the persistent group plugin and reinstall it. Nothing needs to be changed other than uninstall and reinstall.

Once you uninstall and reinstall the plugin the database trigger will be updated with the new code.

This file only addresses the snapins. I’m a bit brain dead at the moment to tackle the printer bits. I’ll work on that later.

At the moment the developers look at this request and patch as a niche solution and probably won’t be added to the main line code. They are positioning this patch much like the one off kernel builds I do to solve a specific niche problem. With that said FOG is opensource and anyone is welcome to modify the code for their own needs.

@Poelie Not sure if you specific NAS will work but here is some information you can start working on: https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node

@seppim said in Capture Ubuntu 20.04 just free diskspace:

The Raid I need when a disk get failure (not so unusual)

If the disk dies you hopefully have a backup of the data as well as the FOG image to deploy that to a fresh disk in a few minutes.

Not saying that RAID is useless. Not at all. There are setups where RAID is great. But with FOG it’s not as simple if you want to use such things.

The setup as you have it now seems to be spread across three MD/RAID containers. I have no idea how to handle that in FOG. Simply setting host primary disk will probably not work.

I have not played with RAID setups yet and so this is just from the top of my head. Maybe there are other users with more insight into that topic. But I just want to give you hints trying to make this easier for you.

@danieln said in Clients imaging despite recieving "Read ERROR: No such file or directory" and "ata1.00: failed command" errors:

is there an easy way to update this kernel

FOG (FOS) kernels can be downloaded from here https://fogproject.org/kernels/ download both the x64 and x32 bit kernels. Save the x64 as bzImage and the x32 ad bzImage32 (case is important). Then you can just move the files to /var/www/html/fog/service/ipxe directory on the FOG server. It probably wouldn’t hurt to rename the existing ones before you move the new kernels in. You can confirm the version of the bzImage files with file /var/www/html/fog/service/ipxe/bzImage It should print out the version of the kernel.

@kek I have that feeling that it might be the CA certificate not being valid anymore. On install the fog-client software grabs that CA cert from your FOG server and installs it into mono’s certificate store.

Run certmgr -list -c -v -m Trust as root to see if a CA cert named FOG Server CA is there and still valid.

@phm2000 I don’t know that model but I did find that your switch does support “green ethernet” mode. I’m not saying that this IS the problem but if your only solution is to disable STP then I would look to see if green ethernet is enalbed on your switch. According to this article its disabled by default: https://community.hpe.com/t5/Comware-Based/How-to-disable-IEEE-802-3az-Energy-Efficient-Ethernet-feature-on/td-p/6896946# Look at the accepted solution.

Disabling STP on user facing ports is not the best choice. You may need to get with a switch engineer to understand why turning on RSTP does not solve your problem (because turning off STP solves the net booting). From your description it sounds like the port is in standard STP mode even if you set it to RSTP. I assume (with RSTP on) placing a dumb (unmanged) cheap switch between the building switch and the pxe booting computer will also mask the problem. We will typically recommend this for people to test to see if the problem is spanning tree or not without changing the switch settings.

@joyboy11111 So what did you install?
Has your installed version(s) (FOG host server and FOG version) changed?

@robpomeroy With the exception of testing the preceed file these instructions work as advertized: https://forums.fogproject.org/post/140720

@george1421 Yes, the IP is of the main (only) DHCP server.

I removed the :UNDI:003016 policy and class, since, like you said, its redundant and too specific.

I just confirmed the DHCP offer’s IP, and it is indeed on the same network as the policy is applied to on my DHCP server.

I also checked my firewall to make sure it was not blocking anything. It does not appear to be blocking any traffic between the test PC and the DHCP server.

Any other ideas? I feel like I’m missing something basic, but I have gone over the settings many times and it looks right.

@jkozee @Tom-Elliott Sorry for bringing up such an old topic again. Working on moving towards the new 5.10.x kernel I was looking at the patches we still apply to our kernel. Most are part of the upstream kernel but not the fix discussed in this topic.

Though the kernel code has changed a bit and I am wondering if we’d still see the slowness without our fix? Would anyone of you be able to replicate the issue with a 5.10.x kernel (with and without fix)?

Searching the web a little more I stumbled upon this patch that made it into the official kernel not long ago: https://patchwork.kernel.org/project/linux-input/patch/20200910143455.109293-12-boqun.feng@gmail.com/

Not sure but could play a role in this case. Anyway it would be great to see if the issue can still be replicated with the newer kernel - without fix.

@tom-elliott said in FOG 1.5.9.57 on Debian 10 mysql root password is blank:

We are a fully clean install. Meaning no packages except git are installed. No Apache, php, or MySQL. Why should the installer ask for root password here? It has never been setup before this point. There would be no password. FOG, in my opinion, should not be defining the root user password here either.

I think it should force the user to have a DB root password unless it’s a setup with local socket access as described below. That was one of the major points of re-writing that part of the installer. I tested a lot and would hope that the installer does what I say on all officially supported systems.

@julio You need to look into who installing those programs on Ubuntu/Debian is possible at all. For example, Notepad++ is a native Windows program and seems like you need to use snap (on Ubuntu) or even manually install wine to be able to run Notepad++ on Linux: https://itsfoss.com/notepad-plus-plus-linux/

Visual Studio Code seems to be available for Linux: https://code.visualstudio.com/download

Putty is available as official package on Ubuntu and Debian as far as I found.

An so on. This is well beyond what we can do for you! You need to figure out how the installations work or ask in different forums specific to that software you want to install. Start by searching the web.

As soon as you figured out how to install each software you can use bash scripts (mentioned below) to do the job for you.

@boriquaboy115 Should be able to fix that without re-install. Go to the directory where you extracted the FOG installer (or cloned it via github). If you don’t have that anymore you can re-download it. Best to use the same version you installed before: https://github.com/FOGProject/fogproject/releases

Change to root user (e.g. sudo -i or su -) and navigate to the subdirectory utils/FOGiPXE/ within the FOG installer dir. Then run the iPXE buildscript and copy over the new binaries that were generated by the build script:

See if you clients are able to PXE boot again.

Edit the file /opt/fog.fogsettings and replace the IP address there.

Then edit the /tftpboot/default.ipxe file

in the fog settings and default storage node change the IP there.

Finally rerun the fog installer once again to fix the rest of the bits.

@sckendall said in Fog ProxyDHC with Fog and Pfsense on the same network:

Well, the question is whether it is possible to have two independent fog servers on the same network.

Well this sentence changes everything.

If you want to pxe boot on your laptop you will need an isolated network or if you are running a hypervisor on your laptop then you can create an internal network.

I just think of an idea. Its possible if on your main FOG server, you create a custom FOG iPXE menu that links the fog server on your laptop. Then normal pxe booting to main fog server, then chain (ipxe command) to your FOG server. That is possible.

@george1421 Scratch that. I was confused about how this works, my apologies.

The Windows 10 installation I used to create my image is using an MBR, aka Legacy boot.

Thanks again for the quick reply.

@klisza1993 said in Fresh FOG installation and no Client detected:

Middleware::Communication ERROR: Communication ERROR: Request Aborted: Unable to create SSL / TLS secure channel.

I have never seen this error before and I am not sure where it might come from yet. In your first post you said you didn’t enable HTTPS when running the installer but you later post says you are using HTTPS as well. So I would imagine that a request to the HTTP URL is being redirected to HTTPS (default when you enable HTTPS with the installer) and the error stems from an issue with the server certificate.

Did you manually change the webserver configuration?

During troubleshooting, what i have discoverd, tah i can get communication with Server pasting this link into browser.:
https://192.168.205.132//fog/service/register.php?hostname=rk-test&mac=D6:C8:93:84:8B:24&newService&json
From my poinf of view its NOT SECURE.

Surely not ideal but you need to consider that FOG is not a secure product. Very few people help working on the code to find and fix bugs. You are more than welcome to join the force and get this out of the way.