<blockquote>
<p>I'm using tmux and I just use kill-session command to stop my node.</p>
</blockquote>
<p>That is probably not a safe shutdown.</p>
<p>For a safe shutdown you should go to the terminal where the <code>node</code> is running and send <code>Control-C</code>. You will then get a message like:</p>
<pre><code>[mainnet:cardano.node.ChainDB:Info:5] [2022-05-30 05:32:03.82 UTC] Closed db with
 immutable tip at 1000a37390ad4590c317da8ec0b456b7d2a50b5a07ad6162cd3fb0b5f5862a7a
 at slot 62277555 and
 tip b1b90587bf4e55e88a0f59ebfd0e4010aabfcd4c5209921a77bb12f479f32df0 
 at slot 62322410

Shutting down..
</code></pre>
<p>This indicts a correct and safe shutdown.</p>

CC BY-SA 4.0
2022-05-30T05:33:12.863Z
2022-05-30T05:33:12.863Z
Erik de Castro Lopo
<p>I've seen people suggest <code>kill -2 &lt;PID&gt;</code> as it sends a SIGINT (similar to CTRL-C), but it never quite completes for me. There is always 1 external network connection active and the main node process is still running, which I then <code>kill &lt;PID&gt;</code> after 10-15 minutes.</p>
<p>Although doing it this way does start up more quickly and avoids most of the <code>Validating chunk X of Y</code> work.</p>

CC BY-SA 4.0
2022-05-30T05:54:40.577Z
2022-05-30T05:54:40.577Z
MC_Brisbane - JUST Pool
<p>I think you should resume the session and press Control-C to stop cardano-node when you are running it in tmux.</p>

CC BY-SA 4.0
2022-05-30T05:31:02.320Z
2022-05-30T05:31:02.320Z
George - APEX Stake Pool
<p>Is there a way to correctly stop <code>cardano-node</code> different than making it run as a service?</p>
<p>I have noticed that, since version 1.34.1, I'm getting the message <code>Validating chunk no. X out of Y.</code> every time I restart it.</p>
<p>I assume this is happening because I'm not stopping it correctly.</p>
<p>I'm using <code>tmux</code> and I just use <code>kill-session</code> command to stop my node.</p>

<cardano-node><stake-pool><node><syncing>
How can I stop Cardano Node correctly without running it as a service?
# How can I stop Cardano Node correctly without running it as a service?

(Asked by: username_0 on 2022-05-30)

Is there a way to correctly stop `cardano-node` different than making it run as a service?

I have noticed that, since version 1.34.1, I'm getting the message `Validating chunk no. X out of Y.` every time I restart it.

I assume this is happening because I'm not stopping it correctly.

I'm using `tmux` and I just use `kill-session` command to stop my node.

**Tags:** cardano-node, stake-pool, node, syncing

---

## 3 answers

### Answer by username_1 on 2022-05-30. Score: 2 | Accepted answer

I'm using tmux and I just use kill-session command to stop my node.

That is probably not a safe shutdown.
For a safe shutdown you should go to the terminal where the node is running and send Control-C. You will then get a message like:
[mainnet:cardano.node.ChainDB:Info:5] [2022-05-30 05:32:03.82 UTC] Closed db with
 immutable tip at 1000a37390ad4590c317da8ec0b456b7d2a50b5a07ad6162cd3fb0b5f5862a7a
 at slot 62277555 and
 tip b1b90587bf4e55e88a0f59ebfd0e4010aabfcd4c5209921a77bb12f479f32df0 
 at slot 62322410

Shutting down..

This indicts a correct and safe shutdown.


---

### Answer by username_3 on 2022-05-30. Score: 4

I think you should resume the session and press Control-C to stop cardano-node when you are running it in tmux.


---

### Answer by username_2 on 2022-05-30. Score: 1

I've seen people suggest `kill -2`  as it sends a SIGINT (similar to CTRL-C), but it never quite completes for me. There is always 1 external network connection active and the main node process is still running, which I then `kill`  after 10-15 minutes.

Although doing it this way does start up more quickly and avoids most of the `Validating chunk X of Y` work.


---

