Unable to query the oasis node #494
Comments
|
yup, it's been updated. use the new network bb3d748def55bdfb797a2ac53ee6ee141e54cd2ab2dc2375f4a0703a178e6e55 |
|
@pro-wh Thanks for your response. When I try querying the latest block synced using the upgraded node I am getting the response. But if I try to query the older blocks it does not work and I get the below response.
|
|
that latest synced block index can't be right. the bb3d748def55bdfb797a2ac53ee6ee141e54cd2ab2dc2375f4a0703a178e6e55 mainnet started at block 16817956. that mainnet can't answer about blocks from before it started |
|
@pro-wh : Then how do we get the data prior to the block 16817956 from our node. |
|
run a separate node from the prior network, and run a separate oasis rosetta gateway connected to that node to answer for blocks in that network. it's a lot of trouble, we're aware. sorry about that |
|
@pro-wh : Tried running the old node with the network b11b369e0da5bb230b220127f5e7b242d385ef8c6f54906243f30af63c815535 . But the node is not syncing and when try to check the latest block query it returns the genesis block and also getting the below error in the node. {"caller":"pex_reactor.go:531","level":"info","module":"tendermint:pex","msg":"No addresses to dial. Falling back to seeds","ts":"2023-12-11T10:58:09.941068528Z"} And when I try to query the block data from the node with the below curl query |
|
the seed nodes are now on the new network, so you won't be able to connect to a network using it. you can run a node in "archive" mode, where it won't connect to the p2p network. you'll need to run it with your own data, i.e. from before the wipe in the upgrade steps, as it won't sync data from a network. |
|
We are running the oasis node using the below docker compose file |
|
the volume for /data is commented out in the screenshot above |
|
@pro-wh : Even when we uncomment the volume mapping for /data we don't get the volumes mapped to our node folder |
|
could it be a permissions issue? the mounted directory needs to be www-data:www-data (33) and be mode 0700. check the container logs for diagnostics. here's how I got it working locally: mkdir -p /tmp/rosetta-data/etc
chmod 700 /tmp/rosetta-data
cp config.yml /tmp/rosetta-data/etc
wget -O /tmp/rosetta-data/etc/genesis.json https://github.com/oasisprotocol/mainnet-artifacts/releases/download/2023-11-29/genesis.json
sudo chown -R www-data:www-data /tmp/rosetta-data
docker run -it -v /tmp/rosetta-data:/data rosetta-priv:latest(edit: chown later for convenience) then sudo ls -al /tmp/rosetta-datashows files |
|
@pro-wh : The image rosetta-priv:latest that you are using is it the latest and we need to use this image. |
|
tried with 2.6.0, works with that too. there are no changes to how the docker image uses that directory between 2.6.0 and master |
|
@pro-wh : Tried to start the node with the backup that we had to read the block data before 16817956. But getting error as below: |
|
from our team:
https://docs.oasis.io/node/run-your-node/archive-node#configuration |
|
quick correction to the docs:
edit: docs updated too |
The node stopped syncing and I had upgraded the oasis node to v2.6.0. When I check the logs of the node it is syncing fine as shown in the below image.
When I try to run the below curl query against the node.
curl --location 'http://************/block' \ --header 'Content-Type: application/json' \ --data '{ "network_identifier": { "blockchain": "Oasis", "network": "b11b369e0da5bb230b220127f5e7b242d385ef8c6f54906243f30af63c815535" }, "block_identifier": { "index": 16840161 } }'I am getting response as
{ "code": 0, "message": "network identifier {\"blockchain\":\"Oasis\",\"network\":\"b11b369e0da5bb230b220127f5e7b242d385ef8c6f54906243f30af63c815535\"} is not supported: requestNetwork is not supported", "retriable": false }Please let me know if the network identifier has been updated.
The text was updated successfully, but these errors were encountered: