xCAT 2.10 20150610 build on RH6.5
[root@c910f02c01p22 result]# rpm -qa |grep -i xcat
xCAT-genesis-base-ppc64-2.10-snap201505172314.noarch
xCAT-server-2.10-snap201506020204.noarch
xCAT-confluent-2.10-snap201506102240.noarch
syslinux-xcat-3.86-2.noarch
grub2-xcat-2.02-0.16.el7.snap201505140423.noarch
xCAT-client-2.10-snap201506020204.noarch
xCAT-genesis-scripts-ppc64-2.10-snap201506020204.noarch
xCAT-2.10-snap201506020204.ppc64
xCAT-test-2.10-snap201506102240.noarch
ipmitool-xcat-1.8.11-3.ppc64
conserver-xcat-8.1.16-10.ppc64
perl-xCAT-2.10-snap201506020204.noarch
xCAT-buildkit-2.10-snap201506020204.noarch
[root@c910f02c01p22 result]# service confluent status
==================> Here is no output
[root@c910f02c01p22 result]# ps -ef |grep -i confluent
root 3012 1 0 Jun18 ? 00:00:05 /usr/bin/python /opt/confluent/bin/confluent
root 3013 3012 0 Jun18 ? 00:00:00 /usr/bin/python /opt/confluent/bin/confluent
root 5471 5289 0 02:41 pts/5 00:00:00 grep -i confluent
Take a look at confluent in /etc/init.d and it only process restart, start and stop. Please add status in following code. Thanks!
[root@c910f02c01p22 result]# vi /etc/init.d/confluent
if [ -f /etc/init.d/functions ]; then
. /etc/init.d/functions
LOG_SUCCESS=success
elif [ -f /lib/lsb/init-functions ]; then
. /lib/lsb/init-functions
LOG_SUCCESS=log_success_msg
else
echo "Unknown platform"
exit 1
fi
case $1 in
restart)
if [ -S /var/run/confluent/api.sock ]; then
echo -n 'Stopping Confluent '
/opt/confluent/bin/confetty shutdown /
fi
echo -n 'Starting Confluent '
/opt/confluent/bin/confluent
$LOG_SUCCESS
;;
start)
echo -n 'Starting Confluent '
/opt/confluent/bin/confluent
$LOG_SUCCESS
;;
stop)
echo -n 'Stopping Confluent '
if [ -S /var/run/confluent/api.sock ]; then
/opt/confluent/bin/confetty shutdown /
fi
$LOG_SUCCESS
;;
esac
Hi Ting Ting,
I will need to sync up with Jarrod and get a newer version of confluent uploaded to SF. You are running a 1.1-1 code and that was the first release.. I'm running a later version of confluent which is matched with the repo.
Will get back to you on this...
Victor
This issue is already fixed in Git, Jarrod is planning to release the next build in July. If you want, I can create a sandbox build as we determine the process of building "snapshot" builds
commit 6ab1ae0c3843d5c8b73eb053a5ac0a6737b884ff
Author: Victor Hu vhu@us.ibm.com
Date: Mon May 18 14:00:35 2015 -0400
I will close this defect since it is fixed in the git.
Will test it after Jarrod give the new rpm build.
Just for completeness, let me show the output on my dev machine running a sandbox build of 6/24/15