I'm trying to update my current version of Ganglia core and web (3.0.7) to the
latest versions.
When I try to run
rpmbuild -ta ganglia-3.3.7.tar.gz
I get.
[...]
make: Entering directory `/usr/src/packages/BUILD/ganglia-3.3.7/gmond'
make: `gmond.conf.5' is up to date.
make: Leaving directory `/usr/src/packages/BUILD/ganglia-3.3.7/gmond'
+ /usr/lib/rpm/brp-lib64-linux
s...@suse.de: if you find problems with this script, drop me a note
+ RPM_BUILD_ROOT=/var/tmp/ganglia-3.3.7-buildroot
+ export RPM_BUILD_ROOT
+ test -x /usr/sbin/Check -a 0 = 0 -o -x /usr/sbin/Check -a '!' -z
/var/tmp/ganglia-3.3.7-buildroot
+ echo 'I call /usr/sbin/Check...'
I call /usr/sbin/Check...
+ /usr/sbin/Check
/etc/profile.d/ec2.sh: line 7: `ec2-instance-data': not a valid identifier
error: Bad exit status from /var/tmp/rpm-tmp.31215 (%install)
Any ideas why?
/etc/profile.d/ec2.sh looks like this
##function: ec2-instance-data
ec2-instance-data() {
local ver="latest"
[ "$2" ] && ver="$2"
curl --retry 3 --retry-delay 0 --silent --fail
"http://169.254.169.254/$ver/$1";
[ $? -eq 0 ] && echo
}
##function: ec2-meta-data
ec2-meta-data() {
ec2-instance-data "meta-data/$1" "$2"
}
##function: ec2-instance-id
ec2-instance-id() {
ec2-meta-data instance-id
}
##function: ec2-public-hostname
ec2-public-hostname() {
ec2-meta-data public-hostname
}
##function: ec2-public-ip
ec2-public-ip() {
ec2-meta-data public-ipv4
}
##function: ec2-public-ipv4
ec2-public-ipv4() {
ec2-public-ip
}
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
