twindb_agent needs privileges for STOP/START slave

Bug #1406808 reported by Aleksandr Kuzminsky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
twindb-agent
Invalid
High
Ovais Tariq

Bug Description

141231 20:01:16 innobackupex: Continuing after ibbackup has suspended
DBD::mysql::db do failed: Access denied for user 'twindb_agent'@'localhost' (using password: YES) at /usr/bin/innobackupex line 3036.
innobackupex: got a fatal error with the following stacktrace: at /usr/bin/innobackupex line 3039.
 main::mysql_query('HASH(0x1eab398)', 'STOP SLAVE SQL_THREAD') called at /usr/bin/innobackupex line 4777
 main::wait_for_safe_slave('HASH(0x1eab398)') called at /usr/bin/innobackupex line 1971
 main::backup() called at /usr/bin/innobackupex line 1592
innobackupex: Error:
Error executing 'STOP SLAVE SQL_THREAD': DBD::mysql::db do failed: Access denied for user 'twindb_agent'@'localhost' (using password: YES) at /usr/bin/innobackupex line 3036.
141231 20:01:16 innobackupex: Waiting for ibbackup (pid=22544) to finish

Changed in twindb:
assignee: Aleksandr Kuzminsky (akuzminsky) → Ovais Tariq (ovais-tariq)
Changed in twindb-agent:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Ovais Tariq (ovais-tariq)
Changed in twindb-agent:
milestone: none → 0.1.33
no longer affects: twindb
Revision history for this message
Ovais Tariq (ovais-tariq) wrote :

The agent grants the "SUPER" privilege when creating the twindb_agent user. So the user used by the backup should be able to stop/start slave. Are you talking about the scenario where the twindb_agent user has the 'SUPER' privilege revoked manually?

Changed in twindb-agent:
status: Confirmed → Invalid
status: Invalid → In Progress
Changed in twindb-agent:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.