Unable to start bpa

[ghost]

Hello team,

I am starting the bpa using the link - https://github.com/hyperledger-labs/business-partner-agent/tree/main/scripts#tldr

it gives me a permission denied error while starting the bpa-agent_1
it says that it can't open the file acapy-static-args.yml
Can you please help me as to how I can solve this?

[etschelp]

did you change the aca-py version to 0.8 or greater?

[ghost]

No

More precisely the error is -
scripts-bpa-agent1-1 | aca-py start: error: Unable to open config file: acapy-static-args.yml. Error: Permission denied

The docker image of aca-py is -
bcgovimages/aries-cloudagent py36-1.16-1_0.7.5 9727d293239d 7 months ago 451MB

In the docker-compose.yml , the version is specified as below -
bpa-agent1:
image: bcgovimages/aries-cloudagent:py36-1.16-1_0.7.5

[etschelp]

What OS are you running?
Are you using docker or something else?
Is your user account in the docker group?
Are you running the docker command with another user than the one who did the git clone?
If you run ls -la scripts all files need to have at least the read permission set for user/group/other

[ghost]

Thanks,

I changed the permissions of the file.
It starts now.

But now, as I try to sign in with the given username and password, it neither signs me in nor it gives an error.
How should i proceed further?

[etschelp]

I guess you are trying to log in from chrome or a chrome based browser. Please see this section of the setup doc: https://github.com/hyperledger-labs/business-partner-agent/tree/main/scripts#setup-security

[ghost]

Thanks a lot,

I tried from firefox, and it worked.

Now, it is starting and I am able to login into it.

But sometimes when i stop and start it again - acapy gives the following error :-

scripts-bpa-agent1-1 | aries_cloudagent.ledger.error.LedgerTransactionError: Ledger request error

and then it shuts down and so the bpa shuts down.

Is it due to network issues? What can be done?

[ghost]

Hi @etschelp , any update on this?

[etschelp]

If you take a look into the gesesis-transaction-list.yml you see what ledgers are configured. If any one of those ledgers is slow to respond this can happen. This file is populated for demo reasons and there is no guarantee that these ledgers are running 100% of the time, or respond fast enough on each request. So you either have to run your own indy ledger instance, or pick another one that satisfies your SLA requirements.