pt-stalk doesn't check pt-collect

Bug #884504 reported by Fernando Ipar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Fix Released
Medium
Daniel Nichter
1.0
Fix Released
Medium
Daniel Nichter

Bug Description

This is a feature request:

pt-stalk looks for pt-collect in a hardcoded location (~/bin/pt-collect) if not configured.
However this is done at the time the trouble condition is triggered, meaning it may abort the chance for gathering data if pt-stalk is left running unattended without a properly configured or executable pt-collect.

I'm attaching a simple fix for this that would make pt-stalk abort upon start up if it finds $COLLECT isn't executable. t

Tags: pt-stalk

Related branches

Revision history for this message
Fernando Ipar (fipar) wrote :
Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

Thanks Fernando. Since pt-stalk and pt-collect are so closely related, this is more than a feature request, it's a bug! After all, pt-stalk is almost useless if pt-collect isn't available, so pt-stalk should really check that it is before it's too late.

summary: - pt-stalk should check for pt-collect at start time
+ pt-stalk doesn't check pt-collect
Changed in percona-toolkit:
importance: Undecided → Medium
milestone: none → 2.0-beta2
Changed in percona-toolkit:
assignee: nobody → Daniel Nichter (daniel-nichter)
status: New → Fix Committed
Revision history for this message
Daniel Nichter (daniel-nichter) wrote :

Since pt-collect is being merge into pt-stalk, is will no longer be an issue.

Revision history for this message
Fernando Ipar (fipar) wrote :

Great news. This will probably take care of at least one other open bug report I have on pt-stalk.
Thanks.

Changed in percona-toolkit:
status: Fix Committed → Fix Released
Changed in percona-toolkit:
status: Fix Released → Fix Committed
Changed in percona-toolkit:
status: Fix Committed → Fix Released
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-430

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.