我到处寻找,只是为了我的生命,弄明白为什么systemctl不启动我的单位。
我正在尝试将GCP的云-sql-代理作为一个系统服务启动。这就是我的cloud-sql-proxy.service的样子。
[Install]
WantedBy=multi-user.target
[Unit]
Description=Cloud SQL Proxy
Requires=networking.service
After=networking.service
[Service]
Type=simple
WorkingDirectory=/opt
ExecStart=/opt/cloud_sql_proxy -instances=pupa=tcp:5432 -credential_file=/etc/pupa-240309-5336639b0c06.json
Restart=always
StandardOutput=journal
User=root我成功地运行了sudo systemctl enable cloud-sql-proxy。然后,当我执行sudo systemctl start cloud-sql-proxy.service时,它失败了,这条消息是:
Failed to start cloud-sql-proxy.service: Unit not found.以下是更多信息:
$ ll -al /etc/systemd/system/cloud-sql-proxy.service
-rw-r--r--. 1 root root 327 May 22 10:56 /etc/systemd/system/cloud-sql-proxy.service
$ sudo systemctl list-unit-files
...
cloud-sql-proxy.service enabled
...
$ systemctl status cloud-sql-proxy
● cloud-sql-proxy.service - Cloud SQL Proxy
Loaded: loaded (/etc/systemd/system/cloud-sql-proxy.service; enabled; vendor preset: disabled)
Active: failed (Result: resources) since Sun 2019-05-19 15:49:48 UTC; 3 days ago
Main PID: 1414 (code=exited, status=1/FAILURE)
May 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service: main process exited, code=exited, status=1/FAILURE
May 19 15:49:48 instance-1 systemd[1]: Unit cloud-sql-proxy.service entered failed state.
May 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service failed.
May 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service holdoff time over, scheduling restart.
May 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service failed to schedule restart job: Unit not found.
May 19 15:49:48 instance-1 systemd[1]: Unit cloud-sql-proxy.service entered failed state.
May 19 15:49:48 instance-1 systemd[1]: cloud-sql-proxy.service failed.对我错过的地方有什么建议吗?谢谢!
发布于 2019-05-23 09:23:10
你能在/usr/lib/systemd/system/cloud_sql_proxy.service里试试这样的东西吗?
[Unit]
Description=GCP CloudSQL Proxy
After=network.target
[Service]
User=root
Group=root
WorkingDirectory=/usr/bin
Type=forking
RemainAfterExit=yes
ExecStart=/bin/sh -c '/usr/bin/nohup /usr/local/cloud_sql_proxy -instances=${INSTANCE_CONNECTION_NAME} -credential_file=${CREDENTIAL_FILE} &'
StandardOutput=journal
KillMode=process
[Install]
WantedBy=multi-user.target配置文件将是/usr/lib/systemd/system/cloud_sql_proxy.service.d/settings.conf。
[Service]
Environment=INSTANCE_CONNECTION_NAME=[YOUR CONNECTION NAME]
Environment=CREDENTIAL_FILE=[PATH TO YOUR CREDENTIAL FILE]发布于 2021-02-25 19:57:48
根据我的经验,这是由于没有找到Requires中的一个服务。如果您能够启用您的服务,但是启动您的服务,则返回Unit not found,然后检查Requires下的服务。在我的例子中,我有一个Requires: rpcbind.service,但是该服务没有安装在我的系统上。
发布于 2019-05-27 17:01:38
我认为您正在遵循这个[1]链接,但是如果您查看底部,它们会指定如果您想在Centos 7上执行相同的操作,则需要使用不同的文件。也许这就是它失败的原因。
对于Centos 7,请使用以下内容:
[Install]
WantedBy=multi-user.target
[Unit]
Description=Google Cloud Compute Engine SQL Proxy
Requires=network.target
After=network.target
[Service]
Type=simple
WorkingDirectory=/usr/local/bin
ExecStart=/usr/local/bin/cloud_sql_proxy -dir=/var/run/cloud-sql-proxy -instances==tcp:3306 -credential_file=/var/local/cloud-sql-proxy/.json
Restart=always
StandardOutput=journalhttps://serverfault.com/questions/968524
复制相似问题