Posts made by Frode Woldsund

Hi @Tom-Elliott,
That might just be the solution. Not sure why, but I had the perception that having a db with no password was the recomanded way. Again, thanks for helping me out and for developing and giving support to this fantastic tool!

@Sebastian-Roth Thanks, It is much possible that this is due to unattended upgrades. I’ll have a look at the forum tread you posted and also check our configuration files. But as @Wayne-Workman said, switching to debian might just solve this more permanent.

@Wayne-Workman Thanks, I will surly try using debian as our default setup, if that is a more recomanded OS for the fog project.

Server

• FOG Version: 1.4.0
• OS: Ubuntu Server 16.04

Client

• Service Version: N/A
• OS: Win 10 Pro 64bit

Description

Hi,

We have a recurring issue where fog stops working and the webportal shows a database error message. All computers that are started after this point will go into a boot loop.

The workaround is to reset the mysql password with the following command.
ALTER USER ‘root’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘’;

We have tested fog project version 1.3.0, 1.4.0 with ubuntu server 16.04.
During installation we used the following command: sudo php_ver=‘7.0’ php_verAdds=‘-7.0’ ./installfog.sh -y

Is this a problem the fogproject is aware of, or have we done something completely wrong in our setup.

The mysql password we use is blank, would that be a problem?

Please let me know what other information I need to provide to find a solution for this problem, or if there are anything you want me to test. I do not have a way to reproduce the issue other than waiting for it to happen again, which is usually once a month on one of our servers.

Hi,

We have problems that the FOG Client does not change the hostname on a computer running windows 10.
Is there any special settings we need to add to the installation, or is this functionality simply not working on win10?

We run FOG server: 1.2.0
Windows 10 Pro 64bit

Best Regards,
Frode Woldsund
Offshore Simulator Centre AS

… And now nothing makes sense anymore …

1. I removed everything from the Advanced menu and rebooted my computer
2. The PXE_Boot_Menu still freezes.

I think it is time to try reinstalling FOG on another clean ubuntu and start from scratch again.
I was 100% sure I registered all computers using PXE_Boot_Menu, but now I am only 90%…

I am really sorry if I have been wasting your time with false information about the initial setup.
Let me try to start from scratch, and I will inform you guys about the initial status of the R5400 computer.

It might that I explain my problem completely wrong: So I will try to create a more step by step way to reproduce this issue I have:

1. I have installed Fog 1.2.0 on a clean ubuntu server 15.04 in a XENSERVER environment. (Which we always do, and that always works fine on all or computers)
2. We login to “fog web-interface” and change our default password but else everything if left to default
3. Then we are able to register all our computers using the “PXE_boot_menu”
4. We can create images and upload/deploy them from the “fog web-interface”, or manually start jobs from the PXE_boot_menu when register new computer
   All our computer including the R5400 does work perfectly until this point
5. Then we want to add extra ISO files like a clean Windows7DVD to the ubuntu server, and we want to activate the “Advanced boot menu” from the “fog web-interface”

• http://serverIP/fog/ -> Fog Configuration -> PXE Boot Menu -> Advanced Configuration Options -> and add something like this

initrd ${boot-url}/service/ipxe/winpe_amd64.iso
chain memdisk iso raw
prompt
autoboot

6. When I now boot any computer(except my troublesome “DELL Precision R5400”) into PXE I still get the normal PXE_boot_menu, but with the additional “Advanced Menu” in the bottom of the list. And if I select it, it will boot from my Windows ISO file.
7. When I now boot my “DELL Precision R5400” into PXE I still get the normal PXE_boot_menu, with the additional “Advanced Menu” in the bottom of the list. But if i press any key at this point, it will freeze. However if I do not press any key, it will boot as normal to my primary harddrive. (or if a task is active, it will skip the menu and go straight to the job, as inteded)

So what is loading the menu, is that the undionly.xxx file, or is that a part of the kernel?

• I have now tested unionly.kpxe, unionly.kkpxe, unionly.kkkpxe and a number of random kernels without anything helped so far.

Also the Troubleshoot_TFTP seems to be to get TFTP working, but as I said all other computers are working fine, and also the R5400 is working fine except if you navigate in the PXE_boot_menu with the R5400 computer.

Thanks for the help so far. Let me know if there is any way I can read our any debug messages from the PXE_boot_menu or if there are any logfiles available to help resolving this issue.

Yes you are correct: I am using 1.2.0 and “undionly.kpxe”
But no changes when trying to load the “undionly.kkpxe”

Hi,
I have multiple computers working perfectly with FOG. Then I have started using the “Advanced_boot_menu” option to make it possible for me to PXE boot into any of my installation iso files. I have got everything up and working except that one of my computer type “Dell Precision R5400” freezes if you press any key in the “boot_menu”. However if you do not touch any key it work as normal. (booting to harddrive, or uploading/deploying images )

I have tried to use other random fog kernel’s without any success. Is there anyone else that have experience this issue? Is there any crash logs available when the computer freezes in the boot_menu?

[quote=“updog, post: 26654, member: 20326”]Hi all,

If anyone has interest in putting this app in a docker container, I can help you do it. I don’t know if I have the time to create a wiki entry, but I can certainly give help.[/quote]

Hi, I created a thread for a docker container. Have a look at [url]http://fogproject.org/forum/threads/create-a-docker-container.12747/[/url]

Hi Jimmyboy, regarding the docker container you mentioned: Could you please have a look at [url]http://fogproject.org/forum/threads/create-a-docker-container.12747?[/url]

Hi all,
I just wanted to start a thread for discussing how to wrap fogproject into a docker container.
I have found just 1 docker container out there, but project seems to be dead: [url]https://registry.hub.docker.com/u/lspiehler/fogproject/[/url]

Is anyone else then me interested in getting a official fogproject docker container?
I’m not a docker guru, but I happy to help and test and hack on a docker project.

Oh, sorry… Thanks to you also Junkhacker
I did not notice that someone else was replying

Hi again Tom,
Thanks for helping me out!
It worked perfectly!

Thanks for quick feedback Tom,
Sorry, but it still not work
I see that the 2 files are downloaded, but after that it just continue to “goto MENU”. Instead of just booting into coreOS image

I would like to deploy a clean CoreOS iso to my new machines using the Advanced PXE boot menu in FOG.
I have found this wiki page:
[url]http://www.fogproject.org/wiki/index.php/Advanced_Boot_Menu_Configuration_options[/url]

Can someone help me boot a *.cpio.gz file instead of *.iso file?

:CoreOS
set base-url [url]http://stable.release.core-os.net/amd64-usr/367.1.0[/url]
kernel ${base-url}/coreos_production_pxe.vmlinuz
initrd ${base-url}/coreos_production_pxe_image.cpio.gz cloud-config-url=[url]http://example.com/pxe-cloud-config.yml[/url]
[[[ SOME FANCY CODE HERE TO ACTUALLY LOAD THE OS??! ]]] ||
goto MENU

— from CoreOS documentation—
This is an example pxelinux.cfg file that assumes CoreOS is the only option. You should be able to copy this verbatim into /var/lib/tftpboot/pxelinux.cfg/default after providing a cloud-config URL:
default coreos prompt 1 timeout 15 display boot.msg label coreos menu default kernel coreos_production_pxe.vmlinuz append initrd=coreos_production_pxe_image.cpio.gz cloud-config-url=[url]http://example.com/pxe-cloud-config.yml[/url]

[quote=“Saleme, post: 36175, member: 25731”]The results are in:
After reinstallation, I was able to get the client installed, after I installed -net framework. But there was a problem when I was going to upload an Image to the server:

FOG Image settings:
Storage Group: Default
Operating system: Windows 7
Image Type: Multiple Partition Image - Single Disk (Not Rezisable)

First imaging test:
Default Dell setup with nothing done to the harddrive. All partitions are intact.
Result: FOG completed the upload

Seccond Imaging test:
Our Windows image through work.
Installed with only one partition (plus the extra windows recovery partition of 100MB).
(The client was correctly installed).
Result: Failed! (Stopped on selection of harddrive …/sda something,something…

What could possibly be different between the two installations?
On the dell image, the OS are Win8, but we cannot use that OS.[/quote]

We finaly found a solution to our problem:
[url]http://fogproject.org/forum/threads/stuck-on-dev-sda.11105/[/url]

In Summary
Step 1: WebGui: Basic tasks -> Advanced tasks -> Upload - Debug
Step 2: run “fixparts” in the command prompt and type in “/dev/sda”(my harddisk) “y”(confirm) “w”(write mbr)
Step 3: Shutdown computer
Step 4: WebGui: Basic tasks -> Upload
Step 5: Restart pc and watch the magic happand

Hope this will help any other with same problem.
And to you developers; Isn’t this something that automaticly could be detected by FOG, and user could be prompted to delete the “GPT” stuff?