Error ./manage start --logs- MAC machine
- Dominant language
- Python
- Stars
- 170
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
ledger 2: state root DfNLmH4DAHTKv63YPFJzuRdeEtVwF5RtVnvKYHd8iLEA
node2_1 | 2022-02-16 18:14:43,258|INFO|ledgers_bootstrap.py| initialized state for ledger 1: state root GWEizEWQdGH5QFdxRpoQGvPR42zSUEJoFkQKGBHiNDbM
node2_1 | 2022-02-16 18:14:43,259|INFO|motor.py|Node2 changing status from stopped to starting
node2_1 | Operation not permitted (bundled/zeromq/src/thread.cpp:277)
node2_1 | qemu: uncaught target signal 6 (Aborted) - core dumped
node2_1 | ./scripts/start_node.sh: line 27: 9 Aborted start_indy_node "Node""$NODE_NUM" $HOST $NODE_PORT $HOST $(( NODE_PORT + 1 ))
von_node2_1 exited with code 134
Want to see the scrolling container logs? Run "./manage logs"
Contributor guide
Research direction
Start with ./manage start --logs and inspect scripts/start_node.sh around line 27, where start_indy_node aborts under qemu in the reported MAC-machine run. Review the surrounding ledgers_bootstrap.py and motor.py startup logs, then verify that the node containers start without the ZeroMQ permission error and exit code 134.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100