🐞 [Bug]: casperlabs stucks after deploying

[khaledyoussef24]

Is there an existing issue for this?

• I have searched the existing issues

which package/s did you face the problem with?

Dashboard

What happened?

After deploying Casperlabs, the services are all telling "checking" and "processing."
produced with 3 deployments
followed the docs

Steps To Reproduce

No response

which network/s did you face the problem on?

Main

version

2.8

Twin ID/s

No response

Node ID/s

No response

Farm ID/s

No response

Contract ID/s

No response

Relevant screenshots/screen records

.

Relevant log output

.

[zaelgohary]

Investigation:

I found that Casperlabs service in the VM is not running, and the logs showed that it had an error while key gen step. Fixed by added a condition before key gen, but faced other issues regarding Casperlabs version & missing dependencies.

[zaelgohary]

I could fix the dependency issues by upgrading Ubuntu & Casper version within the VM.

Currently working on fixing the flist.

[zaelgohary]

Work Completed:

Updated the flist with above changes and created a PR in tf-images. Applied hardeware requirements in solution.

[zaelgohary]

I fixed the node log file issue as the file path was not created on the machine, and the logs were empty in the dashboard. Additionally, I worked on resolving the node sync issue; however, I couldn't test it properly as there were no available nodes on the dev or QA environments due to the new hardware requirements. Tested a bit on the mainnet but faced connection issues as seen in the screenshot below. Will continue testing today. Opened an issue to fund main acc.

[zaelgohary]

The fast node sync is not working due to an empty trust hash. In this case, node sync will be from genesis, which is very slow and could take days. I tried multiple solutions to get a working, trusted hash, but all failed. I also tried multiple validator IPs but all were unreachable.