Systemd: Difference between revisions

From DWIKI
mNo edit summary
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
 




Line 6: Line 8:
*[http://www.freedesktop.org/wiki/Software/systemd/ http://www.freedesktop.org/wiki/Software/systemd/]  
*[http://www.freedesktop.org/wiki/Software/systemd/ http://www.freedesktop.org/wiki/Software/systemd/]  
*[https://wiki.ubuntu.com/systemd https://wiki.ubuntu.com/systemd]  
*[https://wiki.ubuntu.com/systemd https://wiki.ubuntu.com/systemd]  
*[https://wiki.archlinux.org/index.php/Systemd Creating systemd service]
*[https://wiki.archlinux.org/index.php/Systemd Creating systemd service]  
*[https://wiki.ubuntu.com/SystemdForUpstartUsers https://wiki.ubuntu.com/SystemdForUpstartUsers]  
*[https://wiki.ubuntu.com/SystemdForUpstartUsers https://wiki.ubuntu.com/SystemdForUpstartUsers]  
*[https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units How To Use Systemctl to Manage Systemd Services and Units]  
*[https://www.digitalocean.com/community/tutorials/how-to-use-systemctl-to-manage-systemd-services-and-units How To Use Systemctl to Manage Systemd Services and Units]  
Line 13: Line 15:
*[https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Predictable Network Interface Names]  
*[https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Predictable Network Interface Names]  
*[[https://blog.darknedgy.net/technology/2020/05/02/0/index.html#tech-critique https://blog.darknedgy.net/technology/2020/05/02/0/index.html#tech-critique]  
*[[https://blog.darknedgy.net/technology/2020/05/02/0/index.html#tech-critique https://blog.darknedgy.net/technology/2020/05/02/0/index.html#tech-critique]  
*[https://mohsensy.github.io/sysadmin/2018/08/19/systemd-service-tutorial.html Systemd service tutorial]
*[https://www.freedesktop.org/wiki/Software/systemd/dbus/ https://www.freedesktop.org/wiki/Software/systemd/dbus/ Systemd and dbus]
*[https://www.thegeekdiary.com/how-to-boot-into-rescue-mode-or-emergency-mode-through-systemd-in-centos-rhel-7-and-8/ Single user/emergency]


([https://www.thegeekdiary.com/how-to-boot-into-rescue-mode-or-emergency-mode-through-systemd-in-centos-rhel-7-and-8/ Single user/emergency]
= Locations =


=Locations=
  /etc/systemd
  /etc/systemd
  /usr/lib/systemd/
  /usr/lib/systemd/
  /lib/systemd
  /lib/systemd


 
= HOWTO =
== Timers ==
*[https://opensource.com/article/20/7/systemd-timers https://opensource.com/article/20/7/systemd-timers]
*[https://wiki.archlinux.org/title/Systemd/Timers https://wiki.archlinux.org/title/Systemd/Timers]
man systemd.timer
=== List active timers ===
systemctl list-timers
=== List all timers ===
systemctl list-timers --all
=== Create timer ===
systemctl enable fstrim.timer


== Auto restart crashed services ==
systemctl edit elasticsearch.service
add:
[Service]
Restart=always
then
systemctl daemon-reload
systemctl restart elasticsearch.service
And to get an email when service gets restarted: https://dev.to/setevoy/linux-systemd-unit-files-edit-restart-on-failure-and-email-notifications-5h3k


= FAQ =
= FAQ =


==Analyze boot processes==
== Fix journal size ==
 
journalctl --vacuum-time=10d
 
or
 
journalctl --vacuum-size=1G
 
===Journal settings===
/etc/systemd/journald.conf
SystemMaxUse=1G
and then
systemctl restart systemd-journald.service
 
 
== Analyze boot processes ==
 
  systemd-analyze blame
  systemd-analyze blame


 
 
 


== Systemd and DNS ==
== Systemd and DNS ==


  resolvectl status
  resolvectl status
=== Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found. ===
Means systemd-resolved is not running
Restart:
Restart:
  systemctl restart systemd-resolved
  systemctl restart systemd-resolved
     
     
 
=== Add nameserver ===
Sacrifice a chicken
 
=== Flush caches ===
systemd-resolve --flush-caches


== All status ==
== All status ==
Line 68: Line 148:


  systemctl daemon-reexec
  systemctl daemon-reexec
==Status==
=== Active: inactive (dead) ===
parameter ActiveState would return inactive
SubState returns dead

Revision as of 19:36, 20 May 2022

 


Documentation

Locations

/etc/systemd
/usr/lib/systemd/
/lib/systemd

 


HOWTO

Timers

man systemd.timer

List active timers

systemctl list-timers


List all timers

systemctl list-timers --all

Create timer

systemctl enable fstrim.timer

Auto restart crashed services

systemctl edit elasticsearch.service 

add:

[Service]
Restart=always

then

systemctl daemon-reload
systemctl restart elasticsearch.service

And to get an email when service gets restarted: https://dev.to/setevoy/linux-systemd-unit-files-edit-restart-on-failure-and-email-notifications-5h3k

FAQ

Fix journal size

journalctl --vacuum-time=10d

or

journalctl --vacuum-size=1G

Journal settings

/etc/systemd/journald.conf

SystemMaxUse=1G

and then

systemctl restart systemd-journald.service


Analyze boot processes

systemd-analyze blame

 

 

 

Systemd and DNS

resolvectl status

Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.

Means systemd-resolved is not running

Restart:

systemctl restart systemd-resolved
      
      

 

Add nameserver

Sacrifice a chicken

 

Flush caches

systemd-resolve --flush-caches

All status

systemctl status -a

syslog spam

https://psyq123.wordpress.com/2015/06/29/if-you-get-a-lot-of-logspam-from-systemd-in-your-varlogsyslog-this-might-help/

list available services

systemctl list-unit-files

or

systemctl list-units

 

normal interface names

net.ifnames=0

Show failed services

systemctl --failed

 

systemd: Started Session

Change loglevel to notice in /etc/systemd/system.conf

systemctl daemon-reexec

Status

Active: inactive (dead)

parameter ActiveState would return inactive

SubState returns dead