celo-org / celo-blockchain

Official repository for the golang Celo Blockchain
https://celo.org
GNU Lesser General Public License v3.0
554 stars 199 forks source link

Celo rosetta node issue #2222

Closed Swornatoya closed 6 months ago

Swornatoya commented 7 months ago

The celo rosetta node had stopped, when we tried starting it again getting the below error. Could you please help resolve this

Executing: /usr/local/bin/geth --datadir /data/celo --nousb --http --http.addr localhost --http.port 8545 --http.vhosts localhost --syncmode full --gcmode archive --http.api eth,net,web3,debug,admin,personal --ipcpath /var/geth.ipc --light.serve 0 --light.maxpeers 0 --maxpeers 1100 --consoleformat term --txlookuplimit 0 --port 30303 --verbosity 3 --cache 1024 ERROR[01-19|13:24:35.751] Rosetta run failed err="Geth service did not create ipc file within deadline, check the log: /logs/celo.log"

@eelanagaraj : Could you please help us with the above issue

palango commented 7 months ago

Looks like rosetta isn't able to start geth. Does the mentioned log file show why?

Swornatoya commented 7 months ago

@palango : The log files just gives the logs as below. No error logged in it INFO [01-19|13:24:35.690] Rewound fast block number=23,508,984 INFO [01-19|13:24:35.695] Rewound fast block number=23,508,983 INFO [01-19|13:24:35.701] Rewound fast block number=23,508,982 INFO [01-19|13:24:35.707] Rewound fast block number=23,508,981 INFO [01-19|13:24:35.712] Rewound fast block number=23,508,980 INFO [01-19|13:24:35.721] Rewound fast block number=23,508,979 INFO [01-19|13:24:35.726] Rewound fast block number=23,508,978 INFO [01-19|13:24:35.736] Rewound fast block number=23,508,977 INFO [01-19|13:24:35.744] Rewound fast block number=23,508,976

palango commented 7 months ago

Did you encounter any issues with the node before? This seems like an issue with the blockchain client, moving it over to the respective repo.

palango commented 6 months ago

@Swornatoya Are you still running into this issue?

Swornatoya commented 6 months ago

@palango : This has been resolved. Thanks