# Can I get pt-online-schema-change to abort if it can't connect to slave DBs?

**URL:** <https://forums.percona.com/t/can-i-get-pt-online-schema-change-to-abort-if-it-cant-connect-to-slave-dbs/7055>\
**Category:** Percona Toolkit\
**Created:** [June 10, 2019, 10:35am UTC](https://forums.percona.com/t/can-i-get-pt-online-schema-change-to-abort-if-it-cant-connect-to-slave-dbs/7055 "2019-06-10T10:35:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![eliot.chan](https://avatars.discourse-cdn.com/v4/letter/e/97f17d/32.png) [@eliot.chan](https://forums.percona.com/u/eliot.chan)\
**Post date:** [June 12, 2019, 10:15am UTC](https://forums.percona.com/t/can-i-get-pt-online-schema-change-to-abort-if-it-cant-connect-to-slave-dbs/7055/3 "2019-06-12T10:15:40Z")

</div>

Hi Carlos,

The issue was that the root user didn’t have the necessary permissions to connect to the slaves - they were discoverable, just not able to be connected to. That being said, I’m still looking for a way to run the command in a way that it would abort itself if the found slaves could not be connected to.

Thanks

---

_[View the full topic](https://forums.percona.com/t/can-i-get-pt-online-schema-change-to-abort-if-it-cant-connect-to-slave-dbs/7055)._