# Server shutdown problem

**URL:** https://forums.percona.com/t/server-shutdown-problem/1673
**Category:** Other MySQL® Questions
**Created:** [September 21, 2011, 11:31pm UTC](https://forums.percona.com/t/server-shutdown-problem/1673 "2011-09-21T23:31:38Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![slnp](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@slnp](https://forums.percona.com/u/slnp)
#### Post date: [September 21, 2011, 11:31pm UTC](https://forums.percona.com/t/server-shutdown-problem/1673/1 "2011-09-21T23:31:38Z")

</div>

Hi All,

I shutdown our mysql server with service mysql shutdown as normal however I had this problem:

110922 4:34:08 [Note] /usr/sbin/mysqld: Normal shutdown  
110922 4:34:08 [Note] Event Scheduler: Purging the queue. 0 events  
110922 4:34:10 InnoDB: Starting shutdown…  
110922 4:51:58 [Note] Plugin ‘FEDERATED’ is disabled.  
110922 4:52:04 InnoDB: Database was not shut down normally!  
110922 4:56:35 InnoDB: Starting an apply batch of log records to the database…

This same issue also happened earlier today with a normal shutdown.

What could be causing this?

Thanks in advance

---

<div class="post-metadata">

### Author: ![slnp](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@slnp](https://forums.percona.com/u/slnp)
#### Post date: [September 22, 2011, 10:58am UTC](https://forums.percona.com/t/server-shutdown-problem/1673/2 "2011-09-22T10:58:51Z")

</div>

To elaborate on this I shut the server down normally with out any errors however when I start it starts doing recovery and I can’t tell why.

---

<div class="post-metadata">

### Author: ![sterin71](https://avatars.discourse-cdn.com/v4/letter/s/5e9695/32.png) [@sterin71](https://forums.percona.com/u/sterin71)
#### Post date: [September 23, 2011, 5:10am UTC](https://forums.percona.com/t/server-shutdown-problem/1673/3 "2011-09-23T05:10:26Z")

</div>

Does the error log say anything else at startup?

What is your setting for:  
innodb\_fast\_shutdown

You can try setting this variable to 0 (which you can change on a running server) to force InnoDB to perform a complete flush at shutdown (but note that that can take a lot of time if you have a large highly volatile database).
