Posts made by Kiweegie

Hi all first off a simple question how can I allocate a host to a user in the form of a loan so it shows on the Equipment Loan report under Reports > Equipment loan? I’d have thought there was a checkbox or similar under a registered host but I cannot for the life of me find anything. Likewise under a local user account there is no “Loan x Host”.

This feature if it works how I think it does would be invaluable for our service desks to keep track of who borrowed which laptop and when, as users tend to not return them unless chased.

Which leads me to my next question, is it possible to allocate this to an Active Directory user via the LDAP Plugin somehow? I have the LDAP plugin working and logins are working to the FOG ui via membership of the relevant FOG Admins group.

And under Reports > User tracking I can see a list of Domain user accounts to select from so it would appear that AD User lookup does work.

Probably missing something very obvious here I’m sure…

cheers Tom

@Tom-Elliott Excellent stuff, added to my notes

Edit: actually I had that format under the Admin group but not the Mobile group. Which leads me to a question of my own - what is the Mobile group actually used for?

Hi @stuhad

I have this working on 1.5.7 dev branch on Ubuntu 18.04 so can walk you through what I’ve done in case that helps? Also check out this post by @m144 which got me started in the right direction.

Need to install the php plugin and restart apache first off

sudo apt-get install php-ldap
sudo systemctl restart apache2

One important note which doesn’t seem to be documented anywhere - the AD Bind password does not like special characters. I’ve not had time to test which ones are ok and which are not so just went with an alphanumeric password to get up and running.

Assuming your domain is example.com and you have 2 domain controllers:

dc01.example.com
dc02.example.com

Create a security group to house the users you want to log in over LDAP here we will use group fogserver admins in the OU=security groups. And a service account which has been delegated the rights to add and delete computer objects on your domain or in a pinch added as member of the Domain Admins group.

In the FOG ui click on the LDAP icon and then create new LDAP link on the left and fill in details as follows

LDAP connection name: dc01.example.com (each connection name must be unique)
LDAP Server Address: dc01.example.com
LDAP Server Port: 389
Search Base DN: dc=example,dc=com
Group Search DN: dc=example,dc=com
Admin group: cn=fogserver_admins,ou=security groups,dc=example,dc=com
Mobile group: cn=fogserver_admins,ou=security groups,dc=example,dc=com
User Name Attribute: sAMAccountName
Group Member Attribute: member
Search Scope: Subtree and below
Bind DN: cn=service fogserver,ou=service_accounts,dc=example,dc=com
Bind password: <password for service account - add in plain text)

You can (and should) add multiple entries here with your other DCs for redundancy, just fill in another LDAP entry with unique connection name.

You should then be able to login to the FOG web portal with a domain username e.g. foguser (no need to add as example\foguser)

If a user who is not a member of your fogserver admins group tries to login it will fail on the UI with error

fogserver_admins))(member=CN=Jake Fake,OU=Users,OU=Sales,DC=example,DC=com)); Result: 0\nPHP message: Plugin LDAP::_result(). Search Method: search; Filter: (&(|(name=cn=fogserver_admins)(name=ou=security groups)(name=dc=example)(name=dc=com))(member=CN=Jake Fake,OU=Users,OU=Sales,DC=example,DC=com)); Result: 0\nPHP message: Plugin LDAP::authLDAP() Access level is still 0 or false. No access is allowed!\n', referer: http://fogserver/fog/management/index.php?node=home

Try that and if you’re still having issues let us know what OS you’re running and what entries you’re using in the LDAP setup - feel free to edit the entries for privacy reasons.

regards Tom

Thanks to a support session from @Sebastian-Roth this evening we’ve confirmed that this is actually working as designed.

There are 2 things at play.

One: Location plugin

Albeit the location plugin being installed the active tasks list initially shows the task as linking to the wrong storage node. This is only until such time as the client boots and checks in then updates to show the correct storage node is actually being used.

Two: BIOS boot order on clients

In our case due to changes in the BIOS boot order on the remote site computers they were never seeing the FOG task on boot so the task still shows on the Active Tasks page as wrong storage node.

I will resolve the BIOS issue on the remote sites and then test again and confirm back that all is working as designed.

regards Tom

@Sebastian-Roth I did now, and have replied

Hi @Sebastian-Roth

In case it leads to any pointers or brainwaves.

I thought initially the main server was imaging fine as images sent from GEO01VFOG01 to devices within Georgia site pick up OK. However I can see an example this morning where a machine is trying to image from COL01VFOG01 (Colorado Office) which is the only storage node in the Toys 'R Us storage group. (I’ve updated my spreadsheet below which didn’t accurately reflect this).

In the greater number of cases imaging from Georgia office to Georgia machines is working but imaging to remote sites is pulling from the wrong storage node.

Looking at the dashboard I can the display for the Mattel Storage group displays 99.9999999

Instead of the split shown by the Toys 'R Us group

This could be purely cosmetic and the display was not meant to handle more than 99 clients. I presume this shows the number of client activity per storage group?

I can’t seem to find any logs for the plugins, are there any?

regards Tom

@Sebastian-Roth Appreciate the time and effort Sebastian. Let me know if you need anything tested my side please.

regards Tom

@Sebastian-Roth said in Fog 1.5.7 Locations Plugin pulling image from wrong storage node:

SELECT ngmID,ngmMemberName,ngmIsMasterNode,ngmGroupID,ngmIsEnabled,ngmHostname,ngmMaxClients FROM nfsGroupMembers;

Here you go

+-------+---------------+-----------------+------------+--------------+----------------+---------------+
| ngmID | ngmMemberName | ngmIsMasterNode | ngmGroupID | ngmIsEnabled | ngmHostname    | ngmMaxClients |
+-------+---------------+-----------------+------------+--------------+----------------+---------------+
|     1 | GEO01VFOG01   | 1               |          1 | 1            | 10.166.136.199 |            10 |
|     2 | GEO01VFOG02   | 1               |          2 | 1            | 10.166.136.198 |            10 |
|     3 | CON01VFOG01   | 0               |          2 | 1            | 192.168.7.1    |            10 |
|     4 | ALA02VFOG01   | 0               |          2 | 1            | 192.168.1.1    |            10 |
|     5 | ARK01VFOG01   | 0               |          2 | 1            | 192.168.9.1    |            10 |
|     6 | ARI01VFOG01   | 0               |          2 | 1            | 192.168.11.1   |            10 |
|     7 | LOU01VFOG01   | 0               |          2 | 1            | 192.168.6.1    |            10 |
|     8 | CAL01VFOG01   | 0               |          2 | 1            | 192.168.2.1    |            10 |
|     9 | COL02VFOG01   | 0               |          2 | 1            | 192.168.4.1    |            10 |
|    10 | WIS02VFOG01   | 0               |          2 | 1            | 192.168.10.1   |            10 |
|    11 | SOU01VFOG01   | 0               |          2 | 1            | 192.168.8.1    |            10 |
|    12 | KEN02VFOG01   | 0               |          2 | 1            | 192.168.5.1    |            10 |
|    13 | COL01VFOG01   | 0               |          1 | 1            | 192.168.3.1    |            10 |
+-------+---------------+-----------------+------------+--------------+----------------+---------------+

@Sebastian-Roth said in Fog 1.5.7 Locations Plugin pulling image from wrong storage node:

SELECT * FROM location;

+-----+--------------------+-------+-----------------+----------------+------------+---------------------+--------------+
| lID | lName              | lDesc | lStorageGroupID | lStorageNodeID | lCreatedBy | lCreatedTime        | lTftpEnabled |
+-----+--------------------+-------+-----------------+----------------+------------+---------------------+--------------+
|   2 | Alabama	           |       |               2 |              4 | fog        | 2020-01-31 23:37:10 | 1            |
|   3 | Connecticut	   |       |	           2 |              3 | fog        | 2020-01-31 23:37:28 | 1            |
|   4 | Louisiana 	   |       |               2 |              7 | fog        | 2020-01-31 23:39:08 | 1            |
|   5 | Arizona      	   |       |               2 |              6 | fog        | 2020-01-31 23:39:32 | 1            |
|   6 | California         |       |               2 |              8 | fog        | 2020-01-31 23:41:10 | 1            |
|   7 | Arkansas           |       |               2 |              5 | fog        | 2020-01-31 23:41:35 | 1            |
|   8 | Colorado Shop      |       |               2 |              9 | fog        | 2020-01-31 23:42:51 | 1            |
|   9 | Kentucky           |       |               2 |             12 | fog        | 2020-02-01 01:22:42 | 1            |
|  10 | South Dakota       |       |               2 |             11 | fog        | 2020-02-01 01:23:37 | 1            |
|  11 | Wisconsin          |       |               2 |             10 | fog        | 2020-02-01 01:23:53 | 1            |
|  12 | Georgia            |       |               1 |              1 | fog        | 2020-02-01 01:24:45 | 1            |
|  14 | Colorado Office    |       |               1 |             13 | kiweegie   | 2020-02-01 15:34:10 | 1            |
+-----+--------------------+-------+-----------------+----------------+------------+---------------------+--------------+

All storage node have now been uplifted to the latest dev version 1.5.709. I edited the /opt/fog/.fogsettings on each to amend to the new fogstorage creds first.

I’ve deployed image task to Wisconsin desktop now and no longer picking up Alabama storage node, this time it’s selected California.

Going back over my setup, each location is set with Use inits and kernels from this node option checked.

There is a location for each site with 2 in Georgia (head office), 2nd of which I had setup as location for Georgia but linked to the storage node. I don’t think this is actually required so have removed this location entry.

There are only 2 storage groups, Toys’RUs and Mattel with latter being replicated out to all the storage nodes.

All storage nodes therefore are pointed to the Mattel Storage group with exception of the Georgia Head office (normal FOG) server which points to Toys’RUs.

I “think” everything is set as it should be. Is there a log file which shows which storage node is being selected and why?

cheers Tom

@Tom-Elliott @Sebastian-Roth

Thanks Tom, can see that in the GUI ok and it matches what was displayed on screen during installation.

FOG configuration page > FOG Settings > FOG Storage Nodes > STORAGENODE MYSQLPASS

My question was around whether the storage nodes need to be updated to reflect this change? Per this section in the installer unless I’m mistaken.

What is the username to access the database?
This information is storage in the management portal under
'FOG Configuration' ->
'FOG Settings' ->
'FOG Storage Nodes' ->
'FOG_STORAGENODE_MYSQLUSER'. Username [fogstorage]:
What is the password to access the database?
This information is storage in the management portal under
'FOG Configuration' ->
'FOG Settings' ->
'FOG Storage Nodes' ->
'FOG_STORAGENODE_MYSQLPASS'.  Password:

I’ve updated the 2 master nodes (normal and storage) in Georgia only at this stage and kicked off an image deployment task to a machine in Wisconsin. Its picking up the storage node from Alabama instead still.

To which end I’m going to kill that task and uplift all nodes onto the 1.5.709 dev branch and try again.

regards Tom

@Sebastian-Roth said in Fog 1.5.7 Locations Plugin pulling image from wrong storage node:

git checkout dev-branch

Hi @Sebastian-Roth

I’ve snapshotted both vms for the 2 Georgia Servers, GEO01VFOG01 and GEO01VFOG02 and uplifted both to latest dev version 1.5.7.109

KERNEL RAMDISK SIZE was already showing as 275000

Can see on this version it forces a root mysql password to be added.

Also that the fogstorage DB password used previously was deemed not secure enough so new one has been generated. From memory the storage node setup calls this user account so do we need to update all the storage nodes to use this pw? If so how or is it simply easiest to uplift all the nodes to dev instance?

regards Tom

@Sebastian-Roth Hi Sebastien & @Tom-Elliott more than happy to help gents, you’re doingme the favour being so quick to respond to requests and with really good/helpful suggestions. I only wish paid support was this good…

I’ll snapshot the VMs for roll back no problem - i presume every one of the nodes needs updated this way or can I get away with (initially at least) the 2 master nodes in my head office? Only ask as there are 12 nodes to snapshot/update over 10 different vcenters/esxi hosts. If needs be I can do though.

Let me know on the above and I shall proceed accordingly. I’m technically on leave tomorrow but the imaging solution here is getting a lot of focus up the food chain as it were so I’m keen to get working as soon as I can. I can dial in from home tomorrow to focus on this without other distractions

regards Tom

@george1421 @Sebastian-Roth

Hi both not seeing this error any more so can be marked as resolved. I was not seeing the issue before editing the // in the exports file so can’t say that was the fix. Not sure what has changed if anything here other than permissions on the images themselves within the /mnt/images directory.

Ownership was set on the folder to fogproject:root but the images are getting set as root:root. I amended this to fogproject:root again so not sure if that is needed? If so can add sticky bit to get around this perhaps.

EDIT: Ignore above comment ref permissions - some are set as fogproject:root and some as root:root - both work so the permissions is a red herring.

Thoughts welcome

regards Tom

@Sebastian-Roth good spot on the // it was there in exports on geovfog02 server. I’ve now corrected that I’ll blame my poor eyesight on that one…

I’ve double checked all other nodes to be on the safe side and it was only this one.

Ignore the ip from original image was screenshot from an earlier build, albeit same error.

edit: I’ve corrected the original image to avoid confusion and also provide better image - notepad++ with Deep Black theme appplied.

regards Tom

@Sebastian-Roth said in Could not mount images folder (bin/fog.download) ... failed: Operation not supported:

ls -alR /mnt/images/

Here you go Sebastien.

Output from geovfog01 (Georgia normal master server)

admin@geo01vfog01:~$ sudo ls -alR /mnt/images/
[sudo] password for admin:
/mnt/images/:
total 52
drwxr-xr-x 10 fogproject root  4096 Feb  4 18:52 .
drwxr-xr-x  3 root       root  4096 Jan 30 11:25 ..
drwxrwxrwx  3 fogproject root  4096 Feb  4 18:52 dev
drwx------  2 fogproject root 16384 Jan 30 11:25 lost+found
-rwxrwxrwx  1 fogproject root     0 Jan 30 14:58 .mntcheck
drwxrwxrwx  2 fogproject root  4096 Jan 30 13:30 postdownloadscripts
drwxrwxrwx  2 fogproject root  4096 Feb  4 18:18 Toysrus_Post_Sysprep
drwxrwxrwx  2 fogproject root  4096 Feb  4 18:03 Toysrus_Pre_Sysprep
drwxrwxrwx  2 fogproject root  4096 Feb  5 15:40 Mattel_Post_Sysprep
drwxrwxrwx  2 fogproject root  4096 Feb  4 18:39 Mattel_Presysprep
drwxrwxrwx  2 fogproject root  4096 Feb  4 15:14 Windows10_presysprep

/mnt/images/dev:
total 12
drwxrwxrwx  3 fogproject root 4096 Feb  4 18:52 .
drwxr-xr-x 10 fogproject root 4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root    0 Jan 30 13:30 .mntcheck
drwxrwxrwx  2 fogproject root 4096 Jan 30 13:30 postinitscripts

/mnt/images/dev/postinitscripts:
total 12
drwxrwxrwx 2 fogproject root 4096 Jan 30 13:30 .
drwxrwxrwx 3 fogproject root 4096 Feb  4 18:52 ..
-rwxrwxrwx 1 fogproject root  249 Jan 30 13:30 fog.postinit

/mnt/images/lost+found:
total 20
drwx------  2 fogproject root 16384 Jan 30 11:25 .
drwxr-xr-x 10 fogproject root  4096 Feb  4 18:52 ..

/mnt/images/postdownloadscripts:
total 12
drwxrwxrwx  2 fogproject root 4096 Jan 30 13:30 .
drwxr-xr-x 10 fogproject root 4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root  235 Jan 30 13:30 fog.postdownload

/mnt/images/Toysrus_Post_Sysprep:
total 7629888
drwxrwxrwx  2 fogproject root       4096 Feb  4 18:18 .
drwxr-xr-x 10 fogproject root       4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root          5 Feb  4 18:14 d1.fixed_size_partitions
-rwxrwxrwx  1 fogproject root    1048576 Feb  4 18:14 d1.mbr
-rwxrwxrwx  1 fogproject root        190 Feb  4 18:14 d1.minimum.partitions
-rwxrwxrwx  1 fogproject root         15 Feb  4 18:14 d1.original.fstypes
-rwxrwxrwx  1 fogproject root          0 Feb  4 18:14 d1.original.swapuuids
-rwxrwxrwx  1 fogproject root    9265465 Feb  4 18:14 d1p1.img
-rwxrwxrwx  1 fogproject root 7802656523 Feb  4 18:18 d1p2.img
-rwxrwxrwx  1 fogproject root        190 Feb  4 18:14 d1.partitions

/mnt/images/Toysrus_Pre_Sysprep:
total 8060100
drwxrwxrwx  2 fogproject root       4096 Feb  4 18:03 .
drwxr-xr-x 10 fogproject root       4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root          5 Feb  4 17:59 d1.fixed_size_partitions
-rwxrwxrwx  1 fogproject root    1048576 Feb  4 17:59 d1.mbr
-rwxrwxrwx  1 fogproject root        190 Feb  4 17:59 d1.minimum.partitions
-rwxrwxrwx  1 fogproject root         15 Feb  4 17:59 d1.original.fstypes
-rwxrwxrwx  1 fogproject root          0 Feb  4 17:59 d1.original.swapuuids
-rwxrwxrwx  1 fogproject root  453635778 Feb  4 17:59 d1p1.img
-rwxrwxrwx  1 fogproject root 7798828240 Feb  4 18:03 d1p2.img
-rwxrwxrwx  1 fogproject root        190 Feb  4 17:59 d1.partitions

/mnt/images/Mattel_Post_Sysprep:
total 7215252
drwxrwxrwx  2 fogproject root       4096 Feb  5 15:40 .
drwxr-xr-x 10 fogproject root       4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root          5 Feb  4 18:46 d1.fixed_size_partitions
-rwxr-xr-x  1 fogproject root    1048576 Feb  5 15:40 d1.mbr
-rwxr-xr-x  1 fogproject root        190 Feb  5 15:40 d1.minimum.partitions
-rwxrwxrwx  1 fogproject root         15 Feb  4 18:46 d1.original.fstypes
-rwxrwxrwx  1 fogproject root          0 Feb  4 18:46 d1.original.swapuuids
-rwxr-xr-x  1 fogproject root   10387064 Feb  5 15:40 d1p1.img
-rwxr-xr-x  1 fogproject root 7376949941 Feb  5 15:42 d1p2.img
-rwxr-xr-x  1 fogproject root        190 Feb  5 15:40 d1.partitions

/mnt/images/Mattel_Presysprep:
total 7087908
drwxrwxrwx  2 fogproject root       4096 Feb  4 18:39 .
drwxr-xr-x 10 fogproject root       4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root          5 Feb  4 18:35 d1.fixed_size_partitions
-rwxrwxrwx  1 fogproject root    1048576 Feb  4 18:35 d1.mbr
-rwxrwxrwx  1 fogproject root        190 Feb  4 18:35 d1.minimum.partitions
-rwxrwxrwx  1 fogproject root         15 Feb  4 18:35 d1.original.fstypes
-rwxrwxrwx  1 fogproject root          0 Feb  4 18:35 d1.original.swapuuids
-rwxrwxrwx  1 fogproject root  454330540 Feb  4 18:35 d1p1.img
-rwxrwxrwx  1 fogproject root 6802601965 Feb  4 18:39 d1p2.img
-rwxrwxrwx  1 fogproject root        190 Feb  4 18:35 d1.partitions

/mnt/images/Windows10_presysprep:
total 8864012
drwxrwxrwx  2 fogproject root       4096 Feb  4 15:14 .
drwxr-xr-x 10 fogproject root       4096 Feb  4 18:52 ..
-rwxrwxrwx  1 fogproject root         13 Feb  4 15:09 d1.fixed_size_partitions
-rwxrwxrwx  1 fogproject root    1048576 Feb  4 15:09 d1.mbr
-rwxrwxrwx  1 fogproject root        861 Feb  4 15:09 d1.minimum.partitions
-rwxrwxrwx  1 fogproject root         15 Feb  4 15:09 d1.original.fstypes
-rwxrwxrwx  1 fogproject root          0 Feb  4 15:09 d1.original.swapuuids
-rwxrwxrwx  1 fogproject root  444522502 Feb  4 15:09 d1p1.img
-rwxrwxrwx  1 fogproject root   11385185 Feb  4 15:10 d1p2.img
-rwxrwxrwx  1 fogproject root     174678 Feb  4 15:10 d1p3.img
-rwxrwxrwx  1 fogproject root 8619581073 Feb  4 15:14 d1p4.img
-rwxrwxrwx  1 fogproject root        861 Feb  4 15:09 d1.partitions
admin@geo01vfog01:~$

Output from geovfog02 (Georgia storage master server)

admin@geo01vfog02:~$ sudo !!
sudo ls -alR /mnt/images/
[sudo] password for admin:
/mnt/images/:
total 36
drwxr-xr-x 6 fogproject root  4096 Feb  4 16:13 .
drwxr-xr-x 3 root       root  4096 Jan 30 18:20 ..
drwxrwxrwx 3 fogproject root  4096 Feb  4 16:13 dev
drwx------ 2 fogproject root 16384 Jan 30 18:20 lost+found
-rwxrwxrwx 1 fogproject root     0 Jan 30 19:19 .mntcheck
drwxrwxrwx 2 fogproject root  4096 Jan 30 19:19 postdownloadscripts
drwxrwxrwx 2 fogproject root  4096 Feb  4 16:13 Mattel_Post_Sysprep

/mnt/images/dev:
total 12
drwxrwxrwx 3 fogproject root 4096 Feb  4 16:13 .
drwxr-xr-x 6 fogproject root 4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root    0 Jan 30 19:19 .mntcheck
drwxrwxrwx 2 fogproject root 4096 Jan 30 19:19 postinitscripts

/mnt/images/dev/postinitscripts:
total 12
drwxrwxrwx 2 fogproject root 4096 Jan 30 19:19 .
drwxrwxrwx 3 fogproject root 4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root  249 Jan 30 19:19 fog.postinit

/mnt/images/lost+found:
total 20
drwx------ 2 fogproject root 16384 Jan 30 18:20 .
drwxr-xr-x 6 fogproject root  4096 Feb  4 16:13 ..

/mnt/images/postdownloadscripts:
total 12
drwxrwxrwx 2 fogproject root 4096 Jan 30 19:19 .
drwxr-xr-x 6 fogproject root 4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root  235 Jan 30 19:19 fog.postdownload

/mnt/images/Mattel_Post_Sysprep:
total 7215252
drwxrwxrwx 2 fogproject root       4096 Feb  4 16:13 .
drwxr-xr-x 6 fogproject root       4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root          5 Feb  4 16:09 d1.fixed_size_partitions
-rwxrwxrwx 1 fogproject root    1048576 Feb  4 16:09 d1.mbr
-rwxrwxrwx 1 fogproject root        190 Feb  4 16:09 d1.minimum.partitions
-rwxrwxrwx 1 fogproject root         15 Feb  4 16:09 d1.original.fstypes
-rwxrwxrwx 1 fogproject root          0 Feb  4 16:09 d1.original.swapuuids
-rwxrwxrwx 1 fogproject root   10387064 Feb  4 16:09 d1p1.img
-rwxrwxrwx 1 fogproject root 7376949941 Feb  4 16:13 d1p2.img
-rwxrwxrwx 1 fogproject root        190 Feb  4 16:09 d1.partitions
admin@gla01vfog02:~$ sudo ls -alR /mnt/images/
/mnt/images/:
total 36
drwxr-xr-x 6 fogproject root  4096 Feb  4 16:13 .
drwxr-xr-x 3 root       root  4096 Jan 30 18:20 ..
drwxrwxrwx 3 fogproject root  4096 Feb  4 16:13 dev
drwx------ 2 fogproject root 16384 Jan 30 18:20 lost+found
-rwxrwxrwx 1 fogproject root     0 Jan 30 19:19 .mntcheck
drwxrwxrwx 2 fogproject root  4096 Jan 30 19:19 postdownloadscripts
drwxrwxrwx 2 fogproject root  4096 Feb  4 16:13 Mattel_Post_Sysprep

/mnt/images/dev:
total 12
drwxrwxrwx 3 fogproject root 4096 Feb  4 16:13 .
drwxr-xr-x 6 fogproject root 4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root    0 Jan 30 19:19 .mntcheck
drwxrwxrwx 2 fogproject root 4096 Jan 30 19:19 postinitscripts

/mnt/images/dev/postinitscripts:
total 12
drwxrwxrwx 2 fogproject root 4096 Jan 30 19:19 .
drwxrwxrwx 3 fogproject root 4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root  249 Jan 30 19:19 fog.postinit

/mnt/images/lost+found:
total 20
drwx------ 2 fogproject root 16384 Jan 30 18:20 .
drwxr-xr-x 6 fogproject root  4096 Feb  4 16:13 ..

/mnt/images/postdownloadscripts:
total 12
drwxrwxrwx 2 fogproject root 4096 Jan 30 19:19 .
drwxr-xr-x 6 fogproject root 4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root  235 Jan 30 19:19 fog.postdownload

/mnt/images/Mattel_Post_Sysprep:
total 7215252
drwxrwxrwx 2 fogproject root       4096 Feb  4 16:13 .
drwxr-xr-x 6 fogproject root       4096 Feb  4 16:13 ..
-rwxrwxrwx 1 fogproject root          5 Feb  4 16:09 d1.fixed_size_partitions
-rwxrwxrwx 1 fogproject root    1048576 Feb  4 16:09 d1.mbr
-rwxrwxrwx 1 fogproject root        190 Feb  4 16:09 d1.minimum.partitions
-rwxrwxrwx 1 fogproject root         15 Feb  4 16:09 d1.original.fstypes
-rwxrwxrwx 1 fogproject root          0 Feb  4 16:09 d1.original.swapuuids
-rwxrwxrwx 1 fogproject root   10387064 Feb  4 16:09 d1p1.img
-rwxrwxrwx 1 fogproject root 7376949941 Feb  4 16:13 d1p2.img
-rwxrwxrwx 1 fogproject root        190 Feb  4 16:09 d1.partitions
admin@geo01vfog02:~$

I’ve added the server setup to another ticket ref location plugin but might be of use to see here also.

Hi @george1421

output as follows on all nodes.

/mnt//images *(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/mnt/images/dev *(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)

cheers Tom

Hi Sebastien, appreciate the comments. To help others follow along here’s the setup I’m using with names changed to protect the innocent

That will hopefully make it easier to see what I’ve tried to setup. All sites barring Connecticut are on the MPLS, Connecticut is in a hosted site connected over site-to-site VPN.

I understand the concept of Host groups - i’ve just used them to set settings en masse as its designed to do. Just trying to give as complete an overview of the setup so there aren’t any surprises.

Max clients on each node is default of 10 but we’ve not yet tried to deploy to more than a half dozen at a time. I assume your comment here is referring to if we go over the 10 max clients at once it needs to look for a slot on another available storage node which makes sense.

One more question if I may? When an image is uploaded how does the replication to remote nodes work with regards the changes? I’d assume the nature of the image is that it copies the whole image over again? Or can it sort through the changed files in some way and just upload the deltas?

regards Tom

Hi all

Ubuntu 18.04.3, FOG version 1.5.7

I’m running the locations plugin with 2 servers in head office, one normal server set as the Master node for this site and one other main site both of which share a common image plus one Storage server set as the Master node for all other remote sites, mainly smaller branch offices.

Lets refer to these servers as Georgia1 (Normal Master) and Georgia2 (Storage Master) in head office.

Remaining servers are:

Colorado (Storage server replicating from Georgia1)
Arkansas, California and Delaware (Storage servers replicating from Georgia2)

I’ve set up 2 storage groups StorageA and StorageB

StorageA is made up of Georgia1 and Colorado
StorageB is made up of Georgia2, Arkansas, California and Delaware

I have set up locations as follows

Georgia
Georgia-Rep *
Arkansas
California
Colorado
Delaware

• this is in same location but set to handle imaging of machines internally to test the images which will be deployed to remote sites (I may be overthinking this).

I’ve linked hosts to groups, and those groups to locations.

When imaging a machine in Georgia with its location set to Georgia or Georgia-Rep it seems to be pulling the image from Colorado storage node.

These are in different sites, on different subnets. Is there a log file somewhere I can check to determine the logic being applied somewhere?

regards Tom

I have locations setup for each site plus 2 for head office to reflect the different storage groups and also so we can image in main office using images for the remote sites for testing. So:

Main office = Site1A and SiteaB
Remote offices Sites 2-12

@george1421 said in Could not mount images folder (bin/fog.download) ... failed: Operation not supported:

sudo showmount -e 127.0.0.1

Hi George,

Output of command as follows

clnt_create: RPC: Program not registered

I’ve checked NFS server service:

systemctl status nfs-server

and was not started showing following output:

● nfs-server.service - NFS server and services
   Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-02-04 21:58:25 UTC; 21h ago
  Process: 905 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 903 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
  Process: 891 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)

Feb 04 21:58:25 geo01vfog01 systemd[1]: Starting NFS server and services...
Feb 04 21:58:25 geo01vfog01 exportfs[891]: exportfs: Failed to stat /mnt/images/dev: No such file or directory
Feb 04 21:58:25 geo01vfog01 systemd[1]: nfs-server.service: Control process exited, code=exited status=1
Feb 04 21:58:25 geo01vfog01 systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Feb 04 21:58:25 geo01vfog01 systemd[1]: Stopped NFS server and services.

I was able to start it again via

sudo systemctl start nfs-server

This was the same on both the Master (normal) and Master (storage) nodes.

I’ve enabled debugging to see if I can figure out why NFS server stopped which I’m guessing is the cause of the issue I’m seeing?

sudo vi /etc/default/nfs-kernel-server

Added following and restarted NFS service

RPCMOUNTDOPTS="--manage-gids --debug all"

Also seeing loads of these errors in syslog not sure if related?

Feb  5 19:05:06 fogserver systemd-resolved[842]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-20
18-0001, retrying transaction with reduced feature level UDP.
Feb  5 19:05:19 geo01vfog01 in.tftpd[21004]: tftp: client does not accept options
Feb  5 19:05:49 geo01vfog01 in.tftpd[21104]: tftp: client does not accept options
Feb  5 19:05:52 geo01vfog01 in.tftpd[21114]: tftp: client does not accept options
Feb  5 19:06:45 geo01vfog01 in.tftpd[21284]: tftp: client does not accept options
Feb  5 19:06:56 geo01vfog01 in.tftpd[21319]: tftp: client does not accept options

I’ll be able to confirm tomorrow when I’m back in the office that this is resolved or not.

I’m seeing a separate issue with the locations plugin doing something odd but will log separate ticket for that.

Thanks again George

regards Tom