I think I see part of the problem. I was expecting the snapins to be attached to the group, but looking at this code in group.class.php, it appears that the snapins just get attached to each MEMBER of the group:

public function addSnapin($addArray)
{
    $insert_fields = array('hostID', 'snapinID');
    $insert_values = array();
    $hosts = $this->get('hosts');
    if (count($hosts) > 0) {
        array_walk(
            $hosts,
            function (
                &$hostID,
                $index
            ) use (
                &$insert_values,
                $addArray
            ) {
                foreach ($addArray as $snapinID) {
                    $insert_values[] = array($hostID, $snapinID);
                }
            }
        );
    }

I snooped around by adding some syslog messages, and it does seem that the foreach loop above is what’s invoked when I try to add a snapin to a group.

Is that what should happen? Is this possibly something that is different in the newer version of fog?

@sebastian-roth
The fog version is 1.5.5, and we only use one storage node. When I try to add a “single snapin” task, I see:

Please select the snapin you want to install
No items found

I’m finding that I can add snapins to individual hosts with no problem, but when I try to add a snapin to a group, nothing happens. In the group’s snapin configuration I select the snapin from the list of available snapins and then click “Add”. A popup says “Group Update Success / Group updated”. But the snapin is still not available to be used by this group (for example, under Basic Tasks --> Advanced --> Single Snapin).

How should I go about debugging this?

@bryan-wright
I’ll open a new topic on the forum about this, but the problem I’m running into now is that we have some kernel arguments set under “general settings” that we use for all clients. These are “pci=nomsi acpi=off”. But these settings won’t work with the recently problematic machines. For those I’d like to just have “acpi=noirq”. It looks like the per-host kernel arguments get concatenated onto the global ones, though.

In any case, temporarily setting the global kernel args to “acpi=noirq” allows me to image the currently problematic machines.

@george1421 @Sebastian-Roth
Aha! The magic seems to be “acpi=noirq”. Now I just need to figure out how to get fog to apply that to only this subset of machines…

@george1421
Yes, that was one of the first things we tried. The firmware is the latest available.

@sebastian-roth
This is fog 1.5.5. I’ve just now tried downloading and booting the 5.10.34 kernel, but it behaves the same (“probably buggy mp”).

I suspect the solution will involve some combination of acpi and apic flags on the kernel. I’ve tried a few, but haven’t found the right mix yet.

@sebastian-roth
OK, with the kernel log level cranked up to 7, I see the same error message that tiny core shows me “Can’t find IRQ for PCI INT A…”. Here’s photo of the screen after it hangs:

We have several teaching labs full of computers that we’ve been using Fog with for many years (thanks!), but we recently got a batch of Dell Optiplex 9030 computers, and they’re refusing to pxe boot. They hang right after:

bzImage… ok
init.xz… ok

We’ve been using undionly.kpxe for the machines, but I’ve tried switching to ipxe.kpxe and intel.kpxe with the same results. I’ve also tried downloading the latest versions of these, but it still didn’t work.

I notice that the screen flashes momentarily after init.xz, as though it’s trying to do something else, but nothing ever happens. The only log entries I see on the server look like this:

Jun 28 13:28:38 mrwizard-apn dhcpd: DHCPREQUEST for 192.168.104.56 (192.168.104.
2) from 74:e6:e2:e1:ab:1f via eth1
Jun 28 13:28:38 mrwizard-apn dhcpd: DHCPACK on 192.168.104.56 to 74:e6:e2:e1:ab:
1f via eth1
Jun 28 13:28:38 mrwizard-apn in.tftpd[2015]: Error code 0: TFTP Aborted
Jun 28 13:28:38 mrwizard-apn in.tftpd[2016]: Client 192.168.104.56 finished intel.kpxe

Notice the “TFTP Aborted” message. I’ve tried fiddling with the tftp block size, but that doesn’t seem to have any affect either.

I’d appreciate any advice anyone has to offer.

UPDATE:
I tried booting 64-bit tiny core linux from a USB stick on this computer, and it also hangs. In this case, it stops after “Can’t find IRQ for PCI INT A; probably buggy MP table”.

Hi folks,
The following URLs aren’t answering:

http://www.fogproject.org/globalusers/
and
http://www.fogproject.org/version/version.php

These are used to display information below the fog login box.

Bryan