Open wengych opened 1 month ago
REV=87b195f7347c888b418cb46b34ae6711fcbf737e
@wengych thanks for reporting this. As per https://aptos.dev/en/build/indexer/legacy we are not actively supporting the legacy indexer in which this bug is describing. We do however support the new Indexer API https://aptos.dev/en/build/indexer and you should be able to connect to the raw gRPC stream using grpcui -plaintext localhost:30734
. This is the equivalent to the Transaction Streaming Service which means you would need to look at https://github.com/aptos-labs/aptos-indexer-processors/
@wengych thanks for reporting this. As per https://aptos.dev/en/build/indexer/legacy we are not actively supporting the legacy indexer in which this bug is describing. We do however support the new Indexer API https://aptos.dev/en/build/indexer and you should be able to connect to the raw gRPC stream using
grpcui -plaintext localhost:30734
. This is the equivalent to the Transaction Streaming Service which means you would need to look at https://github.com/aptos-labs/aptos-indexer-processors/
Hi, thanks for the answer, however, this is not about indexer. We can't run a normal RPC node, and the above is the log when we run the fullnode according to the doc. If the indexer causes the error, could we just disable it
@zfy0701 We'll be putting in several updates to the indexer integration shortly, including one which will allow you to flag it out. The above can be ignored whilst running your full-node, however.
Describe the bug Following the updated documentation, I rebuilt the docker-compose stack and found error logs in the container
suzuka-full-node
as follows:To Reproduce Steps to reproduce the behavior:
docker compose –env-file .env -f docker/compose/suzuka-full-node/docker-compose.yml -f docker/compose/suzuka-full-node/docker-compose.setup-local.yml -f docker/compose/suzuka-full-node/docker-compose.celestia-local.yml logs suzuka-full-node -f
Expected behavior The docker-compose stack should start successfully without any errors.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Here are the detailed error logs from the
suzuka-full-node
container: