pt-stalk fails to start if $HOME environment variable is not set

Bug #1266869 reported by Valery Panov on 2014-01-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Frank Cizmich

Bug Description

pt-stalk fails to start if $HOME environment variable is not set:

[root@test01 ~]# unset HOME
[root@test01 root]# pt-stalk --daemonize --dest /mnt/data/pt-stalk --threshold 70
/usr/bin/pt-stalk: line 257: HOME: unbound variable

This makes sense e.g. when run from the init script.
The issue can be easily workarounded by exporting HOME.

BTW it would also be good to have init script for the pt-stalk.
I've attached my version which is designed to work on CentOS, feel free to use it if you need it.

Related branches

Daniel Nichter: Pending requested 2015-01-13
Valery Panov (valery-panov) wrote :
Jericho Rivera (jericho-rivera) wrote :

Confirmed on a new centos 6.4 instance.

[root@localhost vagrant]# unset HOME
[root@localhost vagrant]# pt-stalk --daemonize --dest /mnt/data/pt-stalk --threshold 70
/usr/bin/pt-stalk: line 257: HOME: unbound variable
[root@localhost vagrant]# rpm -qa|grep percona-toolkit

@Valery - thanks for sharing your pt-stalk init script

Changed in percona-toolkit:
status: New → Confirmed
tags: added: pt-stalk
Changed in percona-toolkit:
status: Confirmed → In Progress
importance: Undecided → Low
assignee: nobody → Frank Cizmich (frank-cizmich)
milestone: none → 2.2.13
Changed in percona-toolkit:
status: In Progress → Fix Committed
Changed in percona-toolkit:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers