Posts made by george1421

@mrcur Great!! rEFInd is a great boot loader (once you tell it where to and not to look).

@mrcur Then edit /var/www/html/fog/service/ipxe/refind.conf

comment out

# scanfor internal

and uncomment

scanfor internal,hdbios,external,biosexternal

that should tell it to look in more places to see if it can find a boot device. rEFInd is a good choice to set as your global uefi exit mode. Its a real good boot loader (akin to grub)

@mrcur ok set exit mode for uefi to rEFInd. Let me look through the config file. I should be in /var/www/html/fog/service/ipxe directory.

@mrcur What type of hardware (uefi / bios-legacy) are you having issues with?

If its uefi, you will probably want to use rEFInd as your exit mode. You may need to tweak the refind.conf file to search for more devices if its not locating the hard drive.

As for a kernel update not important. This is still in iPXE, not FOS. So the iPXE boot code is in charge.

@mattbrown said in Unable to restart DHCP and TFTP services using default password after 1.4.4 update:

We’re now logging in as fogadm so could that be the conflict?

NO DON’T change this!

If you have changed the linux user fog you will break fog. That user account us under the management of the fog installer and its backend processes.

OK, what you need to do is review the password defined in /opt/fog/.fogsettings. Note what this password is.

Then, go to the web gui and confirm that in:

1. The storage managment -> Storage node (I think its was DefaultStorage) way down at the bottom, ensure the management user (fog) and management password are consistent with the .fogsettings file.
2. Then in FOG Configuration -> Fog Settings under the TFTP Server ensure the password is consistent with the .fogsettings.

My bet is one of those are inconsistent with the .fogsettings file.

@zorderelda The info you are looking for, unfortunately doesn’t exist outside of the brains of the developers. And I agree we really need to get some documentation on this to grow the list of available plugins.

I’ve done some tweaking of a few plugins and I can say they are not difficult but also a pita at the same time.

I worked on / with 2 plugins the LDAP and the Persistent Groups.

The persistent groups was created by the developers to aid in installing a sql trigger that simulates persistent groups in FOG. It is the most simple one with no menus or outward appearance that it has been installed.

The ldap plugin is a bit more complex, but it also shows you how to create tables, hook into a process. It also has a display/editor page. I can tell you the graphics at the top are fonts based on the font awesome library http://fontawesome.io/

The fog application has and calls out hooks at certain functions and as a plugin programmer you can tie into those hooks to add function to fog.

That is about it from what limited knowledge I have.

@joesay Not sure I understand your post but that’s OK.

What I want you to do is this.

1. Manually register this host.
2. Schedule a capture or deploy task it doesn’t matter, BUT before you submit the task select the debug check box and then submit the job.
3. PXE boot the target computer.
4. After a few enter key presses on the target computer it will drop you to a linux command prompt.
5. Once at the linux command prompt key in ip addr show Lets see if it picks up an IP address in debug mode.

Note for developers: The Compaq has a broadcom 57788 nic, and the nuc probably has a realtek nic.

@noelpd OK have someone login and then tail the apache error log we print debugging info there .

rhel/centos: /var/log/httpd/error_log
debian/ubuntu: /var/log/apache2/error.log

From there we can understand what is going wrong. We have tested the ldap plugin against openldap, but we have had more success (of course) with MS AD.

@noelpd The change will be automatic, once installed.

For people to be able to login using ldap they must be listed on the group identified by admin group field.

@jason-shoemake I just tried the fix and that didn’t solve the issue. So close though. Thank you for bringing that to my attention. (whoops I didn’t remove and add back).

Update: Confirm that the fix referenced by Jason does work

1. Open a linux command prompt on your FOG server.
2. Key in the following command:
   sudo wget -O /var/www/fog/lib/fog/plugin.class.php https://raw.githubusercontent.com/FOGProject/fogproject/6717f382177e714c1bd22eb11627133cfd4e0ebe/packages/web/lib/fog/plugin.class.php
3. Remove the ldap plugin
4. Reinstall the ldap plugin
5. Add in your ldap settings and save

@joesay Ok reviewing your pictures of the network information check (2) the ethernet adapter should have an IP address listed for eth0. I just confirmed on my dev box. Its seeing the mac address, but its not seeing the IP address.

@joesay OK we can then rule out spanning tree (networking infrastructure) from causing this.

@joesay While that is a very nice picture, what does that show us?

The idea of the dumb switch is that if your building switch has spanning tree enabled it may cut off your network connection at an unexpected time. The dumb switch will keep the building switch link port from seeing the wink as the FOS engine boots.

@george1421 @Developers could you look at this code. I did enter the correct fields and I’m getting the same error. Its almost like the page isn’t in the right mode, like view instead of edit/insert.

I can confirm that I get the same error on my dev box running 1.4.4. Removing and adding back the plugin doesn’t help either.

Just for clarity you need to adjust your fields a bit.

search base == the base where to start searching for users
group search dn == the base where the plugin will start searching for groups (you need this, can be the same as search base).

@noelpd sure enough its exactly as you said. Let me check

@joesay This looks like its passing the tests.

Just for the sake of argument (because we’ve seen a rash of this issue lately) can you place a dumb (unmanaged) switch between the building switch and the pxe booting computer and see if allows you to register? I’m seriously doubting my self on this one, but we need to rule it out.

would you mind posting a screen shot of the actual error so we can see what values are in the fields? That error is understandable and not at the same time.

@caw001 If that is the process you followed then something is not right with either the fog server or the usb module. Let me look into it. The kernel parameters don’t look correct. There should be more info in the kernel parameters almost like the grub config file is damaged. It should list the web server and storage info.

@joesay It also looks like you need to sync that monitor with the computer. since the image we need to see is actually off the left edge of the monitor.