CB Response: When attempting the Live Response feature `GoLive`, the cursor hangs is in a constant spinning state
search cancel

CB Response: When attempting the Live Response feature `GoLive`, the cursor hangs is in a constant spinning state

book

Article ID: 285921

calendar_today

Updated On:

Products

Carbon Black EDR (formerly Cb Response)

Issue/Introduction

  • Errors seen in /var/log/cb/liveresponse/startup.log 
2018-12-18 15:14:13 +0000] [14507] [INFO] Starting gunicorn 19.9.0 
[2018-12-18 15:14:13 +0000] [14507] [INFO] Listening at: http://[::]:5600 (14507) 
[2018-12-18 15:14:13 +0000] [14507] [INFO] Using worker: gevent 
[2018-12-18 15:14:13 +0000] [14519] [INFO] Booting worker with pid: 14519 
------------ Launching PID(14519) @ 2018-12-18 15:14:16.173189 ----------------------- 
Traceback (most recent call last): 
File "src/gevent/greenlet.py", line 716, in gevent._greenlet.Greenlet.run 
File "/usr/share/cb/virtualenv/lib/python2.7/site-packages/cb/liveresponse/session.py", line 103, in purge_expired_sessions 
File "/usr/lib64/python2.7/logging/__init__.py", line 1186, in warning 
self._log(WARNING, msg, args, **kwargs) 
File "/usr/lib64/python2.7/logging/__init__.py", line 1293, in _log 
self.handle(record) 
File "/usr/lib64/python2.7/logging/__init__.py", line 1303, in handle 
self.callHandlers(record) 
File "/usr/lib64/python2.7/logging/__init__.py", line 1343, in callHandlers
  • Restarting the Cb services has no effect (where this action would normally clear the condition in other circumstances)

Environment

  • CB Response Server: 6.0.1 and Higher

Cause

The purge of expired CB Live Response sessions fails while attempting to log message

Resolution

Defect CB-20632 was created and is slated to be fixed in Cb Response 6.2.5.