Best posts made by george1421

@taspharel I guess you need to go back to your service provider and see if you can get a trending over time. What are they considering high cpu load?

The numbers you posted below are pretty low cpu usage. I understand that was only for a max 15 minute time from when you collected the data. You need to see if you can correlate the high cpu usage time the are saying to a specific action. For 200 nodes, it shouldn’t cause high CPU usage even during imaging.

There are two bits of information we probably should have for completeness.

1. How many vCPUs are allocated to the fog server VM
2. What version of FOG are you running. There WAS issues in the 1.3.x range of heavy CPU loading that was addressed in subsequent version of FOG.

@gabrielzeit said in UEFI: NBP downloaded successfully - then blackscreen:

Sadly USB boot is not suitable for my use case

You are not getting to the FOG iPXE menu, this is an iPXE issue or as I mentioned before your pxe booting is getting hijacked by that WDS suspicious server. Your firmware doesn’t really indicate what is wrong, it just reboots. So that’s not really helpful in debugging.

You could load ipxe onto a usb stick (yes I know you said that USB wasn’t an option) to see if ipxe will boot from the usb drive for testing. If it does then you know the problem is somewhere along the pxe booting chain and not ipxe itself.

I don’t have the pcap anymore, but looking over the thread, I see this WDS server is responding with a bios boot file (wdsnbp.com) that, if sent to the uefi computer, would cause a uefi computer to download it and just reboot. I wanted to see if the DHCP DISCOVER from the client was saying it was a uefi computer, and then this rouge dhcp server was responding with a bios boot loader. That would be strange but also cause the symptoms.

@fernando-gietz [Moderator’s note] Yes I want you to have your own thread on this. Your conditions may be different than the OPs. I’m going to fork this thread into a new one. To avoid polluting this thread with off-point discussions

Thread forked to here: https://forums.fogproject.org/topic/10890/fog-server-cpu-usage-100

@bob-henderson (Pssst… I had a peek at some of the ui improvements. All I can say is, awesome!! )

I guess I would have to ask you can you update to FOG 1.4.4?

Also lets collect some background information here

How many client computers are contacting this fog server?
What is your client check in time/interval?

@Trev-lchs said in FOG 1.5.10 officially released:

Hi all I know its very old, but, will 1.5.10 work ok on ubuntu 10.04.6 LTS Xenial Xerus

I hate to say this because I know we all need to run old stuff, but 10.04 reached end of support by ubuntu in 2015. I would bet that the ubuntu repos will not have all of the required prerequisites in their distribution needed for FOG 1.5.10. The installer should fail. BUT, if you are able to get FOG installed, it will run on that old of an operating system because uses all FOSS components.

For you, unless you have a really compelling case, you will be better off in the long run to install FOG on a current supported operating system and walk away from 10.04.

@jackiejack Right, I do have a tutorial for that already written up: https://forums.fogproject.org/topic/10450/adding-additional-image-storage-space-to-fog-server

Interesting… the first thought is to get a live boot linux distro and see what the real device is called. I would still think it would be /dev/sda something since its still … maybe not using the sata interface (just reread your post).

I was also thinking the trunk build had a debug mode where you could boot to a command prompt to inspect the devices. I know the live boot will work.

[Edit] Ok, if you boot into the fog menu then check system compatibility. Once in system compatibility select partition information. If that shows up blank then we will have to go the live linux route [/Edit]

@jacob-gallant OK new kernels won’t help at that point before the iPXE menu is displayed. I can help you get started with custom kernels but that effort won’t fix the issue.

Please follow this tutorial on compiling the latest version of iPXE.
https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe

@Arrowhead-IT I was just editing my previous post about using compatibility menu to get the info.

Now this is just me guessing out loud here (since I haven’t had this exact issue just yet). But if you look in the FOG GUI, and the host management details for this specific computer. Note there is a field called “Host Primary Disk”, it would be interesting to know if you entered /dev/nvme0n1 in that field, would it blow up (Err… work as intended)?

@Andrew-Single If your fog servers are behind a proxy server let me know there are a few steps you need to do to have a successful upgrade to the SVN trunk.

ok then, I think we’ll need one of the @Developers to look into the code to see if it is honoring the “Host Primary Disk” field when launching the partclone.

Lets flip this around a bit.

What version of fog are you on? The trunk build has a revision number in the cloud. What is that 4 digit number?

What device are you trying to uefi boot. Manufacturer and model.

The default uefi file I would start with is snponly.efi

Do you have a mix of bios and uefi systems you want to pxe boot? If you are also running 2012 dhcp server or a linux dhcp server there is some settings you can adjust to make your life a bit easier when trying to pxe boot both environments.

I think I would still go down the live boot path. Just get ubuntu 15 desktop iso and burn it to CD. Then boot from the CD, there is an option to try it first (or something like that). I would be interested to know what a production kernel reports. But /dev/nvme0 would be a sane name for that hard drive.

@atarone Unfortunately, with 2008 dhcp server you are out of luck. If you have a 2012 dhcp server you can follow the instructions found here: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

This guide does not work with 2008 dhcp server.

@Arrowhead-IT Hey, just wanted to let you know this is all great information. The more details the devs have the better solution they can come up with. Its impossible to have every bit of hardware in the test lab that exists in the wild. So it is key to get support from the user community to help build a better mousetrap.

@Wayne-Workman Most of the noobs would probably use an fog based distribution, especially if they are not that familiar with linux. I can see if someone was just trying it out and didn’t want to put a lot of effort into the software that they may not like. That is where a fog distribution (akin to freepbx distribution) would be a benefit.

The issue (as I see it) is that we don’t currently have enough people with the skill set to build and maintain a distribution as well as the installer based builds. The next issue would be what host OS do you select? Ubuntu or Centos? I know what I would select, but that doesn’t mean it is the best choice.

When you get into VMs some companies will allow externally created VMs and other won’t for the simple fact you don’t “really” know who built the VM and if they put some hidden back door into the software (the same could be said about a distribution or even the fog installer).

If it was up to me (and its not), I would rather devote the 2 or 3 developers that it would take to manage a VM or distribution and put that manpower to fog development.

Lets start with the basics.

What version of FOG are you using? (I’ll assume 1.2.0)

Are you running a trunk version? (if you look at the management page, there is a cloud in the upper left corner. There are numbers on the cloud, what are they?)

Is this a new FOG install or have you been using this successfully for a while?

Do you have any other client computers (older than the 3020) that do register correctly?

BTW: There is another thread in this forum with almost the same exact issue. But lets start with the basics first.

I can’t speak to the fog project, but in general many FOSS applications that are free to use, charge for the branding enabled options. And they typically stipulate that the FOSS application name and copyright information still appears (somewhere visibly) on the branded material, considering that the MSP is probably making some kind of profit from the setup of the FOSS software is only right that the MSP contribute some token back to the FOSS developers.

Lets get a little more info here

What version of fog are you using 1.2.0 stable or a trunk release (i.e. pre 1.3.0)?
Is this device in efi or bios mode? (I’m going to guess bios)
What version of the FOG (Fog OS) kernels are you using?
I can’t find a reference for a lenovo B700 on their web site, what is the real part number?