@pilipp_edv

for the record the Active Directory is working only for the Windows clients as described in the FOG client repo but as you said you don’t want them to join only rename. Since we are discussing for linux clients maybe that is the clue for not being enabled by default.

The database cells hostUseAD and hostEnforce are the ones that enable the procedure to occur. Another test would be to add a host and check what value it has on the dB for hosts.hostUseAD and hosts.hostEnforce without adding the host to the group or changing anything from the dashboard.

@pilipp_edv

can you check the services tab on your dashboard? Is the hostname changer ticked?

also how is the host created in the first place (manually, autoregister, api?)

@PatrickL

you might want to check https://forums.fogproject.org/topic/17648/massive-cpu-usage-from-a-service

also please state the FOG version you are using. If its before 1.5.10.41 there were some security issues that were patched.

@Fog_Newb

try the below

/dev/disk/by-uuid/d61ab2ae-b79a-4b07-bfc5-4678ab0902f4 /images ext4 defaults 0 1
/dev/disk/by-uuid/3d7874cb-8c59-4e6d-8735-fb8361994590 /imagesdev ext4 defaults 0 1
/imagesdev  /images/dev   none    defaults,bind   0   0

Sources:

• https://man.archlinux.org/man/systemd.mount.5
• https://wiki.archlinux.org/title/Fstab#Bind_mount

@Fog_Newb said in FOG has issues if the temp image location is on another drive. FOG 1.5.10.1612 Ubuntu Server24.04.1 LTS:

/dev/disk/by-uuid/d61ab2ae-b79a-4b07-bfc5-4678ab0902f4 /images ext4 defaults 0 1
/dev/disk/by-uuid/3d7874cb-8c59-4e6d-8735-fb8361994590 /images/dev ext4 defaults 0 1

based on the reddit post you should try

/dev/disk/by-uuid/d61ab2ae-b79a-4b07-bfc5-4678ab0902f4 /images ext4 defaults 0 1
/dev/disk/by-uuid/3d7874cb-8c59-4e6d-8735-fb8361994590 /images/dev auto bind,x-systemd.requires=/images 0 0

@Fog_Newb

I believe the issue relates to /etc/fstab parameters because the mounts must reside in order.

Check the comment in reddit and try the proper parameters.

@Fog_Newb

as described in https://www.reddit.com/r/linux4noobs/comments/119i2vy/is_it_possible_to_mount_one_drive_as_a_subfolder/

probably its best to move everything away from the mount points and then create the new structure. Also as always in this occasions BACKUP before testing.

@Fog_Newb

99% it will work. The path /images/dev is the tmp location for image creation, so if you mount a 3rd drive you can achieve the expected result.

Hello,

for the second part you can mount anything (e.x. /sdb, /storageip, /nasdrive ) in /images and keep the storage independent from the VMs primary disk.

@Tom-Elliott couldn’t wait till tomorrow… tested with 1.6 and works with the below settings.

also in 1.6 you need to change Subree on line 988 also.

Thank you once more for your time and effort.

@Tom-Elliott I will test your new code from working-1.6 branch on our dev server and report back (tomorrow).

@Tom-Elliott being explicit helped me better understand the verification process.

Similarly your ‘admingroup’ (I know you’ve masked it) but do you have a group in your LDAP that has a full name of: https://entitlements.it.auth.gr/<adminGroupName>?

yes it’s a full html path

I used the filter from the original code and the results are:

Admin search
Filter: (&(|(name=https://entitlements.it.auth.gr/<adminGroupName>))(edupersonentitlement=uid=usename,ou=People,o=auth,c=gr)); Result: 0

Mobile Search (empty group)
Filter: (&(|(name=))(edupersonentitlement=uid=username,ou=People,o=auth,c=gr)); Result: 0

The correct filter should be (that is what I implemented):

Admin search
Filter: (&(|(edupersonentitlement=https://entitlements.it.auth.gr/<adminGroupName>))(uid=username))

Mobile search
Filter: (&(|(edupersonentitlement=https://entitlements.it.auth.gr/<userGroupName>))(uid=username))

@Tom-Elliott said in FOG 1.5.10.1604 ldap plugin:

@AUTH-IT-Center After some pretty serious testing I think I finally got the ldap plugin working on 1.6 as well.

Basically the problem with your current filter is you only check if the group exists and the username = username, not that the username actually is a member of that group.

We do have logic, I think that double checks but I hope you can see the issue here?

Hello @Tom-Elliott and thank you in advance for your time and effort. The changes that we tried to implement came from this post.

To better give you the concept we are trying to achieve let me explain with our setup and attributes.

What we want is that if a user trying to login to FOG server with his uid = username and is member with specific eduPersonEntitlement(s) can login to FOG server and be member of the FOG admins.

@Tom-Elliott Ι did try the 1.6 branch but didn’t work… that’s when I started debugging on 1.5.10.1064 dev-branch. I made the changes based on our LDAP needs. It would be proper if all the parameters came from the LDAPServers table and dynamically used in the code (even the filter maybe?)

@Tom-Elliott though I deployed it on our production server (from my fork), of course when you push the changes I can test it on the staging server. Just let us know.

@Tom-Elliott Hello!

We wanted to integrate the ldap plugin on our OpenLDAP server and after some debug sessions we finally managed to integrate it.

I opened a pull request https://github.com/FOGProject/fogproject/pull/635 with the changes we made. I believe the filter should be dynamic to match more attributes instead of having hard-coded the name=.

Please review it and check if it can be merged. Thank you.

@Tom-Elliott glad to hear it.

Where can I check - read other events in order to get more notifications? For example the creation of a snapin task, or the creation of a multicast image tasks? (so I can create new events on slack plugin)

Thank you once more the time and effort.

Hello all,

I searched the forums and found various posts for the slack plugin not properly working. I managed to get it to work by modifying some files to match the new slack api.

I pushed the changes on my fork and requested a merge with the dev-branch of fogproject https://github.com/FOGProject/fogproject/pull/631. I tested all the events (except image fail) on our staging server.

Waiting for you review.
Thank you.

@Tom-Elliott if the directory nfs.conf.d exists the fog-nfs.conf isn’t created.

I believe the code should be:

configureNFS() {
    dots "Setting up NFS configuration file"
    if [[ -f "/etc/nfs.conf" ]]; then
        # Fix all set port=20048 back to default values
        sed -i '/^port=20048/ {s/^port=20048/# port=0/}' /etc/nfs.conf >>$error_log 2>&1
    fi
    # set port in nfs.conf.d directory
    if [[ -f "/etc/nfs.conf" && ! -d "/etc/nfs.conf.d/" ]]; then
        mkdir /etc/nfs.conf.d/
    elif [[ -f "/etc/nfs.conf" &&  -d "/etc/nfs.conf.d/" ]]; then
        cat > /etc/nfs.conf.d/fog-nfs.conf <<EOF
[mountd]
port=20048
EOF
    elif [[ -f "/usr/etc/nfs.conf" && ! -d "/usr/etc/nfs.conf.d/" ]]; then
        mkdir /usr/etc/nfs.conf.d/
    elif [[ -f "/usr/etc/nfs.conf" &&  -d "/usr/etc/nfs.conf.d/" ]]; then
        cat > /usr/etc/nfs.conf.d/fog-nfs.conf <<EOF
[mountd]
port=20048
EOF
    fi
    errorStat $?

@Tom-Elliott just a friendly reminder. The dev-branch doesn’t have the new code in functions.sh for the nfs mount.

Thank you for all your help.