Linux control process exited

Docker: How to fix «Job for docker.service failed because the control process exited with error code»

I’m trying to use docker in Manjaro (my kernel version is 4.19) and it is not working. After running sudo pamac install docker I run sudo systemctl start docker.service and receive this message:

Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. 

● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2019-04-29 12:28:44 -03; 39s ago Docs: https://docs.docker.com Process: 17769 ExecStart=/usr/bin/dockerd -H fd:// (code=exited, status=1/FAILURE) Main PID: 17769 (code=exited, status=1/FAILURE) abr 29 12:28:44 tamer-pc systemd[1]: docker.service: Service RestartSec=100ms expired, scheduling restart. abr 29 12:28:44 tamer-pc systemd[1]: docker.service: Scheduled restart job, restart counter is at 3. abr 29 12:28:44 tamer-pc systemd[1]: Stopped Docker Application Container Engine. abr 29 12:28:44 tamer-pc systemd[1]: docker.service: Start request repeated too quickly. abr 29 12:28:44 tamer-pc systemd[1]: docker.service: Failed with result 'exit-code'. abr 29 12:28:44 tamer-pc systemd[1]: Failed to start Docker Application Container Engine. 

-- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit docker.service has entered the 'failed' state with result 'exit-code'. abr 29 12:28:44 tamer-pc systemd[1]: Failed to start Docker Application Container Engine. -- Subject: A unidade docker.service falhou -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A unidade docker.service falhou. -- -- O resultado é failed. abr 29 12:28:44 tamer-pc systemd[1]: docker.socket: Failed with result 'service-start-limit-hit'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit docker.socket has entered the 'failed' state with result 'service-start-limit-hit'. abr 29 12:29:02 tamer-pc dbus-daemon[650]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='> abr 29 12:29:02 tamer-pc dbus-daemon[650]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.> abr 29 12:29:24 tamer-pc sudo[17879]: tamer : TTY=pts/0 ; PWD=/etc/docker ; USER=root ; COMMAND=/usr/bin/systemctl stat> abr 29 12:29:24 tamer-pc sudo[17879]: pam_unix(sudo:session): session opened for user root by (uid=0) abr 29 12:29:24 tamer-pc sudo[17879]: pam_unix(sudo:session): session closed for user root lines 1703-1725/1725 (END) 

I’m looking for resolution for two days but whatever I read seems not to be exactly the same as my problem.

Источник

unit.service failed because the control process exited with error code. What does this error mean?

I am trying to start a script in /etc/init.d in ubuntu 16.04 . but it gives me an error. I am able to execute each step in that (scheduler_slave) unit manually. However it fails while executing through the script. Could anyone explain what is the meaning of the below error/ I am totally a newbie to this field and trying to figure out why this error comes. Please let me know if I missed any detail. command:

sudo /etc/init.d/scheduler_slave start 

[. ] Starting scheduler_slave (via systemctl): scheduler_slave.serviceJob for scheduler_slave.service failed because the control process exited with error code. See "systemctl status scheduler_slave.service" and "journalctl -xe" for details. failed! 

● scheduler_slave.service - LSB: Start scheduler slave at boot Loaded: loaded (/etc/init.d/scheduler_slave; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-03-12 13:03:39 IST; 1h 26min ago Docs: man:systemd-sysv-generator(8) Process: 7315 ExecStart=/etc/init.d/scheduler_slave start (code=exited, status=203/EXEC) 

 -- A new session with the ID 80 has been created for the user ubuntu. -- -- The leading process of the session is 7377. Mar 12 14:29:24 ubuntu systemd[1]: Started Session 80 of user ubuntu. -- Subject: Unit session-80.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-80.scope has finished starting up. -- -- The start-up result is done. Mar 12 14:32:56 ubuntu sudo[7547]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/journalctl -xe Mar 12 14:32:56 ubuntu sudo[7547]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) Mar 12 14:34:29 ubuntu sudo[7547]: pam_unix(sudo:session): session closed for user root Mar 12 14:34:36 ubuntu sudo[7551]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/etc/init.d/scheduler_slave start Mar 12 14:34:36 ubuntu sudo[7551]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) Mar 12 14:34:36 ubuntu systemd[1]: Starting LSB: Start scheduler slave at boot. -- Subject: Unit scheduler_slave.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit scheduler_slave.service has begun starting up. Mar 12 14:34:36 ubuntu systemd[7562]: scheduler_slave.service: Failed at step EXEC spawning /etc/init.d/scheduler_slave: Exec format error -- Subject: Process /etc/init.d/scheduler_slave could not be executed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The process /etc/init.d/scheduler_slave could not be executed and failed. -- -- The error number returned by this process is 8. Mar 12 14:34:36 ubuntu systemd[1]: scheduler_slave.service: Control process exited, code=exited status=203 Mar 12 14:34:36 ubuntu systemd[1]: Failed to start LSB: Start scheduler slave at boot. -- Subject: Unit scheduler_slave.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit scheduler_slave.service has failed. -- -- The result is failed. Mar 12 14:34:36 ubuntu systemd[1]: scheduler_slave.service: Unit entered failed state. Mar 12 14:34:36 ubuntu systemd[1]: scheduler_slave.service: Failed with result 'exit-code'. Mar 12 14:34:36 ubuntu sudo[7551]: pam_unix(sudo:session): session closed for user root Mar 12 14:34:47 ubuntu sudo[7594]: ubuntu : TTY=pts/1 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/bin/journalctl -xe Mar 12 14:34:47 ubuntu sudo[7594]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0) 

Источник

Job for httpd.service failed because the control process exited with error code. See «systemctl status httpd.service» and «journalctl -xe» for details

This is due to non-existance of «/var/www/html» directory. run mkdir «/var/www/html» , hope it will solved. I have installed a fresh copy of Centos 7. Then I restarted Apache but the Apache failed to start. I have 3 days stucked in this issue. Even the support can not figure out the error.

sudo service httpd start Failed to start apache : Job for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details. httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-05-09 16:08:02 BST; 59s ago Docs: man:httpd(8) man:apachectl(8) Main PID: 5710 (code=exited, status=1/FAILURE) May 09 16:08:02 mike079.startdedicated.de systemd[1]: Starting The Apache HTTP Server. May 09 16:08:02 mike079.startdedicated.de httpd[5710]: (98)Address already in use: AH00072: make_sock: could not bind to address 85.25.12.20:80 May 09 16:08:02 startdedicated.de httpd[5710]: no listening sockets available, shutting down May 09 16:08:02 startdedicated.de httpd[5710]: AH00015: Unable to open logs May 09 16:08:02 startdedicated.de systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE May 09 16:08:02.startdedicated.de kill[5712]: kill: cannot find process "" May 09 16:08:02 .startdedicated.de systemd[1]: httpd.service: control process exited, code=exited status=1 May 09 16:08:02startdedicated.de systemd[1]: Failed to start The Apache HTTP Server. May 09 16:08:02 startdedicated.de systemd[1]: Unit httpd.service entered failed state. May 09 16:08:02 mike: httpd.service failed. 

Источник

Tomcat: Can’t start tomcat after installing it on Ubuntu: «Job for tomcat.service failed because the control process exited with error code.»

I followed the steps https://www.digitalocean.com/community/tutorials/how-to-install-apache-tomcat-8-on-ubuntu-16-04 to install tomcat 8.5.24 on Ubuntu 16.04, till running sudo ufw allow 8080 in «Step 6: Adjust the Firewall and Test the Tomcat Server». Then I can’t start tomcat,

$ sudo systemctl start tomcat Job for tomcat.service failed because the control process exited with error code. See "systemctl status tomcat.service" and "journalctl -xe" for details. 

and the link http://localhost:8080/ doesn’t work in both firefox and google chrome browsers. I was wondering how to solve the problem. The following details are what I followed the above output messages of sudo systemctl start tomcat . It seems that /opt/tomcat/bin/startup.sh succeeded while /opt/tomcat/bin/shutdown.sh failed. Much appreciate your help!

$ systemctl status tomcat.service ● tomcat.service - Apache Tomcat Web Application Container Loaded: loaded (/etc/systemd/system/tomcat.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Fri 2017-12-01 18:55:30 EST; 2s ago Process: 19490 ExecStop=/opt/tomcat/bin/shutdown.sh (code=exited, status=1/FAILURE) Process: 19478 ExecStart=/opt/tomcat/bin/startup.sh (code=exited, status=0/SUCCESS) Main PID: 19440 (code=exited, status=127) Dec 01 18:55:30 ocean systemd[1]: tomcat.service: Control process exited, code=exited status=1 Dec 01 18:55:30 ocean systemd[1]: Failed to start Apache Tomcat Web Application Container. Dec 01 18:55:30 ocean systemd[1]: tomcat.service: Unit entered failed state. Dec 01 18:55:30 ocean systemd[1]: tomcat.service: Failed with result 'exit-code'. $ journalctl -xe -- Unit tomcat.service has begun starting up. Dec 01 18:51:24 ocean startup.sh[18873]: Existing PID file found during start. Dec 01 18:51:24 ocean startup.sh[18873]: Removing/clearing stale PID file. Dec 01 18:51:24 ocean startup.sh[18873]: Tomcat started. Dec 01 18:51:24 ocean shutdown.sh[18885]: PID file found but no matching process was found. Stop aborted. Dec 01 18:51:24 ocean systemd[1]: tomcat.service: Control process exited, code=exited status=1 Dec 01 18:51:24 ocean systemd[1]: Failed to start Apache Tomcat Web Application Container. -- Subject: Unit tomcat.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tomcat.service has failed. -- -- The result is failed. Dec 01 18:51:24 ocean systemd[1]: tomcat.service: Unit entered failed state. Dec 01 18:51:24 ocean systemd[1]: tomcat.service: Failed with result 'exit-code'. Dec 01 18:51:34 ocean systemd[1]: tomcat.service: Service hold-off time over, scheduling restart. Dec 01 18:51:34 ocean systemd[1]: Stopped Apache Tomcat Web Application Container. -- Subject: Unit tomcat.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tomcat.service has finished shutting down. Dec 01 18:51:34 ocean systemd[1]: Starting Apache Tomcat Web Application Container. -- Subject: Unit tomcat.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tomcat.service has begun starting up. Dec 01 18:51:35 ocean startup.sh[18896]: Existing PID file found during start. Dec 01 18:51:35 ocean startup.sh[18896]: Removing/clearing stale PID file. Dec 01 18:51:35 ocean startup.sh[18896]: Tomcat started. Dec 01 18:51:35 ocean shutdown.sh[18908]: PID file found but no matching process was found. Stop aborted. Dec 01 18:51:35 ocean systemd[1]: tomcat.service: Control process exited, code=exited status=1 Dec 01 18:51:35 ocean systemd[1]: Failed to start Apache Tomcat Web Application Container. -- Subject: Unit tomcat.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit tomcat.service has failed. -- -- The result is failed. Dec 01 18:51:35 ocean systemd[1]: tomcat.service: Unit entered failed state. Dec 01 18:51:35 ocean systemd[1]: tomcat.service: Failed with result 'exit-code'. 

$ java --version java 9.0.1 Java(TM) SE Runtime Environment (build 9.0.1+11) Java HotSpot(TM) 64-Bit Server VM (build 9.0.1+11, mixed mode) $ javac --version javac 9.0.1 

cd /opt/tomcat/bin sudo ./catalina.sh run 

Источник