-
Notifications
You must be signed in to change notification settings - Fork 41
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
V2445.0 w/ 10.1.2 - Reading from EraReader adapter raised an error: 'general error'. #2104
Comments
Thanks @mrabdibdi-anvil for creating this issue. The error message states that the connection to the Cardano node done by the Mithril signer did not work. Can you tell us what happens when:
|
Morning, you restart the signer node. Does the problem persist? Yes. you connect to the Cardano node with the Cardano CLI (e.g. to retrieve the tip of the chain)? Yes it works. /usr/local/bin/cardano-cli query tip --socket-path /cardano/ipc/node.socket --mainnet
{
"block": 11084811,
"epoch": 521,
"era": "Conway",
"hash": "28302bd95637cd4d792711a5a8f35ad679b00975f97d531fe23ac0886945bd7c",
"slot": 139858372,
"slotInEpoch": 149572,
"slotsToEpochEnd": 282428,
"syncProgress": "100.00"
} Cardano related env vars: CARDANO_NODE_SOCKET_PATH=/cardano/ipc/node.socket
CARDANO_CLI_PATH=/usr/local/bin/cardano-cli I tried with a clean {"msg":"🔥 Cardano transactions preloader failed","v":0,"name":"mithril-signer","level":60,"time":"2024-11-12T15:21:50.55431616Z","hostname":"bb37734874c8","pid":7,"error":"error while sending or receiving data through the channel"} The rest of the logs look ok. Then after few minutes it prints: {"msg":">> get_current_time_point","v":0,"name":"mithril-signer","level":20,"time":"2024-11-12T15:23:50.498065409Z","hostname":"bb37734874c8","pid":7,"src":"SignerRunner"}
{"msg":"An error occurred, runtime state kept. message = 'Could not retrieve current time point in context 'checking if epoch has changed'.'","v":0,"name":"mithril-signer","level":50,"time":"2024-11-12T15:23:50.498093389Z","hostname":"bb37734874c8","pid":7,"src":"StateMachine","nested_error":"Runner can not get current time point\n\nCaused by:\n 0: TimePoint Provider can not get current epoch\n 1: general error\n 2: PallasChainObserver failed to create new client\n 3: error connecting bearer\n 4: No such file or directory (os error 2)"}
{"msg":"… Cycle finished, Sleeping for 60000 ms","v":0,"name":"mithril-signer","level":30,"time":"2024-11-12T15:23:50.498101915Z","hostname":"bb37734874c8","pid":7,"src":"StateMachine"} EDITED: After few cycles, the |
Thanks @mrabdibdi-anvil for providing these information. It looks like the configuration of the Cardano node socket is not correctly setup for the signer node:
Also, I recommend that you rollback the previous store (and restart the signer node) as this is not the source of the problem and starting with a fresh new store means you will have to wait 2 epochs before being able to sign. |
Perfect ! @jpraynaud I restarted using the original files I had backup. Now I get the original error message:
These two commands work as well: $CARDANO_CLI_PATH query tip --socket-path $CARDANO_NODE_SOCKET_PATH --mainnet
$CARDANO_CLI_PATH query tip --socket-path /cardano/ipc/node.socket --mainnet |
OK, I can see that the signer has now access to the Cardano node through the Unix socket as the state is The error message that you have is now different from ythe first one. The Cardano transactions are being imported which explains that the signer is not able yet to sign this type of message. This is probably due to the previous version of the node you were running (can you share the version?). The process will likely take few hours (as explained in this doc: https://mithril.network/doc/manual/operate/run-signer-node#cardano-transactions-certification-footprint). Let me know if you still have error messages in the next 24 hours 🙂 |
Thanks for your time and responses I upgraded the cardano node from 9.2.1 to 10.1.2 last week, The linked documentation is the one I followed to setup the Dockerfile, I have been running like this for a while without issue. Do I have actions to do or just wait 24h to see if it is resolved ? |
OK, can you also share the previous version of the signer you were running? If there is no more error logs in 24 hours you can close the issue. Otherwise, feel free to post them 👍 |
oh ! mithril-signer version 2437.1 Perfect will do ! |
@mrabdibdi-anvil I close this issue. Feel free to reopen if necessary 🙂 |
Hello ! @jpraynaud I let it runs for about 24h The issue is persisting
|
Hi @mrabdibdi-anvil, these might be transient errors 🤔 Can you share a full extract of the signer logs and your pool id so that we can investigate further the problem? Maybe our Discord channel is a better place for troubleshooting: https://discord.gg/5kaErDKDRq. |
Context & versions
Using Docker with prebuilt binaries
mithril-signer_0.2.209+67dc6e4-1_amd64.deb
Steps to reproduce
I restarted using the newest Binary version, and it shows the message (see below)
I tried to remove the
/opt/mithril/stores
, but without success.Actual behavior
Upgraded to latest version (2445.0) And the cardano node to 10.1.2
This message was after I deleted the stores directory.
I get this message:
Expected behavior
Trying to understand the provenance of this error, is it a me issue ?
I suspect file permissions with the volumes (sharing cardano node.socket, db and keys)
Thank you !
The text was updated successfully, but these errors were encountered: