spanning tree, spanning tree la la la la la (jingle bells)
I’m saying this from 2 months 😄
I’m glad to read you saying it ^^

@lacaca Again, please post a picture of the error. We can’t help you otherwise.

Thanks @Sebastian-Roth

We did a remote session. Turned out there was an old fog-client installed on all the machines and for some reason the hosts kept on downloading and trying to install the new fog-client version from the server consuming a lot of traffic on the VPN link. Possibly some security software was preventing the installation though.

@george1421 Ah, i see. I was doing it with rsync in a cron job at the moment. I’ll try out your suggestion. Thanks for the info. 🙂

@Sebastian-Roth Yep! That fixed it!

Thank you.

Andrei

@foguser said in Client doesn't boot from FOG:

When i bootet it again, it did not care again and just downloaded the citrix nbp-file.

This is why I need to see the pcap file, not a picture of it but the actual file so I can peek at its bits. I need to see who is telling what to load.

opened up all ports on the fog server, to make sure nothing is blocked, but i was again only seeing dhcp requests and discoveries. Not to my surprise because the client does, as mentioned above, never try to boot from there.

The fog server is not in the picture at the moment. Right now the actors are the pxe booting computer and what ever dhcp servers respond to the target computer. FOG comes into play as soon as the target computer asks for the boot file pointed to by dhcp option 67. Your focus needs to be capturing what dhcp server is telling the client. That will be in the pcap. I only care (read want to see) the dhcp packets that is why I recommended using the capture filter of port 67 and port 68

@krejci said in Intel RST RAID volumes - missing drives:

When boot in debug mode and cat /proc/mdstat - nothing, also lsblk and blkid shows nothing.

This is interesting. lsblk should show the individual drives even if it can’t see the raid. The intel rst “fake raid” (should be properly called hardware assisted software raid) adds an abstraction layer between the physical disks and the OS (FOS in this case) to create the virtual raid disk. If these were standard drives in UEFI mode and this was a dell computer I would say changed the disk mode from “raid-on” to ahci mode. But in this case you kind of need raid-on mode.

Is this a dell computer? Does it have a bios mode? It would be interesting to see if FOS can see the raid disks in BIOS mode.

@martial The fog-client mostly fails with Middleware::Response Invalid security token. From that I see in our code this can only happen if there is a security token set in the DB for this host (identified via MAC address but it’s always the same as you re-use the same adapter over and over).

Well let’s see if we can figure this out in the DB:

shell> mysql -u root -p Password: ... mysql> use fog; ... mysql> SELECT h.hostID,h.hostName,h.hostSecToken,m.hmMAC,m.hmPrimary,m.hmPending FROM hosts h JOIN hostMAC m ON h.hostID=m.hmHostID AND m.hmMAC LIKE '%aa:bb:cc:dd:ee:ff%'; ...

Use the USB nic adapter MAC address instead of aa:bb:cc:dd:ee:ff. See if you get any results.

@Sebastian-Roth This is exactly what it was. I feel a little embarrassed haha. Thank you for your help

@xburnerx00 The fog-client is running as a service (system account). It’s probably not able to write into a users home (Desktop) directory. Try using something like C:\Temp and make sure that is writeable for everone…

@Sebastian-Roth
Ok, Thank you for the help. I will have to research snapins some more. It seems the issue for this post has been resolved. So I will mark that post as the answer. If I have anymore problems I will make a new post.

@thomasg07 What Linux OS (version) did you try to install FOG on? Your PHP version seems to be way to old (5.4.45) and causes the problem.

oh ok thanks 🙂

Thank you so much, with the new / old inits the capture process ran successfully. Am trying to deploy now and see if everythin works out.

Thanks for your help
Sébastien

Thank you all; you have answered my questions! I have about five images I use most of the time. I do believe your suggestion to deploy from FOG and then capture using CZ would be my best option! And thank you for helping me understand the fundamental differences between FOG and CZ!

Hi again.

Today I need to install some HP Prodesk 400 G4 😄
And the problem come back in both mod (uefi and legacy) I try to check for a Bios update, and I done it but the problem steal here.

I already try with a old no managed dumb switch.

In my case I make a upgrade from 1.4.4 to 1.5.5 it was working like a charm with the 1.4.4. Now I have this problem with the 1.5.5.

Any idea ?

@Almeida Free disk size? df -h?

Anything you see in the apache error logs (see my signature)?

@Tom-Elliott said in Check in Failed There are 0 Before Me (In line for XX:XX):

@Ginto what about max clients for the storage node itself?

It is set to 10.

I was able to bypass this error just now by going to my active tasks and force starting it. I would still like to fix this.

Here are a couple of ideas.
Make sure the geometry of file.png matches (exactly) the geometry and color depth of bg.png. Also if I remember correctly size does matter. There is a maximum total byte count of this background image.

Secondly some uefi firmware can’t / doesn’t display background images. There is nothing you can do it make it work, its flaky uefi firmware.

As for the uefi boot manager. Yes I’ve seen that myself. I think one of the developers was going to look into that issue. I don’t know if the fix will be in 1.5.6 or 1.5.7 if they can work it out. One of the issues we’ve seen is some people want windows to be the first boot option after imaging and other want to keep what ever boot order they currently have and not have FOG change the boot order.