kexec-tools/kdump.service

[Unit]
Description=Crash recovery kernel arming
After=network.target network-online.target remote-fs.target

[Service]
Type=oneshot
ExecStart=/usr/bin/kdumpctl start
ExecStop=/usr/bin/kdumpctl stop
RemainAfterExit=yes
StartLimitInterval=0

[Install]
WantedBy=multi-user.target
Resolves: bz 716994 -Added systemd unit file for kdump 2011-07-04 20:32:15 +00:00			`[Unit]`
			`Description=Crash recovery kernel arming`
kdump.service: Start kdump after network is online and remote fs is mounted Now kdump.service runs "After" network.target. But network.target doesn't mean network is setup and online[1]. We should use network-online.target instead for ssh/nfs dump. And also because nfs dump requires a mounted nfs when rebuilding kdump initrd, kdump.service should also run "After" remote-fs.target (this means all remote fs configured in /etc/fstab is mounted). The downside of this patch is we always need to wait for network-online.target even when dump target is a local disk. If network fails to come up, kdump.service have to be stuck until network-online.target timeout (90 seconds by default). Signed-off-by: WANG Chao <chaowang@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com> 2013-09-25 12:35:05 +00:00			`After=network.target network-online.target remote-fs.target`
Resolves: bz 716994 -Added systemd unit file for kdump 2011-07-04 20:32:15 +00:00
			`[Service]`
			`Type=oneshot`
Removing sysvinit files 2011-07-06 19:25:34 +00:00			`ExecStart=/usr/bin/kdumpctl start`
			`ExecStop=/usr/bin/kdumpctl stop`
Resolves: bz 716994 -Added systemd unit file for kdump 2011-07-04 20:32:15 +00:00			`RemainAfterExit=yes`
Disable the ratelimit of kdump service on hotplug events When doing cpu softplug via /sys ie) echo 0 > /sys/devices/system/cpu/cpuX/online echo 1 > /sys/devices/system/cpu/cpuX/online the kdump service is restarted on every cpu up and down. Eventually the service stops because it is rate limited by systemd. [root@dhg3 hoemann]# systemctl status kdump kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled) Active: failed (Result: start-limit) since Tue 2014-04-22 17:02:56 MDT; 59min ago Process: 8803 ExecStop=/usr/bin/kdumpctl stop (code=exited, status=0/SUCCESS) Process: 8911 ExecStart=/usr/bin/kdumpctl start (code=killed, signal=TERM) Main PID: 8911 (code=killed, signal=TERM) Apr 22 17:02:56 dhg3 systemd[1]: Starting Crash recovery kernel arming... Apr 22 17:02:56 dhg3 systemd[1]: Stopping Crash recovery kernel arming... Apr 22 17:02:56 dhg3 systemd[1]: Starting Crash recovery kernel arming... Apr 22 17:02:56 dhg3 systemd[1]: kdump.service start request repeated too quickly, refusing to start. Apr 22 17:02:56 dhg3 systemd[1]: Failed to start Crash recovery kernel arming. Apr 22 17:02:56 dhg3 systemd[1]: Unit kdump.service entered failed state. The ratelimiting can be disabled by adding StartLimitInterval=0 to the kdump service file. Cc: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Prarit Bhargava <prarit@redhat.com> Acked-by: Vivek Goyal <vgoyal@redhat.com> 2014-05-02 14:28:34 +00:00			`StartLimitInterval=0`
Resolves: bz 716994 -Added systemd unit file for kdump 2011-07-04 20:32:15 +00:00
Fixup sysytemd service file (bug 741272) Drop chkconfig (bug 786938) 2012-02-14 17:13:06 +00:00			`[Install]`
			`WantedBy=multi-user.target`