Open Atikocak opened 7 months ago
@Atikocak , we are currently running the latest testworld release, rampup6. Could you please update your node and see you still face the same issue? https://github.com/MinaProtocol/mina/releases/tag/2.0.0rampup6
@Atikocak , we are currently running the latest testworld release, rampup6. Could you please update your node and see you still face the same issue? https://github.com/MinaProtocol/mina/releases/tag/2.0.0rampup6
Hello, I've updated the Mina Daemon to the latest release (rampup6) that you have given.
Here is my latest issue;
Nov 16 20:50:02 m23636.contaboserver.net systemd[687]: Started Mina Daemon Service.
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: {"timestamp":"2023-11-16 19:50:02.796837Z","level":"Info","source":{"module":"Mina_cli_entrypoint","location":"File \"src/app/cli/src/cli_entrypoint/mina_cli_entrypoint.ml\", line 559, characters 8-19"},"message":"Mina daemon is booting up; built with commit $commit on branch $branch","metadata":{"branch":"rampup","commit":"4061884b18137c1182c7fcfa80f52804008a2509","commit_date":"2023-10-20T16:15:24+02:00","marlin_commit":"fd7c19d4c5dbb6826d1d5ce6bc24796a44087f70"}}
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: {"timestamp":"2023-11-16 19:50:02.797488Z","level":"Info","source":{"module":"Mina_lib__Conf_dir","location":"File \"src/lib/mina_lib/conf_dir.ml\", line 21, characters 10-21"},"message":"Created daemon lockfile $lockfile","metadata":{"lockfile":"/root/.mina-config/.mina-lock"}}
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: {"timestamp":"2023-11-16 19:50:02.797534Z","level":"Info","source":{"module":"Exit_handlers","location":"File \"src/lib/exit_handlers/exit_handlers.ml\", line 28, characters 2-13"},"message":"Registering async shutdown handler: $description","metadata":{"description":"Remove daemon lockfile"}}
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: {"timestamp":"2023-11-16 19:50:02.797560Z","level":"Info","source":{"module":"Mina_cli_entrypoint","location":"File \"src/app/cli/src/cli_entrypoint/mina_cli_entrypoint.ml\", line 567, characters 10-21"},"message":"Daemon will expire at $exp","metadata":{"exp":"2024-12-10 14:00:00-07:00"}}
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: {"timestamp":"2023-11-16 19:50:02.797588Z","level":"Info","source":{"module":"Mina_cli_entrypoint","location":"File \"src/app/cli/src/cli_entrypoint/mina_cli_entrypoint.ml\", line 580, characters 8-19"},"message":"Booting may take several seconds, please wait","metadata":{}}
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: Using libp2p keypair private-key password from environment variable MINA_LIBP2P_PASS
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: {"timestamp":"2023-11-16 19:50:02.798018Z","level":"Info","source":{"module":"Exit_handlers","location":"File \"src/lib/exit_handlers/exit_handlers.ml\", line 31, characters 4-15"},"message":"Running async shutdown handler: $description","metadata":{"description":"Remove daemon lockfile"}}
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: (monitor.ml.Error
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: ("Yojson.Json_error(\"Line 1, bytes 0-33:\\nInvalid token 'CAESQDwCBkrmPROgwtEiqEwyCxgyk4zUn'\")")
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: ("Raised at Yojson.json_error in file \"common.ml\", line 5, characters 19-39"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Yojson.Safe.read_json in file \"lib/read.ml\" (inlined), line 1025, characters 3-39"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Yojson.Safe.from_lexbuf in file \"lib/read.mll\", line 1109, characters 8-26"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Yojson.Safe.from_string in file \"lib/read.mll\", line 1122, characters 6-26"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Secrets__Secret_file.read.(fun) in file \"src/lib/secrets/secret_file.ml\", line 130, characters 31-70"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Async_kernel__Deferred0.bind.(fun) in file \"src/deferred0.ml\", line 54, characters 64-69"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Async_kernel__Job_queue.run_job in file \"src/job_queue.ml\" (inlined), line 128, characters 2-5"
Nov 16 20:50:02 m23636.contaboserver.net mina[33755]: "Called from Async_kernel__Job_queue.run_jobs in file \"src/job_queue.ml\", line 169, characters 6-47"))
Nov 16 20:50:02 m23636.contaboserver.net systemd[687]: mina.service: Main process exited, code=exited, status=1/FAILURE
Nov 16 20:50:02 m23636.contaboserver.net systemd[687]: mina.service: Failed with result 'exit-code'.
OS: Ubuntu 20.04 (bullseye/sid)
@Atikocak have you found a fix? Looking at the logs it seems a problem with an invalid Token. May we close the issue?
Preliminary Checks
Description
Hello,
I'm actually trying to run my block producer node on "Berkeley Testnet Release 2.0.0rampup5". The latest release given here => https://github.com/MinaProtocol/mina/releases/tag/2.0.0rampup5
And here is the latest lines of crash report.
I've successfully completed every steps to connect Main-Net and synced completely but i can't achieve same thing on Berkeley Test-Net.
Steps to Reproduce
I've completed the below steps carefully after installing the latest berkeley-testnet mina branch.
~/.mina-env
file.EXTRA_FLAGS parameters have been updated as on the 3rd step.
and the following environment variables:
Generated Libp2p Keypair into /root/keys/libp2p-key file
mina libp2p generate-keypair /root/keys/my-wallet /root/keys/libp2p-key
Monitor the mina process that's running in the background and auto-restarting.
Checked if mina had any trouble getting started:
systemctl --user status mina
Stop mina gracefully and stop automatically restarting the service:
systemctl --user stop mina
Manually restart the mina process:
systemctl --user restart mina
Look at logs that show the last 1000 lines, and follow from there:
journalctl --user-unit mina -n 1000 -f
Expected Result
Actual Result
How frequently do you see this issue?
Always
What is the impact of this issue on your ability to run a node?
Blocker
Status
Additional information
Here you can find the detailed crash report which was logged.
coda_crash_report_2023-11-11_13-27-41.793284.tar.gz
=> Log File