Hi All,
Please can you help me as my lot of endpoints are not reporting to Console…i am getting below mentioned error in bigfix client logs:
FAILED to Synchronize - General transport failure. - FILE OPEN (winsock error 4294967291 - gather url -
are you sure the default port 52311 is open and is not being blocked by firewall? and also make sure you add besclient.exe to the exception list.
Can you provide the full error message please? And if there a multiple error messages, please provide those as well?
The client reporting would not have anything to do with a problem with the client gathering, they are two different processes. Reporting (upstream) and gathering (downstream)
@techadmin: Yes, telnet is working on port 52311 and there is no blockage on local/network firewall.
@BigFixNinja: after the error message only gather URL is there and there is no other message. Please suggest something.
You stated the problem was that the client is not reporting to the console. Do you see any reported posted successfully messages within the client log?
For example:
At 03:07:01 -0700 -
Report posted successfullyNo, there is no line like reported successfully.
I reinstalled it on system and started working fine however I am having same problem with multiple systems and I want to correct it rather than reinstallation.
Try doing a restart of the BES Client service. See if a restart of the service resolves the issue versus a full re-install.
Below is the complete error message and BESClient service restart is not fruitful.
Please suggest…
Current Date: October 7, 2016
Client version 9.5.2.56 built for WINVER 6.0 i386 running on WINVER 6.1.7601 x86_64
Current Balance Settings: Use CPU: True Entitlement: 0 WorkIdle: 25 SleepIdle: 460
ICU 54.1 init status: SUCCESS
Agent internal character set: UTF-8
ICU report character set: UTF-8 - Transcoding Disabled
ICU fxf character set: windows-1252 (Latin 1 / Western European) - Transcoding Enabled
ICU local character set: windows-1252 (Latin 1 / Western European) - Transcoding Enabled
At 00:01:50 +0000 -
Report posted successfully
At 00:10:08 +0000 -
Report posted successfully
At 00:25:13 +0000 -
FAILED to Synchronize - General transport failure. - FILE OPEN (winsock error 4294967291 - gather url - http://Win_Bigfix.abc.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://Win_Bigfix.abc.com:52311/cgi-bin/bfgather.exe/actionsite&Time=07Oct00:25:13&rand=1cade12f&ManyVersionSha1=d2b69cd78e6d41cda912cf7b5ed3650822dc3006
At 00:26:38 +0000 -
Report posted successfully
At 00:39:13 +0000 -
Report posted successfully
At 00:47:57 +0000 -
PollForCommands: Requesting commands
PollForCommands: commands to process: 1
At 00:47:58 +0000 -
GatherHashMV command received.
FAILED to Synchronize - General transport failure. - FILE OPEN (winsock error 4294967291 - gather url - http://Win_Bigfix.abc.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://Bigfix.abc.com:52311/cgi-bin/bfgather.exe/actionsite&Time=07Oct00:47:58&rand=d3212c09&ManyVersionSha1=d2b69cd78e6d41cda912cf7b5ed3650822dc3006
At 00:47:59 +0000 -
Processing action site.
At 00:49:00 +0000 -
FAILED to Synchronize - General transport failure. - FILE OPEN (winsock error 4294967291 - gather url - http://Win_Bigfix.abc.com:52311/cgi-bin/bfenterprise/BESGatherMirror.exe?url=http://Bigfix.abc.com:52311/cgi-bin/bfgather.exe/actionsite&Time=07Oct00:49:00&rand=59a86030&ManyVersionSha1=d2b69cd78e6d41cda912cf7b5ed3650822dc3006
At 00:51:20 +0000 -
Beginning Relay Select
At 00:51:23 +0000 -
RegisterOnce: Attempting secure registration with 'https://Win_Bigfix.abc.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=9.5.2.56&Body=8861122&SequenceNumber=961&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://Bigfix.abc.com%3a52311&AdapterInfo=00-50-56-aa-22-f8_10.50.30.0%2f24_10.50.30.168_0&AdapterIpv6=00-50-56-aa-22-f8%5efe80%3a%3a9c1e%3aa8d9%3af89c%3add91%2f64_0’
Unrestricted mode
Configuring listener without wake-on-lan
Registered with url 'https://Win_Bigfix.abc.com:52311/cgi-bin/bfenterprise/clientregister.exe?RequestType=RegisterMe60&ClientVersion=9.5.2.56&Body=8861122&SequenceNumber=961&MinRelayVersion=7.1.1.0&CanHandleMVPings=1&Root=http://Bigfix.abc.com%3a52311&AdapterInfo=00-50-56-aa-22-f8_10.50.30.0%2f24_10.50.30.168_0&AdapterIpv6=00-50-56-aa-22-f8%5efe80%3a%3a9c1e%3aa8d9%3af89c%3add91%2f64_0’
Registration Server version 9.5.2.56 , Relay version 9.5.2.56
Relay does not require authentication.
Client has an AuthenticationCertificate
Relay selected: Win_Bigfix.abc.com. at: 10.50.30.245:52311 on: IPV4 (Using setting IPV4ThenIPV6)
At 00:51:24 +0000 -
[ThreadTime:00:51:23] ShutdownListener
[ThreadTime:00:51:23] SetupListener success: IPV4/6.
Can you access the BES relay diagnostic running on the root server from a browser session on the client in question? For example, on the client having these issues open Chrome and enter http://Win_Bigfix.abc.com:52311/rd and let me know the result.
We are seeing similar issues on agents upgraded to 9.5.2.56, in particular on 32-bit POSReady 7 (Win 7 embedded) OS. Either the client shuts itself down, doesn’t respond to actions even when it is ‘reporting’, or generates app crash events in the Windows event log.
One curious client log snip:
At 07:54:59 -0800 -
ActionLogMessage: (action:2130716571) ending action
Starting self imposed client restart.
In this case, the action did not specify any post-action behavior. I’ve never seen “Starting self imposed client restart.” in a client log before.
I tried upgrading a client to 9.5.3.211, but had the same, but inconsistent, results.
A representative app crash event:
Faulting application name: BESClient.exe, version: 9.5.3.211, time stamp: 0x57f5dba1
Faulting module name: BESClient.exe, version: 9.5.3.211, time stamp: 0x57f5dba1
Exception code: 0xc0000005
Fault offset: 0x0023eeab
Faulting process id: 0x1bc0
Faulting application start time: 0x01d223d69861c454
Faulting application path: C:\Program Files\BigFix Enterprise\BES Client\BESClient.exe
Faulting module path: C:\Program Files\BigFix Enterprise\BES Client\BESClient.exe
Report Id: 0affe30a-8fca-11e6-91b2-001a643cc18e
We have a PMR sev 1 open on this issue.
This should make it back to you through the PMR but there are several reasons the client will restart itself when it has to update the masthead of the deployment (which that action was doing) so it is to be expected. The self imposed restart is where the client MUST reload the masthed from the beginning to continue. One example is when it gets FIPS turned on by the masthead.
We have had this issue also, with our AIX clients not reporting. I have corrected the issues, by either restarting the system, just restarting the client, or reinstalling the client completely.
Another thing we have done to try to alleviate this issue, is to set those systems having issues to report by TCPIP instead of UDP. We have them to check in every 30 minutes. We only have about 40 servers in the DMZ (Windows, Linux, and AIX) though.
Feedback from L3 on our PMR for this issue is that 9.5.2 client (also observed 9.5.3) can sometimes crash due to a
not initialized variable. There is suspected AV or white-listing interference as well. IBM has APAR IV90303 open for this issue.
A beta client build provided by dev appears to resolve these crashes by working around AV-type contention and properly initializing variables.
1 Like
9.5.2 and 9.5.3 clients have a bug when interacting with AV or security/whitelisting products where the agent can crash if it is denied inspection of AV/security products. APAR IV90303 is planned to be included in 9.5.4.
I’d suggest you open a new thread specific to your issue rather than using a 1 year old post for a different issue and platform. There are a lot of issues that can cause a client to show grey
1 Like