Failed to set RelaySelect

Usage and Config Platform
1

I’m not sure if I am applying a setting correctly but it is listed as being a config option for 9.5.x. It says it is a numerical value but when setting via the console actions fail to apply _BESClient_RelaySelect_IntervalSeconds. I attempted another action without the quotes thinking the quotes were causing it to be a string.

 Command failed (invalid setting value) setting "_BESClient_RelaySelect_IntervalSeconds"="60" on "Mon, 05 Mar 2018 22:34:42 +0000" for client

 Command failed (invalid setting value) setting "_BESClient_RelaySelect_IntervalSeconds"=60 on "Mon, 05 Mar 2018 22:40:15 +0000" for client
2

60 seconds is WAY too aggressive for this setting, this would cause the agent to no longer function if this setting value were allowed. It would just reselect the relay non stop. I would not recommend setting this to less than once per hour.

  • What are you trying to achieve with this setting?
  • What is the goal?
  • What is the problem you are trying to solve?

I have a feeling you are trying to fix the a problem in the wrong way. Command polling might be what you are looking for, but every 60 seconds is a bit aggressive for even that.

Example Content for settings: https://github.com/jgstew/bigfix-content/tree/master/fixlet/clientsettings

setting "_BESClient_Download_RetryMinutes"="1" on "{ parameter "action issue date" of action}" for client

I believe it must always be a string, and you should always use "{ parameter "action issue date" of action}" unless you have a specific reason not to.

4

This is for testing relay affiliation with a single machine. I can adjust it a bit higher if the setting is too low for bigfix to accept. After I’m done it was going to be set back to the 6 hour default.

5

I should mention this setting was being applied from the console using the edit settings menu.

1 Like
6

You can trigger a relay select with an action or an offer on demand, no need to change the interval.

Example: https://github.com/jgstew/bigfix-content/blob/master/fixlet/Trigger%20Relay%20Selection%20-%20Offer.bes

This is the entire actionscript required:

relay select

You can take a custom action with that actionscript and target it to a specific machine. This works fine if UDP notifications are working or command polling is in place, otherwise it would take a while to take effect.

You can also take the linked offer as a policy action and make it available to all of your machines, or just test machines and allow any user to trigger a relay selection as a diagnostic measure. You can even rate limit it to once every hour as the maximum frequency that a user could trigger it. You could also only make the offer available to admin users or users in IT Staff OUs.

Related:

8

Thanks for the input.

1 Like