You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -140,11 +147,261 @@ If you encounter an error from the `restoration` script indicating a rejected bu
140
147
Also verify that the script is using the correct AWS access key and secret.
141
148
142
149
### The node doesn't sync
150
+
143
151
If your node cannot reach the same state as the main node, it means it did not execute blocks correctly and its database must be restored.
144
152
145
153
Perform a restoration using the appropriate snapshot. If the issue persists after restoration, contact Movement support.
146
154
147
155
### Error "State from Da verification failed"
156
+
148
157
When there's a divergence between the main node state and the full node state, it is detected on the full node, and the node stops with an error containing the sentence: `state from Da verification failed`.
149
158
150
-
To recover, try restarting the node. If you get the same error, perform a restoration to restart from a correct state. After restoration, restart the node; it should then sync correctly.
159
+
To recover, try restarting the node. If you get the same error, perform a restoration to restart from a correct state. After restoration, restart the node; it should then sync correctly.
160
+
161
+
### Warn "DA Sequencer reject batch, can't send the batch."
162
+
163
+
The full node batch signer key is not white listed. Send it to movement so that to register it to the da-sequencer.
164
+
165
+
### The node is blocked and doesn't start
166
+
167
+
If the node start but stop with this logs:
168
+
```
169
+
Attempting to bind metrics server to 0.0.0.0:9464
170
+
Metrics server successfully bound to 0.0.0.0:9464
171
+
Metrics server listening on 0.0.0.0:9464
172
+
```
173
+
It means that the config.json file hasn't been configured. Run the setup_migration script (see Update config).
174
+
175
+
### Error "Send execution state to da sequencer failed"
176
+
177
+
Update config.json to set `propagate_execution_state` field to "propagate_execution_state": false and restart.
178
+
179
+
### Error "he node shouldn't send state to the DA, change the config propagate_execution_state to "propagate_execution_state": false and resta"
180
+
181
+
The maptos database is not the one expected by the node. Stop the node and do a restoration.
182
+
183
+
### Error "WARN movement_da_sequencer_client: DA sequencer Http2 connection url:... failed"
184
+
185
+
The da-sequencer connection url is badly configured. Edit the config.json field `connection_url` and set it with the value corresponding the connected network define in Update config chapter.
186
+
187
+
### Error "movement-restore-db | unknown command "latest" for "restic"
188
+
189
+
The environment needed by the docker script or not defined or not detected by docker.
190
+
191
+
### Error "Error: Da Sync from height zero is not allowed."
192
+
193
+
The restoration hasn't been done or the database is not loaded correctly. Verify the DOT_MOVEMENT variable use to start the node is the same as the one to do the restoration.
0 commit comments