BigFix Relay stops reporting to BigFix Main Server after few hours

dbatista 2021-01-06 12:43:38 UTC #1

Hi guys,

I recently installed a BigFix Relay Server (version 10.0) through console using the fixlet provided. It successfully installs the relay but after few hours the relay selects itself as Relay and it stops communicating with the Main Server.

Is it normal behaviour? I dont think so but I would like your help and thoughts.

Thanks in advance.

At 13:34:55 +0000 -
Beginning Relay Select
At 13:34:56 +0000 -
GetRelayInfo: checking 'http://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=Version’
GetRelayInfo: Valid Relay
Unrestricted mode
Configuring listener without wake-on-lan

dmccalla 2021-01-06 15:01:45 UTC #2

Its normal for a client log to look this way when installed on a relay server. The relay that the system is using will be logged a couple lines below like what I have here… in this case my relay is reporting into my root server.

At 10:34:31 -0500 - 
   RegisterOnce: Attempting secure registration with 'https://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.1.41&Body=1623459980&SequenceNumber=771&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://**ROOT_SERVERNAME**%3a52311&AdapterInfo=00-0c-29-a6-0e-94_192.168.1.0%2f24_192.168.1.4_0'
   Unrestricted mode
   Configuring listener without wake-on-lan
   Registered with url 'https://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.1.41&Body=1623459980&SequenceNumber=771&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://**ROOT_SERVERNAME**%3a52311&AdapterInfo=00-0c-29-a6-0e-94_192.168.1.0%2f24_192.168.1.4_0'
   Registration Server version 10.0.2.15 , Relay version 10.0.1.41
   Relay does not require authentication.
   Client has an AuthenticationCertificate
   Using localhost. Parent Relay selected: **YOUR_RELAY**. at: 192.168.1.3:52311 on: IPV4 (Using setting IPV4ThenIPV6)

By default a client will perform a relay select every 6 hours and that is probably what you are seeing in the logs. If your relay is not reporting in to the console (or is greyed out) it could be for a few reasons. Anything else in the client log that indicates any issues? HTTP errors, timeouts, etc.?

dbatista 2021-01-06 15:37:39 UTC #3

Hey, thanks for your help.

I set verbose debugging on the client relay and I found the following:

Wed, 06 Jan 2021 16:12:13 +0000 Relay Selection: Gather URL: http://ROOTSERVER:52311/cgi-bin/bfgather.exe/actionsite.
Wed, 06 Jan 2021 16:12:13 +0000 Relay Selection: Last selection time: 15:45:25.
Wed, 06 Jan 2021 16:12:13 +0000 Relay Selection: Need Relay selection: true - Reason: Configured interval reached.
Wed, 06 Jan 2021 16:12:13 +0000 Relay Selection: Host selector entry: ROOTSERVER. .
Wed, 06 Jan 2021 16:12:13 +0000 DebugMessage Beginning Relay Select
Wed, 06 Jan 2021 16:12:13 +0000 VerboseMessage RelevanceSubstitution::EvaluateRelevanceAsString() entering, input = exists main gather service
Wed, 06 Jan 2021 16:12:13 +0000 VerboseMessage RelevanceSubstitution::EvaluateRelevanceAsString() evaluating the expression
Wed, 06 Jan 2021 16:12:14 +0000 VerboseMessage RelevanceSubstitution::EvaluateRelevanceAsString() exiting.
Wed, 06 Jan 2021 16:12:14 +0000 VerboseMessage RelevanceSubstitution::EvaluateRelevanceAsString() entering, input = exists relay service
Wed, 06 Jan 2021 16:12:14 +0000 VerboseMessage RelevanceSubstitution::EvaluateRelevanceAsString() evaluating the expression
Wed, 06 Jan 2021 16:12:14 +0000 VerboseMessage RelevanceSubstitution::EvaluateRelevanceAsString() exiting.
Wed, 06 Jan 2021 16:12:14 +0000 Relay Selection: Exists main gather service.
Wed, 06 Jan 2021 16:12:14 +0000 Relay Selection: Starting under Quarantine: false
Wed, 06 Jan 2021 16:12:14 +0000 Relay Selection: For agent with local relay.
Wed, 06 Jan 2021 16:12:14 +0000 DebugMessage GetRelayInfo: checking 'http://127.0.0.1:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=Version’
Wed, 06 Jan 2021 16:12:14 +0000 DebugMessage GetRelayInfo: Valid Relay
Wed, 06 Jan 2021 16:12:14 +0000 Relay Selection: Unable to register with the parent relay until it estabilishes a connection.
Wed, 06 Jan 2021 16:12:14 +0000 DebugMessage Unrestricted mode
Wed, 06 Jan 2021 16:12:14 +0000 DebugMessage Not in grace period
Wed, 06 Jan 2021 16:12:14 +0000 Running Unregistered
Wed, 06 Jan 2021 16:12:14 +0000 DebugMessage Configuring listener without wake-on-lan

Any idea how to solve it?

Cheers

dbatista 2021-01-06 16:07:00 UTC #4

I could make the relay appears again in the console. After some time checking both main server and relay configuration I disabled the _BESRelay_DMZ_ChildEnable on the relay and _BESRelay_DMZ_ParentEnable on the main server.

This relay will be used as internet facing relay. Is it really necessary to configure these options?

dmccalla 2021-01-06 16:54:03 UTC #5

Generally speaking you should not have to use those settings (persistent connection - https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/c_persistenconn2.html) unless you have some firewall constraints that your network team will not address. Without those settings (and you can communicate bi-directionally via TCP 52311 between the two machines) you would just manually point the internet facing relay to another relay on the internal network - which then points to the root server. You can point directly to a root server instead of another relay depending on the size of your environment. Info on manual relay selection can be found here.