Is this related to https://issues.apache.org/jira/browse/BIGTOP-2165? Konstantin, what did you do to solve this? answered Mar 25 2016 at 11:34 |
So, trying to debug the "/etc/init.d/ignite-hadoop" script ... It starts with: *. /lib/lsb/init-functionsBIGTOP_DEFAULTS_DIR=${BIGTOP_DEFAULTS_DIR-/etc/default}[ -n "${BIGTOP_DEFAULTS_DIR}" -a -r ${BIGTOP_DEFAULTS_DIR}/hadoop ] && . ${BIGTOP_DEFAULTS_DIR}/hadoop[ -n "${BIGTOP_DEFAULTS_DIR}" -a -r ${BIGTOP_DEFAULTS_DIR}/ ] && . ${BIGTOP_DEFAULTS_DIR}/* Should the last line in fact be this? *[ -n "${BIGTOP_DEFAULTS_DIR}" -a -r ${BIGTOP_DEFAULTS_DIR}/ ] && . ${BIGTOP_DEFAULTS_DIR}/ignite-hadoop* basically clueless about shell scripting. Could the problem be in this line? *su -s /bin/bash $SVC_USER -c "cd $WORKING_DIR && $EXEC_PATH --config '$CONF_DIR' start $DAEMON_FLAGS"* answered Mar 25 2016 at 12:00 |
Looks like something went horribly wrong with this package indeed. You're right with your analysis on the default line - the component name is gone missing there. BIGTOP-2165 seems to have something to do with it, but I haven't done anything to fix it - basically I couldn't reproduce it and closed the JIRA as such. I know I've promised to look into this issue but am still distracted with dayjob, unfortunately. Will try to space a few moments during the weekend. Thanks for the investigation! Cos answered Mar 25 2016 at 12:08 |
Group Bigtop-user
asked Mar 25 2016 at 11:26
active Mar 25 2016 at 12:08
posts:4
users:2