Skip to content
New issue

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

Auditing The F10 Tally does not work on mac #549

Open
profd2004 opened this issue Sep 4, 2023 · 1 comment
Open

Auditing The F10 Tally does not work on mac #549

profd2004 opened this issue Sep 4, 2023 · 1 comment
Assignees
Labels
in triage Presently being triaged by the triage team

Comments

@profd2004
Copy link
Contributor

Describe the bug
Following the instructions at https://github.com/input-output-hk/catalyst-core/blob/main/src/audit/balance/README.md and accompanying video purports that after 8 to 10 minutes one should be able to curl http://127.0.0.1:10000/api/v0/vote/active/plans and get either a json response or Internal server error: Blockchain tip not set in REST/RPC contex. Instead all I'm getting is curl: (52) Empty reply from server

To Reproduce
Steps to reproduce the behavior:

  1. from the ./src/audit/balance folder:
    Mount local path as a volume in the container.
    MOUNT_PATH=/tmp/fund10-leader-1:/leader1stuff
    Folder structure of /tmp/fund10-leader-1
Screenshot 2023-09-04 at 8 39 58 AM

HISTORICAL_STATE=/leader1stuff/persist/leader-1
BLOCK_0=/leader1stuff/artifacts/block0.bin

  1. Build the things
    earthly +build && earthly +docker-local

  2. Run docker container removing network flag and adding port mapping (to support docker for mac).
    docker run -p 10000:10000 -v $MOUNT_PATH --env STORAGE_PATH=$HISTORICAL_STATE --env GENESIS_PATH=$BLOCK_0 jormungandr

We get flurry of replay logs, then stabalizes to this every second or so:

ind":"topology","name":"service"},{"task":"topology","name":"generating_gossip"}]}
{"timestamp":"2023-09-04T13:37:52.298296969Z","level":"TRACE","fields":{"message":"gossiping with peers"},"target":"jormungandr::topology::process","span":{"task":"topology","name":"generating_gossip"},"spans":[{"kind":"topology","name":"service"},{"kind":"topology","name":"service"},{"task":"topology","name":"generating_gossip"}]}
{"timestamp":"2023-09-04T13:37:52.565379719Z","level":"TRACE","fields":{"message":"skipping roll_iobuf due to empty segment","log.target":"sled::pagecache::iobuf","log.module_path":"sled::pagecache::iobuf","log.file":"/usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sled-0.34.7/src/pagecache/iobuf.rs","log.line":864},"target":"sled::pagecache::iobuf"}
{"timestamp":"2023-09-04T13:37:53.065653219Z","level":"TRACE","fields":{"message":"skipping roll_iobuf due to empty segment","log.target":"sled::pagecache::iobuf","log.module_path":"sled::pagecache::iobuf","log.file":"/usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sled-0.34.7/src/pagecache/iobuf.rs","log.line":864},"target":"sled::pagecache::iobuf"}
{"timestamp":"2023-09-04T13:37:53.570730261Z","level":"TRACE","fields":{"message":"skipping roll_iobuf due to empty segment","log.target":"sled::pagecache::iobuf","log.module_path":"sled::pagecache::iobuf","log.file":"/usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sled-0.34.7/src/pagecache/iobuf.rs","log.line":864},"target":"sled::pagecache::iobuf"}
{"timestamp":"2023-09-04T13:37:54.075163303Z","level":"TRACE","fields":{"message":"skipping roll_iobuf due to empty segment","log.target":"sled::pagecache::iobuf","log.module_path":"sled::pagecache::iobuf","log.file":"/usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/sled-0.34.7/src/pagecache/iobuf.rs","log.line":864},"target":"sled::pagecache::iobuf"}
{"timestamp":"2023-09-04T13:37:54.579886595Z","level":"TRACE","fields
  1. curl http://127.0.0.1:10000/api/v0/vote/active/plans after 10 minutes to no avail with the error: curl: (52) Empty reply from server.

Expected behavior
json response or Internal server error: Blockchain tip not set in REST/RPC context error message.

System:

  • OS: MacOs
  • Docker for mac: 4.22.0 (117440)

Additional context
My guess is that the internal server is only listening on localhost as oppose 0.0.0.0? When I install curl in the container and internally run the command I get a valid json response.

My current work around is to then copy the file form the container after calling the api internally.

@minikin minikin added the in triage Presently being triaged by the triage team label Sep 4, 2023
@cong-or
Copy link
Contributor

cong-or commented Sep 25, 2023

@profd2004 thanks for opening the issue. Have you tried changing the port in the node_config in /balance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in triage Presently being triaged by the triage team
Projects
None yet
Development

No branches or pull requests

3 participants