aries-cloudagent-python: Running the demo on a raspberry pi - agent not starting

A user reporting running ACA-Py demo on a raspberry pi. The user has the demo running on a regular system, but it’s failing to start up on the Pi, with the following details:

First I started a von-network on my PC (raspberry pi was in the same network) following the guide here: https://github.com/bcgov/von-network#running-the-network-locally

Then on pi in Aries-cloud-agent directory I execute:

python3.6 -m venv env
source env/bin/activate
pip3 install wheel
pip3 install -e .
pip3 install prompt_toolkit pygments python3-indy
cd demo
LEDGER_URL=http://192.168.31.186:9000 python3.6 -m runners.faber -p 8020

On the Pi I run:

LEDGER_URL=http://192.168.31.186:9000 python3.6 -m runners.faber -p 8020

Resulting Log:

#1 Provision an agent and wallet, get back configuration details
Faber | Registering Faber Agent with seed d_000000000000000000000000459545
Faber | Got DID: UyUZWxhdbonVygFjy1ZLWy
Faber |
Faber | Shutting down
Faber | Exited with return code 0
Traceback (most recent call last):
File "/usr/local/lib/python3.6/runpy.py", line 193, in runmodule_as_main
"__main__", mod_spec)
File "/usr/local/lib/python3.6/runpy.py", line 85, in runcode
exec(code, run_globals)
File "/home/pi/aries-cloudagent-python/demo/runners/faber.py", line 248, in <module>
asyncio.get_event_loop().run_until_complete(main(args.port, args.timing))
File "/usr/local/lib/python3.6/asyncio/base_events.py", line 468, in run_until_complete
return future.result()
File "/home/pi/aries-cloudagent-python/demo/runners/faber.py", line 117, in main
await agent.start_process()
File "/home/pi/aries-cloudagent-python/demo/runners/support/agent.py", line 286, in start_process
await self.detect_process()
File "/home/pi/aries-cloudagent-python/demo/runners/support/agent.py", line 373, in detect_process
raise Exception(f"Timed out waiting for agent process to start")
Exception: Timed out waiting for agent process to start

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 22 (13 by maintainers)

Commits related to this issue

Most upvoted comments

The timestamp error is fixed with https://github.com/hyperledger/indy-sdk/pull/2210 The issue was a wrong cast in the python wrapper. CC @arner