swcurran
commented
1 year ago Trying…I’ll let you know what I find.
Closed lethal233 closed 10 months ago
swcurran
commented
1 year ago Trying…I’ll let you know what I find.
swcurran
commented
1 year ago Looks like an issue with MacOS, as it works fine on Linux. The “easiest" workaround to try is to:
pushd services/von-network/.build/von-network/managestat -c '%a’ to stat -f ‘%A’popd to return to the root of AATHIf that works, you are good to go. Let us know.
@WadeBarnes — FYI
I’ll open an issue in von-network. The problem is that the stat command differences across MacOS and GNU (on Linux and Windows) implementations. As noted in the error above, the -c option does not work on MacOS, but does with the GNU version. This is the start of the man page on Linux:
STAT(1)
NAME
stat - display file or file system status
SYNOPSIS
stat [OPTION]... FILE...
DESCRIPTION
Display file or file system status.
Mandatory arguments to long options are mandatory for short options too.
-L, --dereference
follow links
-f, --file-system
display file system status instead of file status
-c --format=FORMAT
use the specified FORMAT instead of the default; output a newline after each use of FORMAT
--printf=FORMAT
like --format, but interpret backslash escapes, and do not output a mandatory trailing newline; if you want a newline, include \n in FORMAT
-t, --terse
print the information in terse form
--help display this help and exit
--version
output version information and exit
lethal233
commented
1 year ago Thank you for your instant response! But after trying, I found that I cannot run this script.
Seems that there is still the same problem, here is the full logs:
~/Documents/aries-agent-test-harness main
base ❯ ./manage build -a acapy -a javascript
Agents to build: acapy javascript
Backchannel Folder: aries-backchannels/acapy
Building acapy-agent-backchannel ...
[+] Building 234.3s (21/21) FINISHED
=> [internal] load build definition from Dockerfile.acapy 0.0s
=> => transferring dockerfile: 1.19kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 306B 0.0s
=> [internal] load metadata for docker.io/library/python:3.9-slim-bullse 1.8s
=> [internal] load build context 0.0s
=> => transferring context: 145.35kB 0.0s
=> https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 1.1s
=> [ 1/15] FROM docker.io/library/python:3.9-slim-bullseye@sha256:e71b40 2.2s
=> => resolve docker.io/library/python:3.9-slim-bullseye@sha256:e71b4007 0.0s
=> => sha256:e71b400764bc7c1619f95af370d899f17878a3a79c1 1.86kB / 1.86kB 0.0s
=> => sha256:94dfb9048439d49490de0a00383e2b0183676cbd56d 1.37kB / 1.37kB 0.0s
=> => sha256:e95114f5f7560daad19f0be9596cd56822ca28db461 6.91kB / 6.91kB 0.0s
=> => sha256:9d21b12d5fab9ab82969054d72411ce627c209257 31.42MB / 31.42MB 0.9s
=> => sha256:40b9e4b957eeed658ed5e23cb877a51446a67347635 1.08MB / 1.08MB 0.3s
=> => sha256:f1295b4dd28cba1b9de93b285fd3f3e8b84202b7e 11.05MB / 11.05MB 0.3s
=> => sha256:5f0c68ee6980119b583e0c0e001d06c87385dd999b0c697 245B / 245B 0.4s
=> => sha256:36ad44994e4aa3c86f03cba2bb2cdf241489524f076 3.14MB / 3.14MB 0.6s
=> => extracting sha256:9d21b12d5fab9ab82969054d72411ce627c209257df64b60 0.5s
=> => extracting sha256:40b9e4b957eeed658ed5e23cb877a51446a673476353405c 0.0s
=> => extracting sha256:f1295b4dd28cba1b9de93b285fd3f3e8b84202b7e1e5a855 0.2s
=> => extracting sha256:5f0c68ee6980119b583e0c0e001d06c87385dd999b0c6977 0.0s
=> => extracting sha256:36ad44994e4aa3c86f03cba2bb2cdf241489524f076618e2 0.1s
=> [ 2/15] RUN apt-get update && apt-get install -y git gnupg2 softw 99.6s
=> [ 3/15] RUN mkdir -p /aries-backchannels 0.2s
=> [ 4/15] WORKDIR /aries-backchannels 0.0s
=> [ 5/15] ADD https://github.com/stedolan/jq/releases/download/jq-1.6/j 0.0s
=> [ 6/15] RUN chmod +x ./jq 0.2s
=> [ 7/15] COPY python/requirements.txt python/ 0.0s
=> [ 8/15] COPY acapy/requirements-latest.txt acapy/ 0.0s
=> [ 9/15] RUN pip install -r acapy/requirements-latest.txt && pip ins 125.0s
=> [10/15] COPY python python 0.0s
=> [11/15] COPY acapy acapy 0.0s
=> [12/15] COPY data ./ 0.0s
=> [13/15] RUN mkdir -p ./bin 0.2s
=> [14/15] RUN ln -s /usr/local/bin/aca-py ./bin/aca-py 0.3s
=> [15/15] RUN ./bin/aca-py --version > ./acapy-version.txt 3.7s
=> exporting to image 0.9s
=> => exporting layers 0.9s
=> => writing image sha256:37e62d842d110d7e9b60509abb8bf6827824b35c37c48 0.0s
=> => naming to docker.io/library/acapy-agent-backchannel 0.0s
Backchannel Folder: aries-backchannels/javascript
Building javascript-agent-backchannel ...
[+] Building 340.2s (18/18) FINISHED
=> [internal] load build definition from Dockerfile.javascript 0.0s
=> => transferring dockerfile: 1.44kB 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 72B 0.0s
=> [internal] load metadata for docker.io/library/ubuntu:20.04 1.8s
=> [base 1/8] FROM docker.io/library/ubuntu:20.04@sha256:c9820a44b950956 1.1s
=> => resolve docker.io/library/ubuntu:20.04@sha256:c9820a44b950956a790c 0.0s
=> => sha256:14be0685b7682b182af5b862c9638cb1cb4ca1a70bd 2.30kB / 2.30kB 0.0s
=> => sha256:01085d60b3a624c06a7132ff0749efc6e6565d9f2 27.51MB / 27.51MB 0.6s
=> => sha256:c9820a44b950956a790c354700c1166a7ec648bc0d2 1.13kB / 1.13kB 0.0s
=> => sha256:8c38f4ea0b178a98e4f9f831b29b7966d6654414c1dc008 424B / 424B 0.0s
=> => extracting sha256:01085d60b3a624c06a7132ff0749efc6e6565d9f2531d768 0.4s
=> [internal] load build context 0.0s
=> => transferring context: 67.75kB 0.0s
=> [base 2/8] RUN apt-get update -y && apt-get install -y software 133.4s
=> [base 3/8] RUN apt-key adv --keyserver keyserver.ubuntu.com --recv-ke 3.1s
=> [base 4/8] RUN add-apt-repository "deb https://repo.sovrin.org/sdk/d 12.9s
=> [base 5/8] RUN curl -sL https://deb.nodesource.com/setup_18.x | bash 21.0s
=> [base 6/8] RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | ap 2.9s
=> [base 7/8] RUN apt-get update -y && apt-get install -y --allow-unaut 28.5s
=> [base 8/8] RUN apt-get install -y --no-install-recommends yarn 6.8s
=> [final 1/5] WORKDIR /src 0.0s
=> [final 2/5] COPY javascript/server/package.json package.json 0.0s
=> [final 3/5] RUN yarn install 122.6s
=> [final 4/5] COPY javascript/server . 0.0s
=> [final 5/5] COPY javascript/ngrok-wait.sh ./ngrok-wait.sh 0.0s
=> exporting to image 5.8s
=> => exporting layers 5.8s
=> => writing image sha256:943640393f8735a7f29749673b211792bef2ce700cdf2 0.0s
=> => naming to docker.io/library/javascript-agent-backchannel 0.0s
Building aries-test-harness ...
[+] Building 37.0s (11/11) FINISHED
=> [internal] load build definition from Dockerfile.harness 0.0s
=> => transferring dockerfile: 386B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 185B 0.0s
=> [internal] load metadata for docker.io/library/python:3.7-buster 1.7s
=> [1/6] FROM docker.io/library/python:3.7-buster@sha256:2539f956bcccbac 9.8s
=> => resolve docker.io/library/python:3.7-buster@sha256:2539f956bcccbac 0.0s
=> => sha256:65f08bc4dfb68700010a2ea85fd385de826f624ede6 2.01kB / 2.01kB 0.0s
=> => sha256:58b098d18ab274615169f744c52967dd773a1364145 8.12kB / 8.12kB 0.0s
=> => sha256:ac8bb7e1a32398e26c129ce64e2ddc3e7ec6c34d9 50.45MB / 50.45MB 1.0s
=> => sha256:2539f956bcccbac5e4a48ebdafbbbfbd26b4ab56e65b960 988B / 988B 0.0s
=> => sha256:3b1c264c0ad4598c25048a6dbd3030086cc5c7400 17.58MB / 17.58MB 2.2s
=> => sha256:b1e7e053c9f6f57c6d95002167a6d57aed6aacf04 51.87MB / 51.87MB 2.8s
=> => sha256:a2e1e233599c00054fb839db78b4d42e6f12f36 191.88MB / 191.88MB 5.9s
=> => extracting sha256:ac8bb7e1a32398e26c129ce64e2ddc3e7ec6c34d93424b24 1.2s
=> => sha256:0ebfe287e9761b9b7dd1703470ff3473a62fe75238f 6.15MB / 6.15MB 3.0s
=> => extracting sha256:3b1c264c0ad4598c25048a6dbd3030086cc5c74000e11d04 0.2s
=> => extracting sha256:b1e7e053c9f6f57c6d95002167a6d57aed6aacf04dd2f8e6 1.2s
=> => sha256:d8de4b0f984f47161a06a8314ceed5b0257f03a7f 16.97MB / 16.97MB 3.9s
=> => sha256:1d67c32387a2f0a530a064101b0ce3e7db0e24d28934d17 243B / 243B 3.1s
=> => sha256:a09869dd26ab9ba9444aed8211e150e8b8fc1e1505b 2.85MB / 2.85MB 3.6s
=> => extracting sha256:a2e1e233599c00054fb839db78b4d42e6f12f36b64280aa6 2.6s
=> => extracting sha256:0ebfe287e9761b9b7dd1703470ff3473a62fe75238f3de01 0.1s
=> => extracting sha256:d8de4b0f984f47161a06a8314ceed5b0257f03a7f4dedd57 0.4s
=> => extracting sha256:1d67c32387a2f0a530a064101b0ce3e7db0e24d28934d172 0.0s
=> => extracting sha256:a09869dd26ab9ba9444aed8211e150e8b8fc1e1505b6735a 0.1s
=> [internal] load build context 0.0s
=> => transferring context: 420.63kB 0.0s
=> [2/6] COPY ./requirements.txt /aries-test-harness/ 0.3s
=> [3/6] WORKDIR /aries-test-harness 0.0s
=> [4/6] RUN pip install -r requirements.txt 12.3s
=> [5/6] RUN echo "==> Install stuff not in the requirements..." 12.7s
=> [6/6] COPY . /aries-test-harness 0.0s
=> exporting to image 0.1s
=> => exporting layers 0.1s
=> => writing image sha256:f77329e2dfd380faf8d12ab047b323e882f62326a1b6b 0.0s
=> => naming to docker.io/library/aries-test-harness 0.0s
~/Documents/aries-agent-test-harness main 10m 15s
base ❯ ./manage run -d acapy -b javascript -t @AcceptanceTest -t ~@wip
Agents to be used:
Acme - acapy
Bob - javascript
Faber - acapy
Mallory - acapy
starting local von-network...
[+] Running 5/5
✘ webserver Error 1.6s
✘ node2 Error 1.6s
✘ node1 Error 1.6s
✘ node3 Error 1.6s
✘ node4 Error 1.6s
Error response from daemon: pull access denied for von-network-base, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Want to see the scrolling container logs? Run "./manage logs"
waiting for ledger to start/respond...........................................................\e[31m
The Indy Ledger failed to start within 60 seconds.
\e[0m
\e[31m
The Indy Ledger is not running.
\e[0mI have followed your steps and changed the manage file, see the screenshot:
And when I run ./manage logs, there is no logs showing up.
swcurran
commented
1 year ago Looks like you are past the first error. Try running ./manage service build von-network, and the run the ./manage run… command.
lethal233
commented
1 year ago After running ./manage service build von-network and ./manage run -d acapy -b javascript -t @AcceptanceTest -t ~@wip, this log shows up. Seems that there are no compatible images with the host platform.
WadeBarnes
commented
1 year ago Same as this issue? https://github.com/hyperledger/aries-agent-test-harness/issues/711
lethal233
commented
1 year ago Same as this issue? #711
Yeah, after exporting the env value I can pull the images in my machine. But the error still exists:
...
[+] Running 3/3
✔ Network docker_tails-server Created 0.2s
✔ Container docker-tails-server-1 Started 1.1s
✔ Container docker-ngrok-tails-server-1 Started 1.2s
waiting for tails server to start.....
waiting for uniresolver to start........................................................\e[31m
Universal Resolver failed to start within 60 seconds.
\e[0m
\e[31m
Universal Resolver is not running.
\e[0mYou're further along now. It's the Universal Resolver that is not starting now.
swcurran
commented
1 year ago Which doesn’t really help… :-(. @nodlesh — any idea why the Universal Resolver is not starting on Mac M1? Is it not supported?
FYI — @nodlesh this issue will help in updating the ReadMe for using M1 Macs….
nodlesh
commented
1 year ago I've actually been starting the Universal Resolver from AATH all day on an M1 Mac. Although in a different context, running agents as a service for AMTH. The only thing I do different on this M1 Mac than any other system is set export DOCKER_DEFAULT_PLATFORM=linux/amd64 before building anything.
I have had the uni-resolver fail to start, but this usually clears it up; ./manage stop. Then do the run command again.
I'll dig in and see if I can reproduce this.
lethal233
commented
1 year ago Which doesn’t really help… :-(. @nodlesh — any idea why the Universal Resolver is not starting on Mac M1? Is it not supported?
FYI — @nodlesh this issue will help in updating the ReadMe for using M1 Macs….
Actually it's Mac M2. I don't know if the newest MacOS has any impact on this. (since I installed the newest Sonoma on my Mac)
lethal233
commented
1 year ago I've actually been starting the Universal Resolver from AATH all day on an M1 Mac. Although in a different context, running agents as a service for AMTH. The only thing I do different on this M1 Mac than any other system is set
export DOCKER_DEFAULT_PLATFORM=linux/amd64before building anything.I have had the uni-resolver fail to start, but this usually clears it up;
./manage stop. Then do the run command again.I'll dig in and see if I can reproduce this.
Yeah, I tried ./manage stop and rerun it again. the uni-resolver is still not running.
nodlesh
commented
1 year ago Can you show us the output from the uni-resolver container starting up? It will be called uni-resolver-web.local in docker desktop.
lethal233
commented
1 year ago here it is:
. ____ _ __ _ _
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/ ___)| |_)| | | | | || (_| | ) ) ) )
' |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot :: (v2.6.2)
2023-07-18T22:48:18,534 INFO [main] o.s.b.StartupInfoLogger: Starting WebUniResolverApplication using Java 11.0.16 on 5b50685ad7a9 with PID 8 (/opt/universal-resolver/uni-resolver-web/uni-resolver-web-0.8.0-exec.jar started by root in /opt/universal-resolver/uni-resolver-web)
2023-07-18T22:48:18,737 DEBUG [main] o.s.b.StartupInfoLogger: Running with Spring Boot v2.6.2, Spring v5.3.14
2023-07-18T22:48:18,742 INFO [main] o.s.b.SpringApplication: The following profiles are active: default
2023-07-18T22:48:28,389 INFO [main] o.e.j.u.l.Log: Logging initialized @27468ms to org.eclipse.jetty.util.log.Slf4jLog
2023-07-18T22:48:29,051 INFO [main] o.s.b.w.e.j.JettyServletWebServerFactory: Server initialized with port: 8080
2023-07-18T22:48:29,067 INFO [main] o.e.j.s.Server: jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 11.0.16+8
2023-07-18T22:48:29,235 INFO [main] o.e.j.s.h.ContextHandler$Context: Initializing Spring embedded WebApplicationContext
2023-07-18T22:48:29,239 INFO [main] o.s.b.w.s.c.ServletWebServerApplicationContext: Root WebApplicationContext: initialization completed in 9812 ms
2023-07-18T22:48:30,599 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:btcr:.+)$' at http://driver-did-btcr:8080/1.0/identifiers/ (http://driver-did-btcr:8080/1.0/properties)
2023-07-18T22:48:30,607 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:sov:(?:(?:\w[-\w]*(?::\w[-\w]*)*):)?(?:[1-9A-HJ-NP-Za-km-z]{21,22}))$' at http://driver-did-sov:8080/1.0/identifiers/ (http://driver-did-sov:8080/1.0/properties)
2023-07-18T22:48:30,610 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:v1:nym:.+)$' at http://uni-resolver-did-v1-driver:8080/1.0/identifiers/ (http://uni-resolver-did-v1-driver:8080/1.0/properties)
2023-07-18T22:48:30,614 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:v1:test:nym:.+)$' at http://uni-resolver-did-v1-driver:8080/1.0/identifiers/ (http://uni-resolver-did-v1-driver:8080/1.0/properties)
2023-07-18T22:48:30,616 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:stack:.+)$' at http://driver-did-stack:8080/1.0/identifiers/ (http://driver-did-stack:8080/1.0/properties)
2023-07-18T22:48:30,618 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:web:.+)$' at http://uni-resolver-driver-did-uport:8081/1.0/identifiers/ (null)
2023-07-18T22:48:30,628 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ethr:.+)$' at http://uni-resolver-driver-did-uport:8081/1.0/identifiers/ (null)
2023-07-18T22:48:30,631 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:eosio:.+)$' at http://eosio-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,635 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:nacl:.+)$' at http://uni-resolver-driver-did-uport:8081/1.0/identifiers/ (null)
2023-07-18T22:48:30,642 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:jolo:.+)$' at http://jolocom-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,645 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:hcr:.+)$' at http://hacera-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,647 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:elem:ropsten:.+)$' at https://ropsten.element.transmute.industries/api/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,649 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:github:.+)$' at https://github-did.com/api/v1/did/$1 (null)
2023-07-18T22:48:30,653 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ccp:.+)$' at http://driver-did-ccp:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,655 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:work:.+)$' at http://work-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,659 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ont:.+)$' at http://ontid-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,661 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:kilt:.+)$' at http://kilt-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,663 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:factom:.+)$' at http://uni-resolver-driver-did-factom:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,665 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:io:.+)$' at http://uni-resolver-driver-did-io:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,668 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:bba:.+)$' at http://bba-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,669 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:schema:.+)$' at http://schema-registry-did-resolver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,671 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ion:(?!test).+)$' at http://driver-did-ion:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,673 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ace:.+)$' at http://ace-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,676 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:gatc:.+)$' at http://gataca-did-resolver-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,678 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:icon:.+)$' at http://driver-did-icon:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,681 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:vaa:.+)$' at http://driver-did-vaa:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,683 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:unisot:.+)$' at http://unisot-did-driver:8080/1.0/identifiers/ (http://unisot-did-driver:8080/1.0/properties)
2023-07-18T22:48:30,685 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:sol:.+)$' at http://driver-did-sol:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,687 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:lit:(?:[1-9A-HJ-NP-Za-km-z]{21,22}))$' at http://driver-did-lit:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,689 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ebsi:.+)$' at https://api.preprod.ebsi.eu/did-registry/v3/identifiers/$1 (null)
2023-07-18T22:48:30,692 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:emtrust:.+)$' at http://driver-did-emtrust:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,694 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:meta:.+)$' at https://resolver.metadium.com/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,696 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^did:(?:tz:|pkh:|web:|key:(?:z6Mk|zQ3s|zDna|z.{200,})).+$' at http://driver-didkit:8080/identifiers/$1 (null)
2023-07-18T22:48:30,699 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:orb:.+)$' at http://orb-did-driver:8121/resolveDID?did=$1 (null)
2023-07-18T22:48:30,700 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:oyd:.+)$' at https://oydid-resolver.data-container.net/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,702 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:moncon:.+)$' at https://did.driver.moncon.co/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,704 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:dock:.+)$' at http://dock-did-driver:8080/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,707 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:mydata:.+)$' at http://mydata-did-driver:8080/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,709 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:dns:.+)$' at http://driver-did-dns:8080/1.0/identifiers/ (http://driver-did-dns:8080/1.0/properties)
2023-07-18T22:48:30,711 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:indy:.+)$' at http://indy-did-driver:8080/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,713 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:everscale:.+)$' at http://everscale-did-driver:8080/1.0/identifiers/ (null)
2023-07-18T22:48:30,715 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:ala:quor:redT:.+)$' at http://alastria-did-driver-mvp2:8080/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,717 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:cheqd:.+)$' at https://resolver.cheqd.net/1.0/identifiers/$1 (null)
2023-07-18T22:48:30,719 INFO [main] u.w.c.WebAppConfig: Added driver for pattern '^(did:com:.+)$' at http://driver-did-com:8080/1.0/identifiers/ (null)
2023-07-18T22:48:33,034 INFO [main] o.e.j.s.s.DefaultSessionIdManager: DefaultSessionIdManager workerName=node0
2023-07-18T22:48:33,039 INFO [main] o.e.j.s.s.DefaultSessionIdManager: No SessionScavenger set, using defaults
2023-07-18T22:48:33,043 INFO [main] o.e.j.s.s.HouseKeeper: node0 Scavenging every 600000ms
2023-07-18T22:48:33,094 INFO [main] o.e.j.s.h.ContextHandler: Started o.s.b.w.e.j.JettyEmbeddedWebAppContext@3c1e3314{application,/,[file:///tmp/jetty-docbase.8080.1540898477878628046/],AVAILABLE}
2023-07-18T22:48:33,096 INFO [main] o.e.j.s.Server: Started @32182ms
2023-07-18T22:48:35,560 INFO [main] o.s.b.a.e.w.EndpointLinksResolver: Exposing 1 endpoint(s) beneath base path '/actuator'
2023-07-18T22:48:35,720 INFO [main] o.e.j.s.h.ContextHandler$Context: Initializing Spring DispatcherServlet 'dispatcherServlet'
2023-07-18T22:48:35,721 INFO [main] o.s.w.s.FrameworkServlet: Initializing Servlet 'dispatcherServlet'
2023-07-18T22:48:35,733 INFO [main] o.s.w.s.FrameworkServlet: Completed initialization in 11 ms
2023-07-18T22:48:35,834 INFO [main] o.e.j.s.AbstractConnector: Started ServerConnector@47c4ecdc{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
2023-07-18T22:48:35,839 INFO [main] o.s.b.w.e.j.JettyWebServer: Jetty started on port(s) 8080 (http/1.1) with context path '/'
2023-07-18T22:48:35,918 INFO [main] o.s.b.StartupInfoLogger: Started WebUniResolverApplication in 23.19 seconds (JVM running for 35.004)
So that is actually started. One of two things is happening; we are not waiting long enough for to startup or there is no comms.
Can you increase LEDGER_TIMEOUT in the manage script and see if that does it?
lethal233
commented
1 year ago So that is actually started. One of two things is happening; we are not waiting long enough for to startup or there is no comms. Can you increase
LEDGER_TIMEOUTin the manage script and see if that does it?
How much do you think can it work? I stop them by using ./manage stop and rerun it. I increased it from 60 to 600 and but the message still exists:
waiting for tails server to start...
waiting for uniresolver to start.........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................\e[31m
Universal Resolver failed to start within 600 seconds.
\e[0m
\e[31m
Universal Resolver is not running.
\e[0mI've submitted a PR on von-network to auto-detect the OS and architecture and set DOCKER_DEFAULT_PLATFORM=linux/amd64 for Arm based MACs; https://github.com/bcgov/von-network/pull/272. I'm wondering whether we should do the same for the AATH scripts, and ACA-Py demos. I'll enter tickets.
cc @swcurran, @nodlesh
nodlesh
commented
1 year ago Yes agreed, this should go into the manage scripts of AATH and AMTH.
WadeBarnes
commented
1 year ago Yes agreed, this should go into the manage scripts of AATH and AMTH.
I've added the tickets to ACA-Py, AATH, and AMTH.
nodlesh
commented
10 months ago @lethal233 is this still an issue for you? I believe I can close this issue?
lethal233
commented
10 months ago @nodlesh Yes, I close it for now. Thanks!
Hi, I am trying to build Aries Agent Test Harness by following this instruction: https://github.com/hyperledger/aries-agent-test-harness/blob/main/README.md, However, when I input the last line of the script
It shows
I wonder if there is any instruction on how to solve this issue? Thanks in advance.
Env
MacOS Sonoma 14.0 + M2 chip