@rogalskij This is very interesting as initially I thought this was on some code I wrote (not that it still couldn’t be) but appears more like maybe the percent of free disk space has been unset and your drive is literally sitting as full as if at the hotdog championships and Joey Chestnut just won for 75th time in a row.

There’s a field in fog that is supposed to ensure free space left on the disk, but where yours is failing seems to be due to paging space / minimum size.

I might suggest, if you’re up for it again

Chkdisk again a few times,

Also defragment the disk a few times. THis should move your paging file (which cannot be resized around) toward the end of hte disk which shoul’d prevent the no space left on device issue I believe you’re currently seeing.

@Fog_Newb That’s an interesting fdrive you got there

Not sure how that would work but to your actual question:

Please try:

touch /images/.mntcheck

As that error is indicating that the /images mount (for deploy points) is missing that file.

@Fog_Newb there is a new sed statement that is trying to set the port for mountd to 20048, but seems it may be setting all ports after mountd to 20048. We are aware but trying to figure out why and how to fix.

@AUTH-IT-Center Should be addressed in the latest.

@george1421 we added a little security bit now too as getting the hostinfo gave us the host sensitive information (ad user , domain , password, etccc.)

https://github.com/FOGProject/fos/blob/master/Buildroot/board/FOG/FOS/rootfs_overlay/bin/fog#L9

This is the main difference.

We now need to get a token, and pass that token back to the hostinfo (it’s one time and locks upon initial request.)

Edit: Apologies on not posting the direct example, this was written while from my phone, not at a computer so copy paste wasn’t really “suitable”.

@kalmarteve What do you mean you don’t have permission?

YOu can read the log:

sudo tail -1000 /var/log/php-fpm/www-error.log

When prompted enter your sudo password.

@rogalskij I’m unable to replicate the problem:

I’m assuming this is what you mean?

@rogalskij so it seems your “ipaddress” is defined as your fqdn either on the IP address for the storage node directly.

I don’t know what your storage node settings look like but should be looked at likely from:

Storage Node-> DefaultMember

HOpefully that will help.

Normally if you can dereference the DNS name all would be fine so I’m just not sure where to help out.

But at least you know what is happening now?

Thank you for letting us know.

@Baessens Unforutnately the EFI stub: Measured initrd data into PCR 9 seems to be hitting us a lot lately and I don’t know why or what’s causing it.

I have heard mixed results of using older kernels, and sometimes newer ones fix it for the person. Not really sure what will be the right case here.

From FOG UI you can downgrade the init based kernel by FOG Configuration -> Kernel Update.

Please try some of them and let us know, if any, which works for you.

6.1.89 was one (20240430_1) was one that seemed to work for somebody. Maybe there?

The configs don’t change much between newer version, but we were seeing similar errors using the 6.1.22 version. This leads me to believe something was added to the kernel code, potentially removed, then re-added to it later. Just a suspicion I have.

@Quintin-Giesbrecht basically I think this is something in the kernel, but what it is we don’t have enough information yet. It’s possible a newer kernel might help.

Then again it could be something like:
https://forums.fogproject.org/topic/13620/very-slow-cloning-speed-on-specific-model/105?_=1729271500055

@Bhav We don’t have any information.

What I’m seeing, however, is that the machine you’re attempting to load is using UEFI booting, but you’re presenting MBR/Legacy PXE systems.

@Laurent The information is stored encrypted in the db + the transfer of information is encrypted between the client and the machine.

The only time the password is clear to any user is when you initially enter it in the field.

@fabritrento That’s not how this works. Just saying lol. 6.1.22 works fast for your situation, but that doesn’t mean there’s truly something wrong with the kernel for everybody. So when the next stable release comes out, you should remember to switch back to 6.1.22 and we’ll work to keep trying to update the kernels and hope that you’ll test them to see if it works for your situation so you don’t have to revert it to 6.1.22.

@NoIPName you didn’t provide a csv. You took a screenshot of an excel of your csv.

That said I suspect there’s an issue on the line of or immediately following the host you aren’t able to import.

I also seem to be seeing the same host name multiple times in your image so that might explain things as well.

Please provide your actual csv.

@Tom-Elliott I just did a test had had to run through this:
https://medium.com/yavar/send-mail-using-postfix-server-bbb08331d39d

Though I also had to setup an application specific password as opposed to the native password as my gmail account is MFA protected. So I also had to set an application specific password.

In the tutorial it has you building a sasl_passwd file instead of using your native gmail password you would enter your 16 character app specific password.

Similarly, while the instructions are being setup specific to debian/ubuntu based system, the basic premis is the same for any linux OS I guess.

Use your package manager, install postfix.
Set up your main.cf as instructed making necessary changes for your environment.
Create your sasl_passwd file
Map the sasl_passwd file to the db that postfix can use
restart postfix and test sending an email.

You should (before restarting postfix) check your file and fix up any issues in your main.cf file. (generally going to just be duplicate entries here or there.

https://myaccount.google.com/apppasswords
enter your gmail password and mfa as requried
create your application and setup name.
store the password it generates. It will likely show up as abcd abcd abcd abcd however the password will be without the spaces. and if your password is actually abcdabcdabcdabcd I won’t know it lol.

I certainly hope it’s not that rudimentary.

@rogalskij I suspect what you’re seeing is that the new FOG Server is unable to ping these devices, though I’m unsure as to why. Normally new devices will get set to “ping reachable” initially.

Edited to add:

However, pinging is not done by loading the page anymore as imagine having to wait for the page to load to figure out if it can or cannot ping the host? We, now, have a NRT methodology which is to say it’s not even remotely close to real time for ping status. Instead it’s ping reachable when the host is initially added, but then after 5 minutes an “actual” ping occurs (or whatever time you’ve defined for the service) and updates this value for the hosts. This allows the UI to run more efficiently and gives a general overview of what’s reachable. Though I’m sure this could use refinement, it’s better than nothing most of the time. However, if it cannot ping the host (and I suspect these are listed by hostname and the fog server likely cannot ping the dns hostnames nicely) it will update to whatever value, in your case that it cannot reach it.

What I think might work to address this would be to add the search domain of your network to your fog server so that it can ping your hostnames directly and that should fix your ping reachability.

For example. if the FQDN of the host is hostname.example.com and you ahve the host as hostname on the fog server you’d need your fog server to be able default it’s search domain for dns pinging to be example.com and then as long as DNS is working properly when it tries to ping hostname it will try against dns to the example.com domain structure.

@rogalskij Can you validate that your fog server CAN send email?

The database options are pretty simple:
(Warning the screenshot is from Working-1.6 version)

You obviously would want the FOG_EMAIL_ACTION (probably called Email Action in 1.5 versions) to be checked, and whatever the Email address you want.

That stated, all this is good and well, but you likely aren’t able to send emails from the server.

https://www.digitalocean.com/community/tutorials/send-email-linux-command-line

This link is an example of how to do so. If the cli method of email sending emails works and the fog server still isn’t it may mean you need php-mail installed? Just my thoughts.

@robertkwild There’s only one “stable” one “major/master” and then the one we’re working toward.

Technically there’s also “nightly” so 4 main versions:

• master branch = 1.5.10 (Currently) - Baseline for stable and current updates of the master.

• stable branch = 1.5.10.1634 (Currently) - This is considered (if you will in linux terms) LTS (we’re wanting 1.6 to come out but in the mean time we still need to keep things up and running of the stuff most people are using.)

• dev-branch branch = 1.5.10.x >= 1634 (currently) - This is where we do updates for issues found/reported/ and hopeful fixes to go into the next release of stable. This is what I would call “nightly” but it’s not quite bleeding edge either as this is just holding fixes for hte 1.5.10 and later versions.

• working-1.6 branch = 1.6. This is what some might consider alpha/beta (all working branches will be intended in this manner at least) in that it is where it’s the fully latest bleeding where we hope and want to get to with fog.

@Eazis It looks, to me, there’s a firmware that we may need to add to the kernel for these nics, but I don’t know what version? I see

rtl8125a-3
rtl8125b-1
rtl8125b-2
rtl8125bp-2
rtl8125d-1
rtl8125d-2

I suppose we could attempt to add all of them, but we don’t know which one applies to your specific device.

@sideone No worries. That just let’s us know in your specific case at least, it’s not booting in UEFI mode at least for NIC devices, so thank you!