BF client not reporting

Hi,

I have two Linux endpoints (besclient) one is reporting and i can see in BF Console other is not reportingThe one that is not reporting , besclient.config file was 94 lines , the one that is reporting has 1104 linesI have tried copying the working server besclient.config file to the server that is not working since both are located in the same environment and same specification and have restarted the service but it is still not showing in console , any advise ?

 RegisterOnce: Attempting secure registration with 'https://AAAAAAAA.BBBBB.Local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=544046799&SequenceNumber=0&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAA.local%3a52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0'
   Response: Client Signature Required
   RegisterOnce: Server expects a signature.
   Resetting computer ID
At 23:25:57 +1200 -
   RegisterOnce: Attempting secure registration with 'https://AAAAAAAA.BBBBB.Local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=0&SequenceNumber=1&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAA.local%3a52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0'
At 23:25:58 +1200 -
   Unrestricted mode
   Scheduling client reset; Computer id changed to 1083435350518
   Configuring listener without wake-on-lan
   Registered with url 'https://AAAAAAAA.BBBBB.Local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=0&SequenceNumber=1&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAA.local%3a52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0'
   Registration Server version 10.0.6.84 , Relay version 10.0.6.84
   Relay does not require authentication.
At 23:26:16 +1200 -
   Completed automatic client authentication key exchange.
   Client has an AuthenticationCertificate
   Created mailboxsite and marking to gather
   RegisterOnce: Client is entitled to open a persistent connection.
   Relay selected: AAAAA.BBBBBB.Local. at: 10.178.1.52:52311 on: IPV4 (Using setting IPV4ThenIPV6)
   Client resetting
   Configuring listener without wake-on-lan
   Unrestricted mode
   Created mailboxsite and marking to gather
   Entering Service Loop.
   Starting Service Loop.
   A2AServer::Start().
   Beginning Relay Select      

At 23:31:32 +1200 -
RegisterOnce: Attempting secure registration with 'https://bigfix.AAAAAAA.local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterM
e60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=6&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAA.local%3a52311&Adapt
erInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0’
RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://bigfix.AAAAAAA.loca
l:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=6&MinRelayVersion=7.
1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAAAA.local%3a52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0
At 23:32:04 +1200 -
RegisterOnce: Attempting secure registration with 'https://bigfix.AAAAAA.local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterM
e60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=7&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAAAA.local%3a52311&Adapt
erInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0’
At 23:32:05 +1200 -
RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://bigfix.AAAAAA.local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=7&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAAAA.local%3A52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2F24_172.29.62.43_0
Unrestricted mode
Configuring listener without wake-on-lan
[ThreadTime:23:32:05] ShutdownListener
[ThreadTime:23:32:05] Setup Listener success: reusing existing socket.
At 23:37:48 +1200 -
Beginning Relay Select
RegisterOnce: Attempting secure registration with 'https://bigfix.AAAAAAAA.local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=8&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAAAA.local%3A52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2F24_172.29.62.43_0’
RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://bigfix.AAAAAAAA.local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=8&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAA.local%3A52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2F24_172.29.62.43_0
At 23:38:29 +1200 -

The “BAD SERVERNAME” messages indicate the client can’t resolve the relay hostnames. It’s likely either a DNS client config issue, or someone added relay entries to the /etc/hosts file one one client but not the other, something like that in name resolution.

Thanks for the reply.

yes i can see but where i need to add the correct Relay server , I tried to copy the whole besclient.config file from the working server to the server that is not reporting but it failed.

any specific variable in besclient.config that i need to replace this value ?

Successful 

   RegisterOnce: Attempting secure registration with 'https://SUCCESSFUL.SERVER.Cool:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=544046799&SequenceNumber=1110&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAA.local%3a52311&AdapterInfo=00-50-56-86-2c-76_10.164.1.0%2f24_10.164.1.99_0&AdapterIpv6=00-50-56-86-2c-76%5efe80%3a%3a250%3a56ff%3afe86%3a2c76%2f64_0'
   RegisterOnce: Client is entitled to open a persistent connection.

Failed server

RegisterOnce: GetURL failed - General transport failure. - BAD SERVERNAME (winsock error 4294967290 - registration url - http://bigfix.AAAAAA.local:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=10.0.6.84&Body=1087050518&SequenceNumber=10&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://bigfix.AAAAAAA.local%3a52311&AdapterInfo=00-50-56-8f-51-63_172.29.62.0%2f24_172.29.62.43_0

No, the name resolution is a system-wide configuration, not part of BigFix at all.

The machine cannot resolve the Relay names to IP addresses, which is usually done via DNS or /etc/hosts file.

yes agreed, but the relay server in working endpoint I took and add to the new besclient.config file in not working endpoint and started the besclient service
when the service start it still points to the old root server path which is not reachable.

I am creating this besclient.conf file as below any advise how to fix this ?

[Software\BigFix\EnterpriseClient]
EnterpriseClientFolder = /opt/BESClient

[Software\BigFix\EnterpriseClient\GlobalOptions]
StoragePath = /var/opt/BESClient
LibPath = /opt/BESClient/BESLib

[Software\BigFix\EnterpriseClient\Settings\Client\__RelayServer1]
value                          = http://SERVER1.AAAAAA.NET:52311/bfmirror/downloads/

[Software\BigFix\EnterpriseClient\Settings\Client\__RelayServer2]
value                          = http://SERVER2.AAAAAA.LoCaL:52311/bfmirror/downloads/

[Software\BigFix\EnterpriseClient\Settings\Client\__RelaySelect_Automatic]
value                          = 0

What happens on the broken client when you try to ping the relay by name?

both __RelayServer1 and __RelayServer2 are pingable but when I try to start the service after adding above lines it doesnt contact these RelayServer it goes back to root and gives BAD SERVERNAME

Hi,

Try the following:

  1. Stop the BigFix client service.
  2. Update the values for __RelayServer1 and __RelayServer2 on the config file.
  3. Delete the __BESData folder
  4. Start the client back up.

Check if the config file retains the relay values after the restart.

just to be sure __BESData will get recreated ?

also can you confirm above configuration is correct to create the besclient.config file ? the one i put in my earlier message ? Thanks

Yes, __BESData will be regenerated once the service is started. Also, the config file looks correct.

Thanks it seems to be working , but I am not able to see yet in the console , i guess it will take few minutes, as of now from the logs i can see reported successfully and also it is pointing to Relay servers I added in the config file, I will post the status in a while :slight_smile:

1 Like

@anademayo , it is showing as “Report posted successfully” but I am unable to see this host in console, do i need to run any discovery on console to identify this host ?

Are you a Master Operator? If not, it may take some time for the computer to subscribe to you as an operator, (assuming you are correctly assigned as an operator on it), and the computer won’t be visible to you until then.

I am certainly not the master operator :slight_smile: may I know how many minutes/hours it might take to show up before i give up on it ?

Looking at below log can you confirm if it is working as expected ?

   Relevant - BSL - Windows update Cumulative updates (fixlet:99238)
   Relevant - Datacom - DOME Integration (fixlet:9535)
   Relevant - Vulnerability Scan Results: CVE-2021-44228 Log4j (fixlet:83710)
   Relevant - Vulnerability Scan: Log4j CVE-2021-44228 (fixlet:83708)
   Relevant - BES Client Setting: Change CID (fixlet:65942)
   Relevant - Datacom - Hardware analysis (fixlet:52725)
   Relevant - Remove BigFix reboot registry (fixlet:5106)
   BackgroundAdviceEvaluation::FinishDataLoop side line file Fixlet 4574.fxf
   Relevant - Datacom - Client Loop Cycle Time (fixlet:45118)
   Relevant - Datacom - BES Client Info - Universal (fixlet:45106)
   BackgroundAdviceEvaluation::FinishDataLoop side line file Fixlet 44271.fxf
   BackgroundAdviceEvaluation::FinishDataLoop side line file Fixlet 39973.fxf
   Relevant - Persistent Client Connection Servers Only (fixlet:29039)
   Relevant - Post-Patching configuration  (fixlet:29035)
   Relevant - Pre-Patching configuration  (fixlet:26879)
   BackgroundAdviceEvaluation::FinishDataLoop side line file Fixlet 26751.fxf
   BackgroundAdviceEvaluation::FinishDataLoop side line file Fixlet 140458.fxf
   Relevant - Custom File Search (fixlet:118931)
At 02:43:02 +1200 -
   Report posted successfully
At 02:56:01 +1200 -
   Report posted successfully

Yes, and if your rights are setup correctly at the server, you’ll eventually see some ‘administrator add’ commands in the client log. You should see it in the Console after the next report after your account is added.

You won’t see the administrator names in the log, though, they’ll all be like “op_101” with different numbers.

2 Likes

Thanks @JasonWalker , @anademayo its working :slight_smile:

1 Like