@sebastian-roth It did not help. It still got stuck there. I think it was a version issue with the .fogsettings between 1.5.2 (old) and 1.5.9 (new) and the difference in Linux Distro. I will just move images and other settings and recreate the cert. Thanks for the help!

@aaron-nolet said in PXE boot BItdefender Rescue CD fails:

@jd272 Any chance on getting some clearer step by step doc on the procedure?

Looking into this, it looks like its possible to go boot it via pxe. I should be able to add the instructions to my tutorial. I don’t plan on testing this myself, but if you would want to verify my tutorial I think I can give you what you need to get started.

https://forums.fogproject.org/post/143187

@sebastian-roth UPDATE
I ran 1.4.4 installer
then ran 1.5.5 installer
then ran 1.5.9 installer
and everything worked fine this time it asked me to set a password for MySql this time

@jyost said in Old MAC's retained after being changed in web interface:

FOG 1.58

We don’t have a team of developers to backport fixes so this needs to be verified an issue in the latest dev-branch version. We won’t be able to help you with a fix for 1.5.8.

With that said we can still see if this is really a bug or just a missunderstanding. From what I remember when you change a MAC address it will add the old one as a secondary MAC to that Host. And I think there was a bug in 1.5.8 web UI that did not show the secondary MACs (were somehow hidden). Please see if that’s the case.

@adriand said in Export CSV columns details and Import issues:

Seems good, but when I click on a host, I can’t access it, it gave me “No result found”

While I find it strange that you get back to the host search view when clicking a host I can imagine what’s wrong. Have not tested but in the picture we see TEST 1 as hostname with a space in the name. While the web UI would prevent you from creating hosts with a space character in the name the import seems to allow that (bug or feature 😉 ). I guess that would account for the behavior you see.

Which version of FOG do you use? 1.5.9 I would imagine!?

@sebastian-roth said in Fog http wrong:

port fast

Thank you! I jumped in the switch and enabled port fast and that has taken care of the problem. Thank you for all your help!

@lsdo I may also ask you to open a new topic and post your own details there!

You might also read this topic, possibly answers your question as well: https://forums.fogproject.org/topic/15025/move-partitions-on-gpt-layouts-need-people-to-test

@pierrer What error do you see? If you can take a clear picture of the error with a mobile phone and upload the image here. This will let us see the context of the error.

@zaccx32 said in All hosts deleted/not showing in host list/groups:

After cleaning that up, a few hosts showed up but most are still missing and our images are not showing up in the GUI either.

While disk space is an important thing and 99% seems a lot in first sight, I don’t think this was causing the issue here. Why? Because we see you have a large disk with still 31 GB shown as free. I find it very strange that you see some hosts now. From the SHOW DATABASES; output you posted I would have guessed the fog DB is fully corrupted now and needs recovery (keeping my fingers crossed it’s still possible).

Also, when trying to access the fog DB today, is cannot be found any more, almost like it is gone.

Now we really need to figure out what’s going wrong with the DB. First of all let us take a look a the DB files on disk, the real basis: ls -al /var/lib/mysql (post a picture here)

As well stop the DB and take a file backup. Then start it up again and check the log:

service mysqld stop cd /root mkdir backup rsync -av /var/lib/mysql backup service mysqld start tail -n 30 /var/log/my*

Post a picture of the output from the last command as well. I really hope I got all the commands right for your pretty dated CentOS 6.9 install.

@rodluz said in HostnameChanger Issue:

Would anything break if I run UPDATE hosts SET hostEnforce=‘1’; to update all hosts in one blow?

No, that shouldn’t break anything. I reckon it’s save to do - if you really want this.

@aloniada Playing with this today I figured out what changed in (U/Ku/Lu)buntu and Mint from 20.04 (or maybe earlier) that causes the mentioned error Unable to find a live file system on the network even if you add the ip= parameter (which you definitely have to!)…

You need to copy the hidden folder .disk from the ISO as well which is missed when using the copy command. See more details here: https://forums.fogproject.org/topic/14590/20-04-autoinstall

But be aware that in your case you need to get the ip= parameter right first so the NFS over TCP not available ... error goes away!

this is a VM from the server itself so no way it’s network issue

I also ran into an issue where ip=dhcp did not work in a VM setup. I actually had to set a static IP - which really is a shame!!! So instead of ip=dhcp this worked for me:

... ip=192.168.3.123::192.168.3.1:255.255.255.0:hostname:enp0s3:none:192.168.3.1 ...

@sebastian-roth this has worked for me with a brand new HP 440 G8

@lcsmd Thank you for reporting back on how to get it working. When adding it to the wiki I figured out it uses the “ASIX AX88179” chip and we had some of the Startech devices listed in the “Notes” column already. So I added your USB31000SPTB to that list as well to be found by others - including the hint to use a different iPXE binary.

I have to say the list is not really up to date. Mainly the notes are not because it’s a lot of work to keep it up with information from forum posts only. Nor do we have time and resources to test all the hardware ourselves.

@george1421 : Right !

I removed all offending spaces and voilà !

Thank you very much .

PS : By the way i noticed the error also occurs when i select multiple entries as : default item.

@ice4192 Like this?
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@SomeWeirdRandomDude Please post the full fog.log from that client here.

By the way, which version of FOG and the fog-client do you use?

@john3892 As you see your version of FOG is way newer than the one of the original post here, so please open a new topic and post all your details there.

@sebastian-roth Ahh, I didn’t see that either. Okay, so in DHCP I changed the router to 192.168.22.1 and range starting IP to .20

In fogsettings, I changed both routeraddress and plain router from 192.168.22.11 to 22.1

The test client gets online just fine now.

Thank you again, Sebastian!