主页 / server / 问题 / 1143611
Accepted
George Y
Asked: 2023-09-13 18:00:24 +0800 CST

如何找到 systemd 服务无法启动的确切原因（服务的单元文件设置错误）？

  • 772

这真的很烦人，systemd只回应我的服务文件配置错误，但没有具体指出错误在哪里：

/lib/systemd/system/auto_pgha.service:

[Unit]
Description=PostgreSQL High Availability
After=network.service
After=firewalld.service


[Service]
Type=simple
WorkingDirectory=/etc/repmgr
ExecStartPre=/bin/bash -c 'echo -e "\n"  `date +"%Y/%m/%d %a, %X"`": STARTING \n"  >> pgha.log'
ExecStart=/bin/bash -c "python3 pg_high_availability.py  &>> pgha.log"
Restart=always
RestartSec=3

[Install]
WantedBy=multi-user.target

在目录内/etc/repmgr这两个命令运行得很好。但 systemd 服务只是响应了一个错误：

# systemctl start auto_pgha
Failed to start auto_pgha.service: Unit auto_pgha.service has a bad unit file setting.
See system logs and 'systemctl status auto_pgha.service' for details.

# systemctl status -l auto_pgha
○ auto_pgha.service - PostgreSQL High Availability
     Loaded: bad-setting (Reason: Unit auto_pgha.service has a bad unit file setting.)
......
auto_pgha.service: Unit configuration has fatal error, unit will not be be started.
systemd

1 个回答

  1. Best Answer

    您可以使用该systemd-analyze verify命令。如果我们将您问题的内容放入 中pgha.service，我们会看到：

    $ systemd-analyze verify pgha.service
.../pgha.service:10: Failed to resolve unit specifiers in echo -e "
"  `date +"%Y/%m/%d %a, %X"`": STARTING
"  >> pgha.log: Invalid slot
pgha.service: Unit configuration has fatal error, unit will not be started.
Unit pgha.service has a bad unit file setting.

    您收到此错误是因为 systemd 本身使用%<something>令牌（请参阅手册页的“说明符”部分）systemd.unit(5)。

    你需要写：

    ExecStartPre=/bin/bash -c 'echo -e "\n"  `date +"%%Y/%%m/%%d %%a, %%X"`": STARTING \n"  >> pgha.log'
    • 2

相关问题