On Fri, May 02, 2014 at 10:28:34AM -0400, Prarit Bhargava wrote:
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(a)redhat.com>
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
Looks good to me. Thanks Prarit.
Acked-by: Vivek Goyal <vgoyal(a)redhat.com>
Vivek
---
kdump.service | 1 +
1 file changed, 1 insertion(+)
diff --git a/kdump.service b/kdump.service
index 55b7ca2..24c1386 100644
--- a/kdump.service
+++ b/kdump.service
@@ -7,6 +7,7 @@ Type=oneshot
ExecStart=/usr/bin/kdumpctl start
ExecStop=/usr/bin/kdumpctl stop
RemainAfterExit=yes
+StartLimitInterval=0
[Install]
WantedBy=multi-user.target
--
1.8.5.3