Location Plugin - PHP Warning and Location Assigned Node not working

[Clebboii]

Hi all,

I have 2 issues:

• Firstly, I noticed that my main server was overheating. Using HTOP I saw that RSYSLOGD was using 80% of my CPU. I then used journalctl -r and saw the following logs:
  Jul 23 11:41:23 FOGServer env[1520]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:18 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:17 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:16 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:14 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:14 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:14 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:14 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:14 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:13 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:23 FOGServer env[1520]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:23 FOGServer env[1520]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:18 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:17 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  Jul 23 11:41:16 FOGServer env[1517]: PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121
  It seems something is wrong with the locations plugin. I have followed the tutorials. I have uninstalled for now and that has solved the issue.

• Secondly, I have 1 storage group and 2 nodes. 1 Master node and 1 storage node. The master node is at our main site and is deploying to the majority of machines. The storage node is on another site and is connected via a VPN. I have used the locations plugin to ensure all machines at their relevant site deploys via their relevant node ( ie. site 1 PC’s should be using the master node.). However it seems that FOG is still deploying based on the amount of available slots on each node (ie. sometimes site 2 tries to deploy over the VPN because site 2 is more busy than site 1).

Any suggestions or solutions?

[Greg Plamondon]

@Clebboii
I have the same issue. I have 27 storage nodes using the Location plugin. When adding a storage node, I have to manually assign the Storage group to the new location via editing it in mysql

[Tom Elliott]

@Clebboii said in Location Plugin - PHP Warning and Location Assigned Node not working:

PHP Warning: Undefined array key “REQUEST_METHOD” in /var/www/html/fog/lib/plugins/location/hooks/addlocationapi.hook.php on line 121

I’ve pushed an update to the dev-branch regarding this issue.

I don’t know if it will definitely fix it, but it should help prevent continued writing of this error.

As for the issue of slot and hopping, I’m not sure how I can simulate this issue. Is this a new issue or something that was noticed and we’re not really sure when it began and/or has always been there?

[Tom Elliott]

@Greg-Plamondon and @Clebboli are the Storage nodes associated to the same storage group?

For example:

Site 1 -> Default Group
Site 2 -> Default Group

Or are each storage node associated to their own Storage Groups?

The idea of storage groups is to spread the load of imaging. So if all storage nodes are part of the same storage group, then it makes sense the “jumping to different storage nodes within the group”.

While seemingly unexpected, the idea of jumping to other nodes within the same storage group is intended to balance the workload around as best it can. Sure this can probably be better handled, though I don’t know when I might get around to refactoring it. Just saying what I suspect might be happening.