systemctl

Autossh script running as systemctl start SERVICE works but systemctl enable SERVICE failed

送分小仙女□ 提交于 2021-02-10 16:16:54
问题 We are trying to get autossh to connect to remote server at boot time in Ubuntu 16.04.2. So we use systemctl to do the job. The script is as following: [Unit] Description=Keeps a tunnel to 'remote server' open After=network.target [Service] ExecStart=/usr/bin/autossh -NR 83232:localhost:22 -i /home/user/.ssh/id_rsa REMOTE_USER@REMOTE_IP [Install] WantedBy=multi-user.target It would work fine if we start the service by using start systemctl start SERVICE But it would fail if we use enable

How to debug a failed systemctl service (code=exited, status=217/USER)?

£可爱£侵袭症+ 提交于 2021-02-06 15:25:46
问题 I'm trying to add my first service on rhel7 (which resides in AWS/EC2), but - the service is not configured correctly - as I get: [ec2-user@ip-172-30-1-96 ~]$ systemctl status clouddirectd.service -l ● clouddirectd.service - CloudDirect Daemon Loaded: loaded (/usr/lib/systemd/system/clouddirectd.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2018-01-09 16:09:42 EST; 8s ago Main PID: 10064 (code=exited, status=217/USER) Jan 09 16:09

How to debug a failed systemctl service (code=exited, status=217/USER)?

烈酒焚心 提交于 2021-02-06 15:24:08
问题 I'm trying to add my first service on rhel7 (which resides in AWS/EC2), but - the service is not configured correctly - as I get: [ec2-user@ip-172-30-1-96 ~]$ systemctl status clouddirectd.service -l ● clouddirectd.service - CloudDirect Daemon Loaded: loaded (/usr/lib/systemd/system/clouddirectd.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2018-01-09 16:09:42 EST; 8s ago Main PID: 10064 (code=exited, status=217/USER) Jan 09 16:09

Systemctl - Failed at step Group spawning

你离开我真会死。 提交于 2021-01-27 05:21:11
问题 I have a problem with automatic running of service. I would like to run a script after user login. Once I have succeeded, however when I tried to automatize it, I'm getting an error and I can't find a mistake. Service: Description=Service desc [Service] Type=oneshot Environment=DISPLAY=:0.0 Environment=XAUTHORITY=/home/albert/.Xauthority Environment=HOME=/home/albert/ User=albert Group=albert RemainAfterExit=true StandardOutput=journal ExecStart=/home/albert/.startup-script.sh [Install]

systemctl error in docker 'Failed to connect to bus: No such file or directory'

混江龙づ霸主 提交于 2020-12-31 13:59:06
问题 I am using Ubuntu-16.04 image with docker to test my cookbook in local. While doing kitchen converge , I am getting the following error. I figured out systemctl is not working properly. Can someone please help me to fix this problem OR any other way to achieve the same thing? [2017-11-30T15:22:30+00:00] INFO: Running queued delayed notifications before re-raising exception Running handlers: [2017-11-30T15:22:30+00:00] ERROR: Running exception handlers Running handlers complete [2017-11-30T15

Tomcat 9 no longer starting using systemctl but will start manually

空扰寡人 提交于 2020-12-15 02:01:29
问题 Been digging on this for a while. I reviewed multiple articles on this issue. This one was the closest: Tomcat 8 on CentOS 7 does not start as service (but it starts manually ....) The difference being that I am running Tomcat 9.0.33. Here are the particulars: java version "1.8.0_121"\ Java(TM) SE Runtime Environment (build 1.8.0_121-b13)\ Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)\ Tomcat 9.0.33 NAME="CentOS Linux"\ VERSION="7 (Core)"\ ID="centos"\ ID_LIKE="rhel fedora"

Tomcat 9 no longer starting using systemctl but will start manually

微笑、不失礼 提交于 2020-12-15 01:53:42
问题 Been digging on this for a while. I reviewed multiple articles on this issue. This one was the closest: Tomcat 8 on CentOS 7 does not start as service (but it starts manually ....) The difference being that I am running Tomcat 9.0.33. Here are the particulars: java version "1.8.0_121"\ Java(TM) SE Runtime Environment (build 1.8.0_121-b13)\ Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)\ Tomcat 9.0.33 NAME="CentOS Linux"\ VERSION="7 (Core)"\ ID="centos"\ ID_LIKE="rhel fedora"

systemctl not found while building mongo image

泪湿孤枕 提交于 2020-12-08 16:48:15
问题 I am trying to build a mongo 4.4 image based on the official image Dockerfile but I am running into an issue with systemctl not found. The image itself has a line to remove it after setup, but not sure where it came from. Any ideas? Setting up mongodb-org-database-tools-extra (4.4.0) ... Setting up librtmp1:amd64 (2.4+20151223.gitfa8646d.1-1) ... Setting up libkrb5support0:amd64 (1.16-2ubuntu0.1) ... Setting up krb5-locales (1.16-2ubuntu0.1) ... Setting up libkeyutils1:amd64 (1.5.9-9.2ubuntu2

systemctl not found while building mongo image

不打扰是莪最后的温柔 提交于 2020-12-08 16:46:42
问题 I am trying to build a mongo 4.4 image based on the official image Dockerfile but I am running into an issue with systemctl not found. The image itself has a line to remove it after setup, but not sure where it came from. Any ideas? Setting up mongodb-org-database-tools-extra (4.4.0) ... Setting up librtmp1:amd64 (2.4+20151223.gitfa8646d.1-1) ... Setting up libkrb5support0:amd64 (1.16-2ubuntu0.1) ... Setting up krb5-locales (1.16-2ubuntu0.1) ... Setting up libkeyutils1:amd64 (1.5.9-9.2ubuntu2

systemctl not found while building mongo image

眉间皱痕 提交于 2020-12-08 16:39:54
问题 I am trying to build a mongo 4.4 image based on the official image Dockerfile but I am running into an issue with systemctl not found. The image itself has a line to remove it after setup, but not sure where it came from. Any ideas? Setting up mongodb-org-database-tools-extra (4.4.0) ... Setting up librtmp1:amd64 (2.4+20151223.gitfa8646d.1-1) ... Setting up libkrb5support0:amd64 (1.16-2ubuntu0.1) ... Setting up krb5-locales (1.16-2ubuntu0.1) ... Setting up libkeyutils1:amd64 (1.5.9-9.2ubuntu2