无法将流程作为服务启动？ （代码=退出，状态= 203 / EXEC）

时间：2019-11-10 16:54:06

标签： linux redhat

我需要将cassandra进程作为服务启动。为此，按照doc

将以下脚本放在/etc/init.d目录中

这是我放置在init目录中的脚本。

#!/bin/bash
# chkconfig: 2345 99 01
# description: Cassandra

. /etc/rc.d/init.d/functions

CASSANDRA_HOME=/home/cassandra/binaries/cassandra
CASSANDRA_BIN=$CASSANDRA_HOME/bin/cassandra
CASSANDRA_NODETOOL=$CASSANDRA_HOME/bin/nodetool
CASSANDRA_LOG=$CASSANDRA_HOME/logs/cassandra.log
CASSANDRA_PID=$CASSANDRA_HOME/cassandra.pid
CASSANDRA_LOCK=$CASSANDRA_HOME/cassandra.lock
PROGRAM="cassandra"

if [ ! -f $CASSANDRA_BIN ]; then
  echo "File not found: $CASSANDRA_BIN"
  exit 1
fi

RETVAL=0

start() {
  if [ -f $CASSANDRA_PID ] && checkpid `cat $CASSANDRA_PID`; then
    echo "Cassandra is already running."
    exit 0
  fi
  echo -n $"Starting $PROGRAM: "
  $CASSANDRA_BIN -p $CASSANDRA_PID -R >> $CASSANDRA_LOG 2>&1
  sleep 60
  RETVAL=$?
  if [ $RETVAL -eq 0 ]; then
    touch $CASSANDRA_LOCK
    echo_success
  else
    echo_failure
  fi
  echo
  return $RETVAL
}

stop() {
  if [ ! -f $CASSANDRA_PID ]; then
    echo "Cassandra is already stopped."
    exit 0
  fi
  echo -n $"Stopping $PROGRAM: "
#  $CASSANDRA_NODETOOL -h 127.0.0.1 decommission
  if kill `cat $CASSANDRA_PID`; then
    RETVAL=0
    rm -f $CASSANDRA_LOCK
    echo_success
  else
    RETVAL=1
    echo_failure
  fi
  echo
  [ $RETVAL = 0 ]
}

status_fn() {
  if [ -f $CASSANDRA_PID ] && checkpid `cat $CASSANDRA_PID`; then
    echo "Cassandra is running."
    exit 0
  else
    echo "Cassandra is stopped."
    exit 1
  fi
}

case "$1" in
  start)
    start
    ;;
  stop)
    stop
    ;;
  status)
    status_fn
    ;;
  restart)
    stop
    start
    ;;
  *)
    echo $"Usage: $PROGRAM {start|stop|restart|status}"
    RETVAL=3
esac

exit $RETVAL

但是，当执行service cassandra start时，会出现如下错误。 

[root@casstestnode1 init.d]# service cassandra start
Starting cassandra (via systemctl):  Job for cassandra.service failed because the control process exited with error code. See "systemctl status cassandra.service" and "journalctl -xe" for details.
                                                           [FAILED]
[root@casstestnode1 init.d]#

和

[root@casstestnode1 init.d]# systemctl status cassandra.service
● cassandra.service - SYSV: Cassandra
   Loaded: loaded (/etc/rc.d/init.d/cassandra)
   Active: failed (Result: exit-code) since Sun 2019-11-10 22:23:07 IST; 41s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 2624 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited, status=203/EXEC)

Nov 10 22:23:07 casstestnode1 systemd[1]: Starting SYSV: Cassandra...
Nov 10 22:23:07 casstestnode1 systemd[1]: cassandra.service: control process exited, code=exited status=203
Nov 10 22:23:07 casstestnode1 systemd[1]: Failed to start SYSV: Cassandra.
Nov 10 22:23:07 casstestnode1 systemd[1]: Unit cassandra.service entered failed state.
Nov 10 22:23:07 casstestnode1 systemd[1]: cassandra.service failed.
[root@casstestnode1 init.d]#

我重新引导VM，然后再次重试，但错误仍然相同。任何Linux专家，请帮助。

此外，这是journalctl -xe的输出

[root@casstestnode1 init.d]# journalctl -xe
-- Unit session-3153.scope has begun starting up.
Nov 11 23:55:01 casstestnode1 systemd[1]: Started Session 3154 of user cassandra.
-- Subject: Unit session-3154.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-3154.scope has finished starting up.
--
-- The start-up result is done.
Nov 11 23:55:01 casstestnode1 systemd[1]: Starting Session 3154 of user cassandra.
-- Subject: Unit session-3154.scope has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-3154.scope has begun starting up.
Nov 11 23:55:01 casstestnode1 CROND[24584]: (cassandra) CMD (. /home/cassandra/test/cr.sh)
Nov 11 23:55:01 casstestnode1 CROND[24585]: (cassandra) CMD (date >> /home/cassandra/test/ll.txt)
Nov 11 23:55:01 casstestnode1 postfix/pickup[23967]: A5210F1C27: uid=995 from=<cassandra>
Nov 11 23:55:01 casstestnode1 postfix/cleanup[24090]: A5210F1C27: message-id=<20191111182501.A5210F1C27@casstestnode1.localdomain>
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: A5210F1C27: from=<cassandra@casstestnode1.localdomain>, size=837, nrcpt=1 (queue activ
Nov 11 23:55:01 casstestnode1 postfix/pickup[23967]: A8301F1C29: uid=995 from=<cassandra>
Nov 11 23:55:01 casstestnode1 postfix/cleanup[24315]: A8301F1C29: message-id=<20191111182501.A8301F1C29@casstestnode1.localdomain>
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: A8301F1C29: from=<cassandra@casstestnode1.localdomain>, size=845, nrcpt=1 (queue activ
Nov 11 23:55:01 casstestnode1 postfix/local[24021]: A5210F1C27: to=<cassandra@casstestnode1.localdomain>, orig_to=<cassandra>, relay=loc
Nov 11 23:55:01 casstestnode1 postfix/cleanup[24090]: A987AF1C2A: message-id=<20191111182501.A987AF1C2A@casstestnode1.localdomain>
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: A987AF1C2A: from=<>, size=2878, nrcpt=1 (queue active)
Nov 11 23:55:01 casstestnode1 postfix/bounce[24164]: A5210F1C27: sender non-delivery notification: A987AF1C2A
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: A5210F1C27: removed
Nov 11 23:55:01 casstestnode1 postfix/local[23698]: A8301F1C29: to=<cassandra@casstestnode1.localdomain>, orig_to=<cassandra>, relay=loc
Nov 11 23:55:01 casstestnode1 postfix/cleanup[24315]: AA5AFF1C27: message-id=<20191111182501.AA5AFF1C27@casstestnode1.localdomain>
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: AA5AFF1C27: from=<>, size=2886, nrcpt=1 (queue active)
Nov 11 23:55:01 casstestnode1 postfix/bounce[24164]: A8301F1C29: sender non-delivery notification: AA5AFF1C27
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: A8301F1C29: removed
Nov 11 23:55:01 casstestnode1 postfix/local[24021]: A987AF1C2A: to=<cassandra@casstestnode1.localdomain>, relay=local, delay=0.01, delay
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: A987AF1C2A: removed
Nov 11 23:55:01 casstestnode1 postfix/local[23698]: AA5AFF1C27: to=<cassandra@casstestnode1.localdomain>, relay=local, delay=0.01, delay
Nov 11 23:55:01 casstestnode1 postfix/qmgr[2035]: AA5AFF1C27: removed
lines 1923-1959/1959 (END)
[root@casstestnode1 init.d]#
[root@casstestnode1 init.d]#

当我手动运行脚本时

[root@casstestnode1 init.d]#
[root@casstestnode1 init.d]# ./cassandra start
Starting cassandra:                                        [  OK  ]
[root@casstestnode1 init.d]# ./cassandra status
Cassandra is running.
[root@casstestnode1 init.d]#
[root@casstestnode1 init.d]#
[root@casstestnode1 init.d]# service cassandra status
Cassandra is running.
[root@casstestnode1 init.d]# ./cassandra stop
Stopping cassandra:                                        [  OK  ]
[root@casstestnode1 init.d]#
[root@casstestnode1 init.d]# ./cassandra status
Cassandra is stopped.
[root@casstestnode1 init.d]# service cassandra status
Cassandra is stopped.
[root@casstestnode1 init.d]#

3 个答案:

答案 0 :(得分：3)

首先，您可能是copypasteitis的急性形式：

  • init脚本是从一个位置（“互联网”）获得的
  • cassandra文件所在的路径与init脚本假定的路径不同

您的错误声明：

Nov 10 22:23:07 casstestnode1 systemd[1]: cassandra.service: control process exited, code=exited status=203

此203通常意味着在exec*()系统调用时找不到某个可执行文件 （即使用不存在的可执行路径调用了exec）

第二，您使用的是基于systemd的发行版，因此无需使用系统V（旧的，过时的）类型的初始化脚本

让我们看看如何使您既熟悉又最新：

  1. 找到别人应该为cassandra工作的系统单位文件（例如this one）
  2. 侧面打开systemd文档：redhat official systemd doc
  3. 将单位文件放到正确的位置，对其进行编辑
  4. 编辑后，运行systemctl daemon-reload
  5. 现在尝试以systemd-way启动cassandra：systemctl start cassandra

因此，在找到导致错误的原因之后，请使用 现在，针对日志中的错误

答案 1 :(得分：1)

203 EXIT_EXEC   The actual process execution failed (specifically, the execve(2) system call). Most likely this is caused by a missing or non-accessible executable file

按照systemd.exec man page

所以根本原因是

  1. 确切路径不是/etc/rc.d/init.d/cassandra

    您可以使用find /etc -name cassandra

  2. 文件不可执行，因为您可以手动执行。

答案 2 :(得分：0)

我从这个link找到了答案。原因是在#!/bin/bash之前，我的cassandra脚本的开头有一个空白行。删除后，我执行了以下两个命令，此问题已解决。

chkconfig --add cassandra

systemctl daemon-reload
相关问题
最新问题