pt-heartbeat --check should not write to the heartbeat table

Bug #1733010 reported by monty solomon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
New
Undecided
Unassigned

Bug Description

% pt-heartbeat --host localhost -D heartbeat --check

DBD::mysql::db do failed: The MySQL server is running with the --read-only option so it cannot execute this statement [for Statement "INSERT INTO `heartbeat`.`heartbeat` (server_id, ts) VALUES ('639407132', UTC_TIMESTAMP())"] at /usr/bin/pt-heartbeat line 5953.

pt-heartbeat still tries to write to the table when --check-read-only is added

% pt-heartbeat --host localhost -D heartbeat --check --check-read-only

DBD::mysql::db do failed: The MySQL server is running with the --read-only option so it cannot execute this statement [for Statement "INSERT INTO `heartbeat`.`heartbeat` (server_id, ts) VALUES ('639407132', UTC_TIMESTAMP())"] at /usr/bin/pt-heartbeat line 5953.

Revision history for this message
monty solomon (monty+launchpad) wrote :

The same is true for --monitor

% pt-heartbeat --host localhost -D heartbeat --monitor

DBD::mysql::db do failed: The MySQL server is running with the --read-only option so it cannot execute this statement [for Statement "INSERT INTO `heartbeat`.`heartbeat` (server_id, ts) VALUES ('639407132', UTC_TIMESTAMP())"] at /usr/bin/pt-heartbeat line 5953.

% pt-heartbeat --host localhost -D heartbeat --monitor --check-read-only

DBD::mysql::db do failed: The MySQL server is running with the --read-only option so it cannot execute this statement [for Statement "INSERT INTO `heartbeat`.`heartbeat` (server_id, ts) VALUES ('639407132', UTC_TIMESTAMP())"] at /usr/bin/pt-heartbeat line 5953.

Revision history for this message
monty solomon (monty+launchpad) wrote :

pt-heartbeat 2.2.19

Server version: 5.7.18-15-log Percona Server (GPL), Release 15, Revision bff2cd9

CentOS release 6.9 (Final)

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1458

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.