@Tom-Elliott Thank you so much as always for the detailed, thorough explanations. I was able to get it working again, and tested both imaging and login with several users.
For anyone experiencing additional confusion, I made a quick settings screenshot of what worked for me (descriptions instead of actual data).
2 seconds after I posted the below, I was able to login. I am going to test imaging now.
Getting closer, but something is still off. I felt like I had to add an AD group somewhere specifically, for example if the 3 IT staff are part of the “ITStaff” group, shouldn’t I reference that somewhere within FOG itself? Instead of it pointing directly to an OU that could contain many groups? How does it know to look in ITStaff only for the users?
How does it know where to choose from? Also, do i still use just the samAccountName to login with?
Sorry I know you are swamped with requests today most likely.
@Tom-Elliott I was able to update the plugin and create a brand new LDAP that saves correctly, but having some trouble with associating the group itself. Where do I add the actual search DN for AD for the group to match to?
Under LDAP Groups, it just asks for a common name. Am I supposed to do this in "LDAP Group User Group Associations? Or is that for something else?
Upgraded to version 1.6, couldn’t login to LDAP. Updated the plugin, but everytime i try to add in a new LDAP server I get an error that says “Failed to add LDAP Server”
We use on prem LDAP, it has both port 389 and 636 but I truthfully don’t care which it uses. Any ideas I should check? This is our normal method here on campus for logging into FOG
@Tom-Elliott I also updated to 1807 and it has fixed it for me as well. As always Tom you are a mad scientist and always figure out the issue. FOG Project is the fastest bug resolution of any software we use and I mean that sincerely. I appreciate this software and your dedication to it so much, thanks for everything!
A test for anyone having this issue. I did a little trouble shooting, and if you go to: Reports > Pending Mac List and approve all the pending mac addresses at once, performance improved somewhat.
I am unsure if this is coincidental but for me my “Hosts” tab is now much more responsive. Same thing with the “Fog Settings” tab. Give that a try. Certainly worked for me for the moment.
@Tom-Elliott Yes we utilize the LDAP Plugin for all logins. Version 1.5.5, I will tried logging in with a local account but the slowness persisted.
@Tom-Elliott I collected both log files and sent them to you directly via “Chat”. you should see all of them in there. Thanks so much for investigating this issue.
@Tom-Elliott Thank you for looking into this. Are there any log files from my setup I can provide that would help you? For reference, my server environment is:
Dell Poweredge R620
2x Intel Xeon E5-2640vs 2ghz CPUs
128 Gb ram
Alma Linux 9.7
Fog 1.5.10.1804 (was 1798)
@Infojoe I am getting this exact same issue. Very long load times on the “Hosts” and “FOG Configuration” pages. Additionally there is a number now appended to the front of all the hosts for some reason.
I updated to the latest dev branch version 1.5.10.1804 hoping for a fix, but alas, no change. I applied patches to Alma Linux 9.7 and rebooted but still seeing high CPU on several processes including apache. I am happy to test anything and everything to assist in fixing this issue.
@george1421 Thank you for this suggestion. This disabling of “fastboot” worked PERFECTLY! I interrupted the OOBE with Shift + F10 and got the command line window. I shutdown using the “shutdown.exe -s -t 0” command you suggested. Then after booting up, the FOG capture task I had already started took over and it captured 100% as it should have.
Essentially, I had forgotten to disable fastboot like I normally do on EVERY computer I have. So when it “rebooted” it technically wasn’t rebooting the device since fastboot is a misguided absurd hibernation feature Microsoft developed. The error I got was nearly identical to the one in the original post.
Thanks so much for this suggestion George and all!
@Tom-Elliott Thank you so much Tom, as always I appreciate your support and guidance.
So, does that mean I should install the new one at the top? Or do I have the new one already by virtue of installing back in July? Sorry versioning gets confusing for me. Also what is FOS?
Our Fog instance updated to Kernel version 6.12.35 sometime over the summer. Since then new Kernel versions have been showing up under the Fog Configuration > Kernel Update menu per normal. The version number on these new versions however keep showing 6.12.35, the same that we already have. The first 6.12.35 shows July 15th as the date, but the newest 6.12.35 shows October 14th as the date.
Is this a bug only affecting us? Should we just update to the new version even though it shows the same number? Anyone else experiencing this? I just want to make sure I have the latest Kernel for new devices we purchase. Thanks everyone!
@Clebboii A workaround that always worked for me that was recommended by Tom was to use the full DNS name rather than the IP address. I was initially logging into the UI through the IP, and found that very same issue. When he mentioned it and I started using the full DNS name, the issue went away.
Simply Installing “Postfix” on Alma Linux and rebooting the server did the trick. After the server came back up, I successfully deployed an image, and afterwards the email came through without an issue. Had all the information filled out appropriately as well. Thank you very much Tom!
Requesting a feature addition in the “FOG Settings > FOG Email Settings” section that would allow an admin to test whether or not email is working. This would be similar to other programs that have a “test email” button with a box of who to send the test email to.
Or perhaps some built in logic to test if postfix or other email prereqs that FOG needs to send email post image deployment.
@Tom-Elliott As usual Tom you are a genius. I had forgotten to add the individual search domains for our active directory domains. Once I added those, and waited the requisite amount of time you mentioned, the machines that are on came back and now I can see them in the interface. This was super helpufl and I sincerely appreciate all the effort and insight you folks give into this great product.
For those experiencing the same issue on mainstream linux distros, navigate to your “resolv.conf” config file located in /etc/resolv.conf and add your individual search domains. Test a ping to a DNS name via command line on the box itself, then check your GUI again. Took about 2 minutes for it to reflect and show for me.
I thought FOG used “sendmail” so I installed that on the box. I am working on FOG version 1.6, and i copied over the settings from my previous working FOG install, but I suspect the email software on linux itself not being configured is where the issue is.
We do have an internal SMTP server that I could relay to, if that is a possibility. I would just need to know where in linux to configure that relay. I guess what I need is where to start looking for email config using sendmail, or some other built in linux mail program.
Version 1.5.10.1629
Environment - Dell Poweredge server running Alma Linux 9.5
FOG client 0.13
We recently migrated to a new FOG server (Wanted newer/better hardware). While FOG installed, and is functioning when capturing and deploying images, the “OS Details” feature on the “Hosts” screen shows a red exclamation mark for all new hosts we attach. Previously on the old server, it would sometimes glitch and show the exclamation mark. Now ALL of them show this. Am I missing a setting in the FOG client or Windows firewall setting on the host PC? While the feature isn’t critical, it was nice to see all green across the board. Thanks everyone!
