Systemctl status

systemctl status
SERVER_NAME
   State: degraded
    Jobs: 0 queued
  Failed: 2 units
   Since: Sat 2019-12-07 07:24:53 UTC; 2 weeks 4 days ago
   .../...

systemctl status SERVICE
System has not been booted with systemd as init system (PID 1). Can't operate.

● ip-10-12-0-111
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Wed 2023-07-05 11:24:48 UTC; 1 day 6h ago
   CGroup: /
           ├─user.slice
           │ └─user-1000.slice
           │   ├─[email protected] …
           │   │ └─init.scope
           │   │   ├─1331 /lib/systemd/systemd --user
           │   │   └─1332 (sd-pam)

Services examples

• systemctl status qemu-kvm
• systemctl status docker
• systemctl status containerd
• systemctl status openvpn-server@server
• systemctl status cron
• systemctl status oscapd
• systemctl status rsyslog
• systemctl status nginx
• systemctl status nfs-server
• systemctl status postgresql
• systemctl status prometheus
• systemctl status apt-daily
• systemctl status php7.2-fpm
• systemctl status kubelet
• systemctl status jcagent.service

Related commands

• systemctl --failed
• systemctl enable
• snap services

See also

• Systemd services: systemctl [status | is-active | start | daemon-reload | stop | mask | reload | restart | reboot | enable | disable | cat], systemctl list-units, systemctl list-timers, systemctl --failed, systemctl get-default, systemctl --help, .service, .timer, .socket, systemctl restart elasticsearch.service, systemctl status apt-daily, systemctl status oscapd
• systemd-journald: journalctl, /etc/systemd/journald.conf, journalctl logs, journalctl --list-boots, journalctl --disk-usage, journalctl -u kubelet, journalctl -u prometheus, journalctl --help