FAQs
I encountered the following error after completing the Stader node service config: "error response from daemon: manifest for flashbots/mev-boost:1.6-portable not found: manifest unknown". How can I resolve this?
To address this issue, please follow these steps:
Run the command
~/bin/stader-cli service configto access the configuration manager page.Press Ctrl+U to navigate to the configuration settings page.
Locate the MEV Boost section and update the container tag datafield with the following value:
flashbots/mev-boost:1.6
Flashbots no longer supports portable images such as 1.6-portable. Portable images were utilized in systems lacking specific CPU features. If you encounter the mentioned error, simply update the container tag to resolve the issue and proceed with your Stader node setup smoothly.
I am encountering connection errors with the ETH 1 and ETH 2 clients when starting the stader node services and running stader-cli node sync?
If you are locally managing the stader node services, it is normal to see connection errors with the ETH 1 and ETH 2 clients during the initial startup phase, which typically takes around 30 to 60 seconds. In such cases, it is recommended to wait for a short while as the clients need some time to fully sync up. After this brief period, the connection errors should disappear on their own.
However, if you are externally managing the stader node services, you should verify whether the external clients are functioning as intended to ensure proper connectivity.
I am encountering a "Temporary Name Resolution Error" with my ETH 1 and ETH 2 clients?
This indicates that the ETH 1 and ETH 2 clients are not running.
If you are locally managing the ETH 1 and ETH 2 clients, and encounter this error, first run docker ps to verify if the containers are running. If the containers are not running, use stader-cli service start to start the clients.
If the clients are externally managed, the node operator should ensure that the DNS for the clients is resolved correctly.
I am encountering this error message when starting the services
"Error response from daemon: path /proc is mounted on /proc but it is not a shared or slave mount, error startService: error starting API container: exit status 1"
What should I do?
This error typically occurs on Docker Desktop with Mac M2 chipset. Please note that our current Stader node platform does not support Mac M2. To resolve this issue, consider using a different platform.
What should I do if I encounter the error message "Error piping stdout: read |0: file already closed" when running stader-cli service start or stader-cli service stop?
This error message can be safely ignored as it is not significant and does not affect the functionality of the command or the services.
My validator is not attesting at all, what should I do?
First, ensure that you have sufficient CPU, RAM, and network bandwidth to support the number of validators you are running. If the resources meet the requirements, check the validator client logs to verify if the validator keys have been successfully read by the client. If the keys have not been read, restart the validator client to allow it to read the keys.
What should I do if my validator has not received 31 ETH to start validating?
Please verify that the 1 ETH deposit has been processed on the beacon chain. If it has been processed, please be patient and wait for the distribution of 31Eth, which typically occurs every 24-36 hours. If you do not receive the 31 ETH within 2-3 days after the 1 ETH has been processed, please raise the concern to the Stader team on Discord for further assistance.
How can I use a different version of my CC/EC clients, Prometheus, MEV Boost, or Grafana?
First, run
~/bin/stader-cli service configto open Stader node configuration Manager. Then, press ctrl + U to access the configuration settings page.In the settings page, navigate to the relevant section for the desired component.
Within that section, locate the "image tag" field. Simply update the image tag field with the version you want to use, and proceed to restart your services.
Note: Please note that using incorrect or incompatible versions may result in container update failures. Please exercise caution, as Stader will not be responsible for any issues caused by using unsupported versions. Stader takes responsibility only for issues related to the suggested versions it recommends.
The validator status does not show my validators in order of registration, and the validator sequence appears to shift on every run
To optimize network calls, Stader fetches data from the contract in batches and stores it in a hashmap for efficient access. However, it's important to note that Hashmaps are non-deterministic data structures, meaning that each call to the Hashmap may yield the validator results in a different sequence.
How can I view the logs of the containers?
Firstly, run "docker ps" to obtain the container IDs.
Once you have the container ID, use the command "docker logs -f --tail 100 \<container_id>".
This command will display the latest 100 log lines of the specified container.
How can I check if my validator has successfully sent the pre-sign message
To verify the successful transmission of the pre-sign message
check the logs of the
stader_nodecontainer. Look for the log entry stating "Successfully sent the pre-signed message for validator:<validator public key>".If you come across this log entry, it confirms that the pre-sign message has been successfully sent for the validator with the corresponding public key.
My pre-sign was not sent to Stader after changing the network, what should I do?
Once a node operators changes the network they need to restart the services. Please use the following commands to restart your services.
~/bin/stader-cli service stop
~/bin/stader-cli service start
How to check the ETHx deposit queue?
To check the ETHx 28ETH deposit queue, click here
How to check a validator position in the ETHx 28ETH deposit queue
To check a validator position in the ETHx 28ETH deposit queue, Step 1. Click on this link: https://universe.staderlabs.com/eth/validatorQueuePosition?validatorKey=
Step 2: Add your Validator Public Key after the URL and press enter. You validator position in the deposit queue will be displayed.
Last updated