systemctl list-units --failed

Issues related to applications and software problems
Post Reply
mySKILLZ
Posts: 35
Joined: 2018/02/21 09:10:21

systemctl list-units --failed

Post by mySKILLZ » 2018/02/21 10:35:17

guys
you should see this maybe you'd help

[root@skillz ~]# systemctl status httpd.service
● httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd.service; disabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2018-02-21 06:00:01 EST; 26min ago
Docs: man:httpd(8)
man:apachectl(8)
Process: 6481 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
Process: 6479 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
Main PID: 6479 (code=exited, status=1/FAILURE)

Feb 21 06:00:01 skillz systemd[1]: Starting The Apache HTTP Server...
Feb 21 06:00:01 skillz systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Feb 21 06:00:01 skillz kill[6481]: kill: cannot find process ""
Feb 21 06:00:01 skillz systemd[1]: httpd.service: control process exited, code=exited status=1
Feb 21 06:00:01 skillz systemd[1]: Failed to start The Apache HTTP Server.
Feb 21 06:00:01 skillz systemd[1]: Unit httpd.service entered failed state.
Feb 21 06:00:01 skillz systemd[1]: httpd.service failed.
[root@skillz ~]# systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● httpd.service loaded failed failed The Apache HTTP Server
● kdump.service loaded failed failed Crash recovery kernel arming

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.

2 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: systemctl list-units --failed

Post by TrevorH » 2018/02/21 11:28:21

Read /var/log/httpd/*error* and see if there are clues there.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Post Reply