@quazz said in Fog/dnsmasq and EFI booting:

SecureBoot must be disabled for EFI

i…

That was it. I feel like an idiot! thank you!

@sebastian-roth Checked on the storage node that was giving issues and it done fine i am going to just move everything to new master SN and test

fog@Fog-Main-Storage:/images$ cp Win1064Bit4-15-21/d1p2.img test_extract.img.gz fog@Fog-Main-Storage:/images$ file test_extract.img.gz test_extract.img.gz: gzip compressed data, last modified: Thu Apr 15 12:45:14 2021, from Unix, original size modulo 2^32 3448112244 gzip compressed data, reserved method, ASCII, has CRC, extra field, has comment, encrypted, from FAT filesystem (MS-DOS, OS/2, NT), original size modulo 2^32 3448112244 fog@Fog-Main-Storage:/images$ gunzip test_extract.img.gz

@sebastian-roth
Yes one of the storage nodes is the master
But i am working on changing that as we speak and creating a new master 64bit then the others will be changed to 64 bit also

as of right now i have
server 64 bit 16.04 xubuntu not storage node
1 Ubuntu 16.04 32bit storage node master
1 Ubuntu 16.04 32bit storage node
1 ubuntu 20.04 64 bit storage node

I am going to just use the 64bit as master after i get the images all copied over, then disable the other 2 32 bit nodes, upgrade them to 64 bit and re-enable them to see if that fixes some of the issues i am having since the 1.5.9 upgrade

@sebastian-roth I resolved this issue by changing the boot file to ipxe.efi on my DHCP server scope configuration. Thank you!

@nerdstburns said in Reset fog dashboard login password:

I have tried the 1.5.0 steps on this page

So what was the outcome if trying this? Were you able to login to the database? What happens when you send the SQL query? Please provide more details on what exactly you tried and what happened and we should be able to help.

@Tom-Elliott
Dude, I was able to integrate the LDAP with the fog, now I need to manage the access levels, how can I do with LDAP enabled? I thank your previous answers.

Looks like @John-L-Clark has a huge setup with many hosts. Talked in chat and figured that increasing the value of php_admin_value[memory_limit] in /etc/php/7.4/fpm/pool.d/www.conf fixed the issue.

Possibly moving to InnoDB could help here as well. Though this is not supported in an official release yet. Take a look at those topics:
https://forums.fogproject.org/topic/15162/the-list-all-hosts-tab-takes-a-long-time
https://forums.fogproject.org/topic/14254/high-cpu-usage
https://forums.fogproject.org/topic/14689/high-cpu-usage-on-fog-server/9

@sebastian-roth
All the laptops we have are HP Probook x360 435 G7 model,

thanks

@sebastian-roth Moving it to 12 did the trick! Is there anything else I should change or do? Thank you guys for the help!

@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.