Skip to content
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

docs: graceful-shutdown-value #2123

Merged
merged 2 commits into from
Mar 4, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -121,7 +121,7 @@ Or:
- When shutting down the Docker image, it is important to allow a graceful shutdown so that the current state can be saved to disk. Here is an example of how to do a graceful shutdown of all Docker images currently running

```shell
docker stop --time=300 $(docker ps -aq)
docker stop --time=1800 $(docker ps -aq)
```

### Note on permissions
Expand Down
2 changes: 1 addition & 1 deletion arbitrum-docs/run-arbitrum-node/03-run-full-node.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ Even though there are alpha and beta versions of the <a data-quicklook-from='arb
- When shutting down the Docker image, it is important to allow a graceful shutdown to save the current state to disk. Here is an example of how to do a graceful shutdown of all docker images currently running

```shell
docker stop --time=300 $(docker ps -aq)
docker stop --time=1800 $(docker ps -aq)
```

### Note on permissions
Expand Down
2 changes: 1 addition & 1 deletion arbitrum-docs/run-arbitrum-node/06-troubleshooting.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ You can check logs by different log types: info, warn, and error.
This is usually because your node shuts down ungracefully. In most cases, it will
recover in a few minutes, but if it not, you may have to re-sync your node. Remember to
shut down your node gracefully with the following command:{' '}
<code>docker stop —time=300 $(docker ps -aq)</code>.
<code>docker stop —time=1800 $(docker ps -aq)</code>.
</td>
</tr>
<tr className="scenario">
Expand Down