--- Begin Message ---
Hi

What is the reason for hardcoding the watchdog timeout into 
pve-ha-manager/watchdog-mux.c?

https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/watchdog-mux.c#l33 
<https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/watchdog-mux.c#l33>
  33 
<https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/watchdog-mux.c#l33> 
int watchdog_timeout = 10;
https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/watchdog-mux.c#l157 
<https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/watchdog-mux.c#l157>
 157 
<https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/watchdog-mux.c#l157>
     if (ioctl(watchdog_fd, WDIOC_SETTIMEOUT, &watchdog_timeout) == -1) {

I am trying to use a more conservative 5 minute timeout for the IPMI watchdog 
but it gets changed to 10 seconds when the watchdog-mux.service starts.

root@pve5:~# cat /etc/modprobe.d/ipmi_watchdog.conf 
options ipmi_watchdog timeout=300 action=power_cycle panic_wdt_timeout=10

Thanks

Stefan

References:
https://forum.proxmox.com/threads/watchdog-timeout-hardcoded-to-10s.29994/ 
<https://forum.proxmox.com/threads/watchdog-timeout-hardcoded-to-10s.29994/>
https://www.kernel.org/doc/Documentation/IPMI.txt 
<https://www.kernel.org/doc/Documentation/IPMI.txt>


--- End Message ---
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Reply via email to