Sunday, April 28, 2024
 Popular · Latest · Hot · Upcoming
1
rated 0 times [  1] [ 0]  / answers: 1 / hits: 2154  / 2 Years ago, wed, december 1, 2021, 10:58:39

I have a server which is monitored by Watchdog, and experiences reboots occasionally due to faulty network hardware I am unable to replace at the moment. As I read, Watchdog sends a SIGTERM to all processes, requesting a safe shutdown, and after a short time, sends a SIGKILL, which will stop the process immediately. However, in this case, it leads to data corruption since the main process of importance is not fully shut down yet and has unwritten data.



How long is this pause Watchdog takes between asking all processes to stop, and forcing them to stop? Is it hardwired within Watchdog, set in watchdog.conf(if it was, it never got documented in the manpage), or the same as another system setting? How may I change this setting?



Edit: I've found the timeout, but I am still looking for instructions on how to rebuild and integrate with the system properly.


More From » shutdown

 Answers
6

The official 5.15 version at Sourceforge now has this option included. It can be configured in the file watchdog.conf using the line:



sigterm-delay = 5



(commented out in the example file). Please note the experimental 'V6' version should not be used any more as 5.15 has practically all of its features and several bug-fixes as well. Also note that the 'sat' web site might be shut down later in 2019 due to the withdrawal of NERC funding.


[#32016] Wednesday, December 1, 2021, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
uquelighted

Total Points: 242
Total Questions: 110
Total Answers: 106

Location: Cyprus
Member since Tue, Sep 22, 2020
4 Years ago
;