堆栈内存溢出
  简体   繁体   English

为 Apache Drill 创建系统单元时出错

[英]Error when creating a systemd unit for Apache Drill

 原文  2019-10-25 07:46:35  0   1    systemd/ apache-drill

问题描述

I have installed Apache Drill and want to start it when the machine boots up.我已经安装了 Apache Drill 并希望在机器启动时启动它。 To do this, I have created the following systemd unit in /etc/systemd/system/drill.service为此，我在/etc/systemd/system/drill.service中创建了以下 systemd 单元

[Unit]
Description=Start/Stop Apache Drill
After=syslog.target network.target

[Service]
Type=forking
User=me
Group=me
ExecStartPre==-/usr/bin/zk_up
ExecStart=/opt/apache/drill/current/bin/drillbit.sh --config /opt/apache/drill/current/conf start
ExecStop=/opt/apache/drill/current/bin/drillbit.sh stop

[Install]
WantedBy=multi-user.target

The issue is that when I issue the command systemctl start drill , the service does not start completely.问题是当我发出命令systemctl start drill ，服务没有完全启动。 It seems to hang and then times out.它似乎挂起，然后超时。 While the process is hung, running the command systemctl status -l drill.service shows the status as activating .当进程挂起时，运行命令systemctl status -l drill.service显示状态为正在activating 。 This is the output of the command systemctl status -l drill.service这是命令systemctl status -l drill.service

drill.service - Start/Stop Apache Drill
   Loaded: loaded (/etc/systemd/system/drill.service; disabled; vendor preset: disabled)
   Active: activating (start) since Fri 2019-10-25 07:32:24 UTC; 55s ago
  Process: 10257 ExecStartPre=/usr/bin/zk_up (code=exited, status=0/SUCCESS)
  Control: 10262 (drillbit.sh)
   CGroup: /system.slice/drill.service
           ├─10262 /bin/bash /opt/apache/drill/current/bin/drillbit.sh --config /opt/apache/drill/current/conf start
           ├─10273 /bin/bash /opt/apache/drill/current/bin/drillbit.sh --config /opt/apache/drill/current/conf start
           ├─10274 find -L / -name java -type f
           └─10275 head -n 1

After the process fails, I see the following message displayed Job for drill.service failed because a timeout was exceeded. See "systemctl status drill.service" and "journalctl -xe" for details.进程失败后，我看到以下消息显示Job for drill.service failed because a timeout was exceeded. See "systemctl status drill.service" and "journalctl -xe" for details. Job for drill.service failed because a timeout was exceeded. See "systemctl status drill.service" and "journalctl -xe" for details.

The command systemctl status -l drill.service after the timeout returns the following超时后的命令systemctl status -l drill.service返回如下

drill.service - Start/Stop Apache Drill
   Loaded: loaded (/etc/systemd/system/drill.service; disabled; vendor preset: disabled)
   Active: failed (Result: timeout) since Fri 2019-10-25 07:33:54 UTC; 3min 3s ago
  Process: 10262 ExecStart=/opt/apache/drill/current/bin/drillbit.sh --config /opt/apache/drill/current/conf start (code=killed, signal=TERM)
  Process: 10257 ExecStartPre=/usr/bin/zk_up (code=exited, status=0/SUCCESS)

And when I run journalctl -xe , I see the following messages当我运行journalctl -xe时，我看到以下消息

Oct 25 07:39:17 drill-1 drillbit.sh[10774]: find: File system loop detected; ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sda’ is part of the same file system loop as ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda’.
Oct 25 07:39:17 drill-1 drillbit.sh[10774]: find: File system loop detected; ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem/2:0/subsystem’ is part of the same file system loop as ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem’.
Oct 25 07:39:17 drill-1 drillbit.sh[10774]: find: File system loop detected; ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem/8:0/subsystem’ is part of the same file system loop as ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem’.
Oct 25 07:39:17 drill-1 drillbit.sh[10774]: find: File system loop detected; ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem/0:38/subsystem’ is part of the same file system loop as ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem’.
Oct 25 07:39:17 drill-1 drillbit.sh[10774]: find: File system loop detected; ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi/subsystem/8:16’ is part of the same file system loop as ‘/sys/bus/cpu/devices/cpu0/node0/cpu1/driver/cpu2/firmware_node/subsystem/devices/PNP0303:00/physical_node/subsystem/devices/00:03/tty/ttyS0/subsystem/ttyS2/device/subsystem/devices/VMBUS:01/firmware_node/2dd1ce17-079e-403c-b352-a1921ee207ee/driver/b6650ff7-33bc-4840-8048-e0676786f393/subsystem/devices/00000000-0001-8899-0000-000000000000/host3/scsi_host/host3/subsystem/host2/device/target2:0:0/subsystem/devices/3:0:1:0/scsi_device/3:0:1:0/subsystem/2:0:0:0/device/block/sda/sda2/subsystem/sdb/bdi’.

Can anyone tell me why am I seeing these messages and what do I need to do to get it working?谁能告诉我为什么我会看到这些消息以及我需要做什么才能使其正常工作？

If I run the command defined for the ExecStart parameter on my terminal itself, Apache Drill start without throwing any errors.如果我在终端上运行为ExecStart参数定义的命令，Apache Drill 将启动而不会引发任何错误。 The command /usr/bin/zk_up just checks if the zookeepers are running before I start Drill and as shown above, this command exits successfully.命令/usr/bin/zk_up只是在我启动 Drill 之前检查 zookeepers 是否正在运行，如上所示，该命令成功退出。

1 个解决方案

解决方案1
 1 已采纳  2019-10-25 08:02:44

When I closely looked at the output of the systemctl status -l drill.service command, I saw that the culprit that was printing the file system loop messages was the find command and that command was looking for java .当我仔细查看systemctl status -l drill.service命令的 output 时，我发现打印文件系统循环消息的罪魁祸首是find命令，而该命令正在寻找java 。 I added the JAVA_HOME to the environment in the systemd file and it worked.我将JAVA_HOME添加到 systemd 文件中的环境中，它可以工作。 My new systemd unit is我的新systemd单元是

[Unit]
Description=Start/Stop Apache Drill
After=syslog.target network.target

[Service]
Type=forking
User=me
Group=me
Environment="JAVA_HOME=/opt/java/current"
ExecStartPre==-/usr/bin/zk_up
ExecStart=/opt/apache/drill/current/bin/drillbit.sh --config /opt/apache/drill/current/conf start
ExecStop=/opt/apache/drill/current/bin/drillbit.sh stop

[Install]
WantedBy=multi-user.target

where /opt/java/current is where my $JAVA_HOME is. /opt/java/current是我的$JAVA_HOME所在的位置。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 系统单元的setsockopt - 错误：“不允许操作” - setsockopt for systemd unit - error: "Operation not permited" 如何使用Systemd Unit配置的'when'条件 - How to use 'when' conditional with Systemd Unit configs 启动失败并使用playframework的systemd单位文件时返回错误消息 - Return error message when start-up fails with systemd unit file for playframework 当使用AWS日志记录驱动程序配置运行Docker容器时，Systemd Unit引发错误 - Systemd Unit is throwing an error when a docker container is being run with AWS logging driver configs 从systemd单元文件运行时，无法打开目录 - When running from systemd unit file, unable to open directory systemd：如何在覆盖单元文件时清除条目 - systemd: How to clear an entry when overriding a unit file systemd 单元启动/停止时的 Qt/C++ 信号 - Qt/C++ signal when systemd unit is started/stopped 多个目标需要并在目标停止时停止的 systemd 单元 - systemd unit that's needed by multiple targets and stops when target stops 使用systemd自动启动Python3脚本时出错 - Error when autostarting Python3 script with systemd 在systemd上发生错误时，应用程序不退出 - Application does not exit when an error happening on systemd
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM