Of note, I’m calling it 1.6 because when we do release it, that’s what this will become.

It is using the current latest version (1.5.7) and the .XXX after is the number of commits ahead of the master branch the working-1.6 branch is at.

@franck25 said in How to boot uefi on ltsp server via ipxe fog:

I find myself facing a problem of boot on my server “ltsp ubuntu”

Please take a picture of the screen where we see what goes wrong and post that here.

@sudburr In my FOG installation (1.5.5), the value for DATABASE_PASSWORD in config.class.php is in single quotes, so the sed statement for needs to be:

sed -i.bak 's|DATABASE_PASSWORD', '<oldpassword>'|DATABASE_PASSWORD', '<newpassword>')|g' /var/www/html/fog/lib/fog/config.class.php

I would also like to note that the values in .fogsettings are only initial values for during installation. So it does not matter if you patch the password there really (not 100% sure though).

@WalterT Good to hear you could fix this issue on your own. Too bad that we don’t have any information from you about how the password was, when ich caused an issue! How can we improve this if we don’t have any informaiton on what exactly went wrong?!

@Tom-Elliott Possibly it’s the \ but I am not sure. We already changed the password generation method in dev-branchand therefore this won’t be an issue from the next release on.

@Sebastian-Roth : I fixed it. I needed to do run su - and that fixed the Path variable that is not set properly. Fog is now installed correctly and the useradd worked great. This is the page that I found that lead me to the fix.
https://linuxconfig.org/command-not-found-missing-path-to-sbin-on-debian-gnu-linux

Thanks again for your help.

I look at it and come back to you thank you

@egorhan Must have been blind when I looked at this the first time. Now I see something that makes me wonder.
Search Base DN: ou=administrators,ou=pm_users,dc=parimatch,dc=local
Bind DN: cn=administrator,ou=pm_users,ou=administrator,dc=parimatch,dc=local

The OU pm_users seems to be on different levels of your LDAP tree. That doesn’t make sense to me. Please double and triple check all the settings. Better you copy & paste the settings from some LDAP browser tool instead of typing those in.

@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