IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

CB Response: After Upgrading To 6.2.2, CB Threat Intel Is No Longer Connecting

CB Response: After Upgrading To 6.2.2, CB Threat Intel Is No Longer Connecting

Environment

  • CB Response Server: 6.2.2

Symptoms

  • On the server dashboard 'Server Communication Status' is red and shows an error code of 605.
  • Error in :/var/log/cb/allianceclient/allianceclient.log
<err> cb.alliance.community -
...urlopen
File "/opt/jenkins/build/workspace/build-cbent-signed-docker-staging/code/coreservices/src/cb/utils/requests/packages/urllib3/connectionpool.py", line 545, in urlopen
File "/opt/jenkins/build/workspace/build-cbent-signed-docker-staging/code/coreservices/src/cb/utils/requests/packages/urllib3/connectionpool.py", line 324, in _get_conn
File "/opt/jenkins/build/workspace/build-cbent-signed-docker-staging/code/coreservices/src/cb/utils/requests/packages/urllib3/connectionpool.py", line 734, in _new_conn
File "/opt/jenkins/build/workspace/build-cbent-signed-docker-staging/code/coreservices/src/cb/utils/requests/packages/urllib3/connectionpool.py", line 698, in _prepare_conn
File "/opt/jenkins/build/workspace/build-cbent-signed-docker-staging/code/coreservices/src/cb/utils/requests/packages/urllib3/connectionpool.py", line 152, in connect
File "/opt/jenkins/build/workspace/build-cbent-signed-docker-staging/code/coreservices/src/cb/utils/requests/packages/urllib3/connectionpool.py", line 110, in _challenge_response_tunnel
AttributeError: VerifiedHTTPSConnection instance has no attribute '_set_hostport'
  • Latest values in the postgres table, allianceclient_comm_history show an http_status of 605
  • Alliance Client Proxy is configured in cb.conf in the field AllianceClientProxyUrl

Cause

Due to changes from Python 2.6 to 2.7, attempting to connect to the Alliance backend uses an attribute that no longer exists. This issue is tracked with the ID CB-19556.

Resolution

This issue is resolved in CB Response Server 6.2.3.

Related Content


Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎09-09-2020
Views:
518
Contributors