@dylan123 Reading a bit more about the apparmor stuff I found this: https://stackoverflow.com/a/49583958

I read in another SO thread comment that the apparmor=“DENIED” message probably isn’t the reason that MySQL (or in my case MariaDB) wasn’t starting, as it’s only a warning.

Confirmed by this bug report:

On the affected system, there was no noticeable impact (yet?) other than the denials, so I’d say it’s low impact.

Spinning up a VM with Ubuntu 18.04 I saw that quite true it has those log messages in /var/log/syslog on my VM as well but the DB is running perfectly fine. So just for the records: Those apparmor=“DENIED” message don’t cause an impact on the DB and can be ignored.

Check all the information George and Daniel posted as well as my suggestion on the mysql logs.

Thanks guys! You all have been so helpful. I figured out that you don’t have to select the FOG Boot screen to select the Hard drive boot. It goes right into pxe.

It’s cut our deploy time from an 1 hour and 15 - 30 minutes to like 10 minutes.

If it becomes a further issue I’ll keep the post deploy scripts in mind.

Thanks again!

Found them, yes transferring them worked but also resetting encryption data also worked.

@george1421 I believe at one point it was suggested to use SSH to handle interactions with the server instead of ftp/nfs (one or both, don’t remember)

Though I imagine that’s further down the line.

@Sebastian-Roth This is more by design.

Typically snapins are one time run. If needed to rerun a while later, you can run it individually to the host needed, or you could task the host to run all snapins associated.

Maybe something we can limit in the future, but I guess I need better understanding.

Snapins run in queue.

For example, if a host has 25 Snapins to install, it installs 1, 2, 3, etc… It will not install 25 at once.

Now, based on the information, I believe the question here is about number of machines running snapins at once. Lets say you have 25 Machines to install Snapin 1, you want this to be limited?

Right now the code doesn’t take into consideration the number of snapin tasks as a queued process.

Hopefully this all makes sense.

Thank you,

@Trev-lchs Did you ever solve this? I just stumbled upon this issue report which we got years ago: https://github.com/FOGProject/fog-client/issues/72

@sudburr Ok, I tested and updated my version of the script below (derived from yours).

Again, make sure you have backups of your /images and the certificate files before you run this script!! I won’t be responsible for any trouble caused by this script!

I found and believe I may have fixed the issue. It was actually pretty simple. The error was coming from the unpacking of information.

Hopefully it helps. Just repull the dev-branch and install and all should be back to normal.

@Sebastian-Roth Thank you for finding and fixing the issue.
@Greg-Plamondon Thanks for reporting. This fix is also set for 1.6 now too.

Awesome job everybody!

Thank you,

@masoudmahamid Please run this on the command line and post output here: ls -al /images/dev

@dario-vettore Did you get this solved?

@brakcounty Any news on this?

@andrewhancock91 Are you still keen to discuss this?

@f-an Is this still an issue or did you solve it?

@brakcounty To get some more information, can you please schedule a debug deploy task (same as you would do a normal deploy task but just before you hit the last button in the web UI there is a check box for debug). Boot up the client as usual and let it boot up. Then you need to hit ENTER twice to get to the shell. Now type fog and ENTER again to start and step through all the process till you hit the error. It will throw you back to the shell. Now type:

sgdisk -gl /images/Win10Standard_GPT_EFI/d1.mbr /dev/sda

It surely will fail. Take a picture of the screen and post that here.

@brakcounty said in customizations to ipxe menu not applying after updating to 1.5.7:

One question though, from the main FOG ipxe menu, when i hit Deploy Image, and get the prompt to authenticate with fog/pass, that text is blue, i want it to be white. Where can i change that setting?

In my test environment if I change the iPXE main colors (FOG Configuration -> FOG Settings -> FOG Boot Settings -> IPXE MAIN COLOURS) this is valid for all the text in the iPXE boot screens as well as for the password entry.

@george1421 That is because the separate storage group has a master. It’s a “work around” to the “Images are always captured to the master node” because you, quite literally, are making the storage node, now, a master node. It works of course for this reason.

@madeyem said in FOG and UEFI/M.2 SSD:

Is it really necessary for you to have the PC run in raid on mode? If not, leave it at AHCI

If you have only a single disk in the computer OR you have multiple disks but have no plans on setting up a raid configuration there is no performance penalty to leave the disk controller in ahci mode.

@Brad-Schumann The short answer is it depends on what the laptop is doing. The bit longer answer is the config file for refind is in /var/www/html/service/ipxe and its called refind.conf.

Also make sure the firmware is up to date on this laptop because it could be flaky firmware that is causing refind to fail.

The last option is we may need to look into updating refind to a later version because the hardware drivers in refind may need updating.

So in the end it depends…

@Quazz Thanks, done: https://github.com/FOGProject/fos/issues/31