Bluefors agent crashing with Bluefors PC windows directory mounted
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17
- Forks
- 20
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 2
Description
I've been running into this issue sporadically ; the BlueforsAgent is crashing with this error;
2021-08-03T02:02:10+0000 The Bluefors Agent cannot process error logs. Not publishing.
2021-08-03T11:36:55+0000 The Bluefors Agent cannot process error logs. Not publishing.
2021-08-03T11:36:55+0000 The Bluefors Agent cannot process error logs. Not publishing.
2021-08-03T13:00:17+0000 acq:0 Crash in thread: [Failure instance: Traceback: <class 'ValueError'>: not enough values to unpack (expected 3, got 1)
/usr/lib/python3.8/threading.py:932:_bootstrap_inner
/usr/lib/python3.8/threading.py:870:run
/usr/local/lib/python3.8/dist-packages/twisted/_threads/_threadworker.py:47:work
/usr/local/lib/python3.8/dist-packages/twisted/_threads/_team.py:181:doWork
--- <exception caught here> ---
/usr/local/lib/python3.8/dist-packages/twisted/python/threadpool.py:238:inContext
/usr/local/lib/python3.8/dist-packages/twisted/python/threadpool.py:254:<lambda>
/usr/local/lib/python3.8/dist-packages/twisted/python/context.py:118:callWithContext
/usr/local/lib/python3.8/dist-packages/twisted/python/context.py:83:callWithContext
bluefors_log_tracker.py:488:start_acq
bluefors_log_tracker.py:385:read_and_publish_logs
bluefors_log_tracker.py:227:_parse_single_value_log
]
2021-08-03T13:00:17+0000 acq:0 Status is now "done".
I'm running the OCS dockers on a linux server and mounting the windows Bluefors log directory on that server, so that may be playing a role. Zach Huber at Cornell who is also running the Bluefors Agent this way (with the windows log directory mounted on linux) reports similar crashes. Restarting the agent seems to get things going again. Thanks! Shawn
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in bluefors_log_tracker.py at start_acq, read_and_publish_logs, and _parse_single_value_log, which appear in the traceback. Reproduce the Bluefors Agent with the Windows log directory mounted on Linux and inspect how the log entry causing the unpacking error is handled. Done means the agent continues processing logs without crashing in this setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100