Fog 1.5.7 Locations Plugin pulling image from wrong storage node

[Sebastian Roth]

@Kiweegie Sorry, I’d need info from another query as well:

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

[Kiweegie]

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

@Kiweegie Sorry for the delay! I have some time tomorrow to work on this. I’ll try to set things up as close to what you have and try to find what’s wrong.

[Kiweegie]

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

regards Tom

[Kiweegie]

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]

@Kiweegie Not sure if you saw the chat bubble in the top right corner yet. Trying to contact you via PM.

[Kiweegie]

@Sebastian-Roth I did now, and have replied

[Kiweegie]

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

[AlexPDX]

This post is deleted!

[Sebastian Roth]

@AlexPDX Please open a new topic as your request has nothing to do with the initial post as far as I can see. Just copy and paste your text from this.