@Sebastian-Roth Thank you very much! I tested it and it worked!

Hello

I do not understand …

I have this problem but I find the plugin rental customers?

Thank you

@amc123 If this is a relatively fresh install of FOG I’d start from scratch (really by re-installing the OS).

Then use the latest version from github dev-branch which has the fix for VSFTPd on Fedora 30 already.

I noticed that the fog version after the upgrade was not showing:

alt text

After I manually changed the fogstorage password in MySQL the versions started populating for the storage nodes that were upgraded but not for the storage nodes that were not upgraded.
is it possible that the upgrade corrupted the fogstorage MySQL password in the database on upgade or was it the mysql dump that was generated by Configuration Save> Export Database in the fog gui?

The more I think about it it would have to be the MySQL dump… I installed fog on a new Centos 8 build and imported the database after installing fog.

snapins are now downloading with the correct file sizes.

Thank you everyone for helping me with this issue!

@markbam Are you good with network analyzing using tcpdump/wireshark? If you are keen to give it a try let and need help just let us know.

@dotlightyear Please provide more information as requested. Otherwise we can’t help you.

@cbrherms It’s been a long time… sorry! Finally found the time to set this test case up myself but I can’t replicate the issue as described. In my setup it deploys from the right storage node if a host is set to be at that location. Both doing single deploy as well as group deploy. If I create a group with two hosts, one at each location and deploy to that group they both pull the image from the correct server (one from master and one from storage node).

Tested on dev-branch as this is the version we currently work on. So either I got things wrong or this issue is not existing in the latest version (anymore). I’ll mark this topic solved until someone else comes along and is able to replicate the problem.

@roseward Ok so we are going between models of computers. Also when you removed the network adapter and rediscovered it it still fails. So at this point I’m thinking windows driver. Because the same driver would be reinstalled. The network adapter is functional because you were able to image with FOG, so the hardware and network infrastructure probably can be ruled out on this issue.

So on this computer what network adapter is installed (version reported by windows)? Also get the vendor and hardware ID from the driver applet.

Also note the driver author and version (i.e. GigaByte Brix i7 LOM driver).

You may need to load a model specific driver because the one that windows detected may be close but not exact.

@blacksmile said in Failed to get an IP via DHCP:

I’m using FOG 1.4.4 on an isolated lan.
Any idea?

While I also recommend that you update fog to 1.5.7, if you can’t for whatever reason then at least update the FOS Linux kernel to 4.12.3 if your target computer has an Intel i219 style network adapter. You can get them from here: https://fogproject.org/kernels/

@tech49 said in Full Registration glitch, cannot type hostname for this computer.:

When I try to do a quick host registration and then select the host and prenamed image to be captured.

Registration allows deployment of an image, not capture.

For capture, issue a capture task for the now registered host in the WebUI.

@tech49 Please make a new thread for the new issue so we can help you there. (since it’s unrelated to the thread)

@Sebastian-Roth said in Fog installation and cofiguration on ubuntu 18.04:

You are welcome to open new topics for each question you have. It’s way easier for others having similar or same problems to find the right answer in a short topic instead of half a dozen questions being packed in one thread.

thanks,

I agree, i will start a seperate thread to update on any progress on this topic.

@processor In this case I’d ask you to update to the latest development version. There is a minor issue with 1.5.7 on Ubuntu and it’s better you use the latest version in case we still need to work on fixing the multicast issue.

sudo -i apt-get update apt-get install git git clone https://github.com/FOGProject/fogproject cd fogproject git checkout dev-branch cd bin ./installfog.sh

@lperoma The grep error can be ignored.

@EduardoTSeoane said in Common WebUI pages takes minutes to load.:

Ok, I’m ready to start the test, plz explain me how do you want the, bugs/problems report?

Just report here in the forums as you did before. Or if you are keen you could also post an issue on github. Whichever suites you best.

Knowing that my FOG server is in place, I mounted a drive to a nas in the / etc / fstab file.

8f9204b0-dd57-4792-ac3d-9ba399365321-image.png

it does not work … how to deport my storage without reinstalling FOG
thanks

@Pablo For your FOG server to get to the internet is a web proxy server required or does the fog server have direct internet access?

You can also use a windows computer and download these two files:
https://fogproject.org/kernels/Kernel.TomElliott.4.9.4.64
https://fogproject.org/kernels/Kernel.TomElliott.4.9.4.32

After download rename Kernel.TomElliott.4.9.4.64 to bzImage and Kernel.TomElliott.4.9.4.32 to bzImage32 Make sure you use the exact capitalization I used. Then move these files to the FOG server into the /var/www/html/fog/service/ipxe directory.

@Quazz
Thank you for your answer, I did not know that deployed partitions were prorated to captured partitions.
It’s clear for me now

@boomtown said in Interactive PXE Boot setting?:

Is it possible to require a key be pressed before the PXE image will boot so that if nothing is pressed the computer will go to the next device in the boot priority?

Unless I’m missing something here, this is the default. In the iPXE menu the default menu item is boot to the hard drive. If you don’t touch the keyboard during the timeout period the system will select the default menu item and boot the hard drive. You can change what the default iPXE menu item is, but as shipped from the developers, its the boot to hard drive menu.

Now if your target systems are Dells (only system I have) you can use the command and configure utility (i.e. CCTK) to change firmware settings. So you can from a running windows system change the boot order by calling cctk with the proper command line parameters.

@TBuzaTechnician Just a quick update here. I finally found the time to work on this. Currently we have a major set of changes regarding database security in a testing stage. Looks pretty good so far and it will all be part of the next release.