Mic*_*key 2 systemctl centos7 google-cloud-sql
我四处寻找,并竭尽全力找出为什么 systemctl 无法启动我的单元。
\n\n我正在尝试将 GCP 的 cloud-sql-proxy 作为 systemd 服务启动。这就是我的cloud-sql-proxy.service
样子。
[Install]\nWantedBy=multi-user.target\n\n[Unit]\nDescription=Cloud SQL Proxy\nRequires=networking.service\nAfter=networking.service\n\n[Service]\nType=simple\nWorkingDirectory=/opt\nExecStart=/opt/cloud_sql_proxy -instances=pupa=tcp:5432 -credential_file=/etc/pupa-240309-5336639b0c06.json\nRestart=always\nStandardOutput=journal\nUser=root\n
Run Code Online (Sandbox Code Playgroud)\n\n我跑sudo systemctl enable cloud-sql-proxy
成功了。然后当我执行时sudo systemctl start cloud-sql-proxy.service
失败并显示以下消息:
Failed to start cloud-sql-proxy.service: Unit not found.\n
Run Code Online (Sandbox Code Playgroud)\n\n以下是更多信息:
\n\n$ ll -al /etc/systemd/system/cloud-sql-proxy.service\n-rw-r--r--. 1 root root 327 May 22 10:56 /etc/systemd/system/cloud-sql-proxy.service\n\n$ sudo systemctl list-unit-files\n...\ncloud-sql-proxy.service enabled\n...\n\n$ systemctl status cloud-sql-proxy\n\xe2\x97\x8f cloud-sql-proxy.service - Cloud SQL Proxy\n Loaded: loaded (/etc/systemd/system/cloud-sql-proxy.service; enabled; vendor preset: disabled)\n Active: failed (Result: resources) since Sun 2019-05-19 15:49:48 UTC; 3 days ago\n Main PID: 1414 (code=exited, status=1/FAILURE)\n\nMay 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service: main process exited, code=exited, status=1/FAILURE\nMay 19 15:49:48 instance-1 systemd[1]: Unit cloud-sql-proxy.service entered failed state.\nMay 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service failed.\nMay 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service holdoff time over, scheduling restart.\nMay 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service failed to schedule restart job: Unit not found.\nMay 19 15:49:48 instance-1 systemd[1]: Unit cloud-sql-proxy.service entered failed state.\nMay 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service failed.\n
Run Code Online (Sandbox Code Playgroud)\n\n对我错过的地方有什么建议吗?\n谢谢!
\n小智 8
Requires
根据我的经验,这是由于找不到其中一项服务造成的。如果您能够启用服务但启动服务返回,Unit not found
请检查 下的服务Requires
。就我而言,我有一个Requires: rpcbind.service
但该服务未安装在我的系统上。
归档时间: |
|
查看次数: |
52781 次 |
最近记录: |