# updating via yum leaves database server shut down

**URL:** <https://forums.percona.com/t/updating-via-yum-leaves-database-server-shut-down/3456>\
**Category:** Other MySQL® Questions\
**Created:** [May 7, 2014, 9:50pm UTC](https://forums.percona.com/t/updating-via-yum-leaves-database-server-shut-down/3456 "2014-05-07T21:50:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![greengecko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/greengecko/32/888_2.png) [@greengecko](https://forums.percona.com/u/greengecko)\
**Post date:** [May 7, 2014, 9:50pm UTC](https://forums.percona.com/t/updating-via-yum-leaves-database-server-shut-down/3456/1 "2014-05-07T21:50:25Z")

</div>

I’m seeing this happening with CentOS / Amazon Linux servers. This is a bit of a problem as I reckon that CentOS is far enough behind the bleeding edge that running yum-cron to automatically update software is the least risky option.

Is there any alternative to disabling the percona repo by default?

Cheers,

Steve
