为什么即使文件存在，rhel8 aws systemd 服务也会抛出 No such file or directory 错误？

Question

I have a systemd service define on rhel8

[Unit]
Description=Apache Kafka - ZooKeeper
Documentation=http://docs.confluent.io/
After=network.target

[Service]
Type=simple
EnvironmentFile=/app/bin/confluent/etc/kafka/zookenv.properties
User=kafka
Group=kafka
ExecStart=/app/bin/confluent/bin/zookeeper-server-start /app/bin/confluent/etc/kafka/zookeeper.properties
TimeoutStopSec=180
Restart=no

[Install]
WantedBy=multi-user.target

when i start this service i get the below error in journalctl

Jul 09 12:00:51 10.204.142.111 systemd[1]: confluent-zookeeper.service: Failed to load environment files: No such file or directory
Jul 09 12:00:51 10.204.142.111 systemd[1]: confluent-zookeeper.service: Failed to run 'start' task: No such file or directory
Jul 09 12:00:51 10.204.142.111 systemd[1]: confluent-zookeeper.service: Failed with result 'resources'.

the environment file exists in the path and so does the start script and properties files.

this is on RHEL8 aws and trying this for the first time.

the component starts up fine when i run the start script manually from command line.

Answer 1

Check that the path and file for

EnvironmentFile=/app/bin/confluent/etc/kafka/zookenv.properties

are correct

Answer 2

In my case, I had my service file like this

ExecStart=/app/bin/confluent/bin/zookeeper-server-start
EnvironmentFile=/app/bin/confluent/etc/kafka/zookenv.properties

I changed it to

EnvironmentFile=/app/bin/confluent/etc/kafka/zookenv.properties
ExecStart=/app/bin/confluent/bin/zookeeper-server-start

Then I run,

systemctl daemon-reload &&
systemctl restart service-name.service`

Initially, I was using `systemctl start service-name.service` and I guess that didn't make systemd read the environment files properly