We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
indyscan-daemon exits and restarts
» docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f61931cbe3f2 pstas/indyscan-daemon:4.1.0 "/bin/sh -c 'npm run…" 14 minutes ago Restarting (1) 1 second ago indyscan-daemon 46855b570c89 docker.elastic.co/kibana/kibana:7.15.2-arm64 "/bin/tini -- /usr/l…" 14 minutes ago Up 11 minutes 0.0.0.0:5601->5601/tcp indyscan-kibana 0cd055888f65 docker.elastic.co/elasticsearch/elasticsearch:7.15.2-arm64 "/bin/tini -- /usr/l…" 14 minutes ago Up 11 minutes 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp indyscan-elasticsearch 2bb423df5f2f pstas/indypool:indyscanpool-v1.15.0 "/usr/bin/supervisord" 59 minutes ago Up 11 minutes 0.0.0.0:9701-9708->9701-9708/tcp indyscanpool 812460bf881f pstas/indyscan-api:4.1.0 "docker-entrypoint.s…" 59 minutes ago Up 11 minutes 0.0.0.0:3708->3708/tcp indyscan-api d864baf5eddd pstas/indyscan-webapp:4.1.0 "docker-entrypoint.s…" 59 minutes ago Up 11 minutes 0.0.0.0:3707->3707/tcp indyscan-webapp 0129826a65b2 pstas/indyscan-daemon-ui:4.1.0 "/bin/sh -c 'npm run…" 59 minutes ago Up 11 minutes 0.0.0.0:3710->3710/tcp indyscan-daemon-ui
Follow instructions for IndyPool + IndyScan on localhost
make up
all instances running, indyscan connects to local indyscan-pool and web-ui is accessible
indyscan-daemon | indyscan-daemon | > [email protected] start /home/indyscan/indyscan-daemon indyscan-daemon | > cross-env NODE_ENV=production node ./src/index.js indyscan-daemon | indyscan-daemon | Loaded configuration: { indyscan-daemon | "LOG_LEVEL": "info", indyscan-daemon | "WORKER_CONFIGS": "/home/indyscan/indyscan-daemon/app-configs-docker/INDYSCANPOOL.json", indyscan-daemon | "SERVER_ENABLED": "true", indyscan-daemon | "LOG_HTTP_REQUESTS": "true", indyscan-daemon | "LOG_HTTP_RESPONSES": "true", indyscan-daemon | "SERVER_PORT": "3709", indyscan-daemon | "AUTOSTART": "true", indyscan-daemon | "ENABLE_LOGFILES": "false" indyscan-daemon | } indyscan-daemon | 2021-11-12T16:13:34.200Z [--] info: Will bootstrap app from following operations definitions [ indyscan-daemon | "/home/indyscan/indyscan-daemon/app-configs-docker/INDYSCANPOOL.json" indyscan-daemon | ] indyscan-daemon | 2021-11-12T16:13:34.228Z [--] info: Going to build workers by rtwSerialization from {"indyNetworkId":"INDYSCANPOOL","genesisPath":"/home/indyscan/indyscan-daemon/app-configs-docker/genesis/INDYSCANPOOL.txn","esIndex":"txs-indyscanpool","esUrl":"http://indyscan-elasticsearch.esnet:9200","workerTiming":"FAST"} indyscan-daemon | 2021-11-12T16:13:34.260Z [--] info: Connecting to ledger INDYSCANPOOL. indyscan-daemon | Operation not permitted (src/thread.cpp:122) indyscan-daemon | qemu: uncaught target signal 6 (Aborted) - core dumped indyscan-daemon | npm ERR! code ELIFECYCLE indyscan-daemon | npm ERR! errno 1 indyscan-daemon | npm ERR! [email protected] start: `cross-env NODE_ENV=production node ./src/index.js` indyscan-daemon | npm ERR! Exit status 1 indyscan-daemon | npm ERR! indyscan-daemon | npm ERR! Failed at the [email protected] start script. indyscan-daemon | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. indyscan-daemon | indyscan-daemon | npm ERR! A complete log of this run can be found in: indyscan-daemon | npm ERR! /home/indyscan/.npm/_logs/2021-11-12T16_13_34_351Z-debug.log indyscan-daemon exited with code 1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
IndyPool + IndyScan on localhost
Description
indyscan-daemon exits and restarts
Steps to reproduce:
Follow instructions for IndyPool + IndyScan on localhost
make up
Expected result
all instances running, indyscan connects to local indyscan-pool and web-ui is accessible
Actual result
Environment
The text was updated successfully, but these errors were encountered: