@lucasgfaj have you turned off secure boot?

@JCS-RVK Based on the limited information I see:

VGA RAM on yours is 8MiB vs 16MiB (doubt this would be the issue):

Of other note is the “Secure boot -> Propogate Certificates” which seems to be missing on yours?

Also His VM has 8 cpu limits and memory is much higher (4/16 vs 4/4 on yours):

I’m not saying these are the definitive causes of the problem you’re seeing, rather just pointing out the differences I’m seeing at a glance.

Why one side works, vs the other, I don’t know (using this XCP-ng specific kernel of course)

@devle Can you post your apache error log or php-fpm?

Please see my signature to see where to locate those.

@JCS-RVK Roger thank you.

I know @BPSTravis was able to test with XCP and this particular kernel, so if you’d be willing to maybe share the VM Configuration less any ‘secret’ data?

@JCS-RVK https://www.reddit.com/r/Ubuntu/comments/1jc7bzj/install_hangs_after_efi_stub_measured_initrd_data/

I’m using this link, I know it’s a thirdparty link but wanted to show my thoughts here.

Based on what I’m seeing -> it would seem to me that the output is working just fine, but sending to a different Video output port than the expected one when the machine boots.

Since it’s waiting on input, the machine appears to be “Hung” but it’s not really, so maybe (without making any other changes) If you’re able connect a monitor (or maybe multiple monitors) to all the Video ports on the machine and see which one is directing video to.

yes, I know this can be clumsy becuase one video card might have multiple output ports.

I hate this issue because it never seems to have a solution, but maybe that’s because there (technically speaking) wasn’t anything wrong. The kernel has decided to send the output somewhere else.

@JCS-RVK said in EFI Stub Errors on XCP-ng Virtual Machine Attempting 'Perform Full Host Registration and Inventory':

EFI stub: Measured initrd data into PCR 9.

Do you have nomodeset as a kernel argument set somewhere?

Maybe on the Host kernel args or Global Kernel Args?

@JCS-RVK Would you be willing to disable your TPM on the XCP-ng device and see if that helps?

@boombasstic You’re able to test this on your own already:

Change your branch from stable -> dev-branch

cd /path/to/installer
git checkout dev-branch
git pull
cd bin
sudo ./installfog.sh -y

This will install whatever is “bleeding edge” on the development (which eventually roll up into the stable automatically on the 15th of each month).

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

@boombasstic Can you check DB with: SELECT * FROM HISTORY; after your entry?

When I test in 1824, I’m not seeing the problem. So it’s possible a future set of updates fixed the problem you’re specifically looking at.

When a MC task cancels (or completes) the session name is expected to be cleared out because you may need to reuse the session name down the road.

I’m seeing the clients and time are being set correctly.

Maybe I’m not understanding what exactly you’re doing?

Similarly, I started 2 multicast sessions for the exact same image, and I’m unable to replicate what you’re seeing.

i also cancelled one then started a new session and that worked.

To be fair (like I said) I’m on 1824 so maybe we unknowingly fixed the problem you’re hitting right now?

@devle I’m the developer for FOG so I’m almost always at the “latest” because i’m the one making them.

The version I’m at currently is ending in 2283 (so about 6 commits ahead of you.)

Yes, cron tasks are expected to have stMinute, stHour, stDOM, stMonth, stDOW filled out and delayed tasks would not have this filled out (and the stDateTime would have the timestamp of when that task is expected to kick off.)

@devle The first one appears to be set to run at 15:00

I don’t know what timezone you’re in, but I suspect your server’s timezone is showing UTC.

It’s interesting but it shows you should be seeing them trigger at 2026-03-26 15:00 (~ 1.5 hrs from right now, and 1.75 hrs from right now)

So it does appear scheduled tasks are working appropriately since restarting the service at least?

Also, i might suggest updating the latest working-1.6 as that will kick the tires around other services as well.

You are able to set the UI datetime FOG Configuration -> FOG Settings -> look for TZ_INFO and update to your relevant Timezone.

It does seem, maybe, your FOGScheduler service may need a good kick though?

@devle So I’m unable to replicate this:

[03-26-26 11:46:47 am]  * 1 task found.
[03-26-26 11:46:47 am]  * Checking for expired checked-in tasks...
[03-26-26 11:46:47 am]  * Scheduled Task run time: Thu, 26 Mar 2026 12:00:00 +0000
[03-26-26 11:46:47 am]  * This is a cron style task that should not run now. 
^C
telliott@7550precision:~/fogproject$ date -u
Thu Mar 26 11:46:57 AM UTC 2026
telliott@7550precision:~/fogproject$

The item I have:

MariaDB [fog]> select * from scheduledTasks\G
*************************** 1. row ***************************
         stID: 2
       stName: Multi-Cast Task
       stDesc: 
       stType: C
 stTaskTypeID: 8
     stMinute: 0
       stHour: *
        stDOM: *
      stMonth: *
        stDOW: *
    stIsGroup: 1
stGroupHostID: 1
    stImageID: 0
   stShutDown: 
     stOther1: 
     stOther2: -1
     stOther3: fog
     stOther4: 1
     stOther5: 
   stDateTime: 0
     stActive: 1
1 row in set (0.000 sec)

@Infojoe Unfortunately my test environment where I would normally work on these things hasn’t been behaving nicely.

Luckily, however, a fellow developer @rodluz was able to narrow the “what” and I believe I have fixed it.

The issue at least based on what was found:

PHP 8.1 deprecated the FILTER_SANITIZE_STRING feature and I replaced it with FILTER_SANITIZE_SPECIAL_CHARS or something alike to it.

This was the expected change at the time, but forgot that special characters may show up in Session variables (among other variables)

So say an & would get created, well FILTER_SANITIZE_SPECIAL_CHARS would encode & to & which would then see the & again and perform the same trick over and over and over in a recursive loop.

This is what was causing the CPU spikes, my apologies for that oversite. This has been addressed within the latest dev-branch if anyone would like to kick the tires?

Thank you!

Is everyone having this particular problem consistently using the LDAP plugin by chance?

@rogalskij I don’t know OS:

PHP error logs
/var/log/php-fpm/www-error.log (redhat based)
/var/log/apache2/error.log (debian based)

SQL:
SELECT * FROM history;

I doubt the sql will be of much help, but anything is better than nothing.

Most of the logs I’ve gotten this far don’t appear to have anything and maybe none of them do, in which case I don’t know when the issue was directly introduced.

If anyone is able to bisect known good and the obvious current as the starting bad to figure out when it got introduced?

I’m assuming we’ve all tried reverting to the first known good and verified it is still “good” as well?

Basically if someone doens’t mind taking where they know they’re broken, and iterating back to when it works great to exactly when it fails, it may help us figure out where to start otherwise I’m currently flying blind.

@rogalskij The number in front of all hosts (and groups/snapins/images/etc…) is the Database ID of the object in question, that’s expected.

I’m trying to follow what caused this and I’m having a difficult time reproducing it.

Can you all edit /var/www/fog/lib/db/pdodb.class.php at line -> 125:

change:

PDO::ATTR_EMULATE_PREPARES => false,

to:

PDO::ATTR_EMULATE_PREPARES => true,

I’m pretty sure this is going to break other things, but it will give me a data point I’m trying to narrow down.

Can you get some output from /var/log/php-fpm/www-error.log (if redhat based?) or /var/log/apache2/error.log (if debian)

Basically try to load the page, and tail the log and return that output here for htat rough timestamp.

Also see if there’s anything in the history table:

SELECT * from fog.history;

For around that time frame.