# STOP\_EVENT

The master server writes the event to the [binary log](/docs/server/server-management/server-monitoring-logs/binary-log.md) when it shuts down, or when resuming after a mariadbd process crash.

A new binary log file is always created, but there is no `ROTATE_EVENT`.

`STOP_EVENT` is the last written event after a clean shutdown, or when resuming after a crash.

{% hint style="warning" %}
This event is never sent to replica servers.
{% endhint %}

## Header

* Event header with EventType set to `STOP_EVENT` (`0x03`).
* Event header NextPos set to `EOF` .
* No special flags added.

## Fields

* The event has no data.

## Example With CRC32 (Last 4 Bytes)

Event size = header\[19] + 0 bytes data + 4 CRC32 = 23.

```
3a b8 15 5a 03 01 00 00  00 17 00 00 00 09 0c 00  ..Z............
00 00 00 4e 99 ee 2c                              ...N..,
```

<sub>*This page is licensed: CC BY-SA / Gnu FDL*</sub>

{% @marketo/form formId="4316" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mariadb.com/docs/server/reference/clientserver-protocol/replication-protocol/stop_event.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.