>>> Lars Marowsky-Bree <[email protected]> schrieb am 20.02.2013 um 16:37 in 
>>> Nachricht
<[email protected]>:
> On 2013-02-20T11:03:20, Ulrich Windl <[email protected]> 
> wrote:
> 
> > Let me remark that I'm seeing the opposite for sbd-based fencing 
> occasionally: The action is set to reboot, but occasionally some servers are 
> powered down. The less-pleasing feature of that is that you can't power up a 
> server using sbd, but you'll have to walk to find out what's wrong...
> 
> The only way ever that SBD executes "poweroff" is when the fencing code
> sends a poweroff message - that's the only code path leading to this.
> 
> All SBD's suicide actions are reboot-based.
> 
> If it powers off, that's either a stonith-ng issue or a hardware
> problem or something different; but I'm guaranteeing it's not SBD acting
> on its own.
> 
> Or can the watchdog you use power off the system? Normally, watchdogs
> tend to reboot the system though ...

I'm not sure which watchdog is being used; the machines are Sun X4100 which 
have iLO. When starting , sbd says "sbd: [12123]: info: Watchdog enabled." ;-)
I cannot see any "dog" or "watch" modules loaded either.

It's hard to find out which module is actually used from the syslog; see 
yourself:
Feb 18 11:13:14 so2 kernel: [   75.556326] usbcore: registered new interface 
driver pcwd_usb
Feb 18 11:13:14 so2 kernel: [   75.556330] pcwd_usb: Berkshire USB-PC Watchdog 
driver v1.02
Feb 18 11:13:14 so2 kernel: [   75.562906] WDT driver for Acquire single board 
computer initialising.
Feb 18 11:13:14 so2 kernel: [   75.562967] acquirewdt: I/O address 0x0043 
already in use
Feb 18 11:13:14 so2 kernel: [   75.562971] acquirewdt: probe of acquirewdt 
failed with error -5
Feb 18 11:13:14 so2 kernel: [   75.564759] WDT driver for Advantech single 
board computer initialising.
Feb 18 11:13:14 so2 kernel: [   75.564938] advantechwdt: initialized. 
timeout=60 sec (nowayout=0)
Feb 18 11:13:15 so2 kernel: [   75.659762] alim7101_wdt: Steve Hill 
<[email protected]>.
Feb 18 11:13:15 so2 kernel: [   75.659773] alim7101_wdt: ALi M7101 PMU not 
present - WDT not set
Feb 18 11:13:15 so2 kernel: [   75.666679] sc520_wdt: cannot register miscdev 
on minor=130 (err=-16)
Feb 18 11:13:15 so2 kernel: [   75.708581] eurwdt: can't misc_register on 
minor=130
Feb 18 11:13:15 so2 kernel: [   75.794566] ib700wdt: WDT driver for IB700 
single board computer initialising.
Feb 18 11:13:15 so2 kernel: [   75.794666] ib700wdt: START method I/O 443 is 
not available.
Feb 18 11:13:15 so2 kernel: [   75.794672] ib700wdt: probe of ib700wdt failed 
with error -5
Feb 18 11:13:15 so2 kernel: [   75.872173] WDT driver for Wafer 5823 single 
board computer initialising.
Feb 18 11:13:15 so2 kernel: [   75.872180] Wafer 5823 WDT: I/O address 0x0443 
already in use
Feb 18 11:13:15 so2 kernel: [   75.877719] iTCO_vendor_support: vendor-support=0
Feb 18 11:13:15 so2 kernel: [   75.878766] iTCO_wdt: Intel TCO WatchDog Timer 
Driver v1.06
Feb 18 11:13:15 so2 kernel: [   75.878863] iTCO_wdt: No device detected.
Feb 18 11:13:15 so2 kernel: [   75.929847] sc1200wdt: build 20020303
Feb 18 11:13:15 so2 kernel: [   75.929867] sc1200wdt: io parameter must be 
specified
Feb 18 11:13:15 so2 kernel: [   76.002420] pc87413 WDT: Version 1.1 at io 0x2E
Feb 18 11:13:15 so2 kernel: [   76.002426] pc87413 WDT: cannot register miscdev 
on minor=130 (err=-16)
Feb 18 11:13:15 so2 kernel: [   76.073284] sbc60xxwdt: I/O address 0x0443 
already in use
Feb 18 11:13:15 so2 kernel: [   76.127499] cpu5wdt: misc_register failed
Feb 18 11:13:15 so2 kernel: [   76.206113] SMsC 37B787 watchdog component 
driver 1.1 initialising...
Feb 18 11:13:15 so2 kernel: [   76.207177] smsc37b787_wdt: Unable to register 
miscdev on minor 130
Feb 18 11:13:15 so2 kernel: [   76.252583] WDT driver for the Winbond(TM) 
W83627HF/THF/HG/DHG Super I/O chip initialising.
Feb 18 11:13:15 so2 kernel: [   76.252679] w83627hf/thf/hg/dhg WDT: cannot 
register miscdev on minor=130 (err=-16)
Feb 18 11:13:15 so2 kernel: [   76.315005] w83697hf/hg WDT: WDT driver for 
W83697HF/HG initializing
Feb 18 11:13:15 so2 kernel: [   76.315011] w83697hf/hg WDT: Looking for 
watchdog at address 0x2e
Feb 18 11:13:15 so2 kernel: [   76.315043] w83697hf/hg WDT: watchdog not found 
at address 0x2e
Feb 18 11:13:15 so2 kernel: [   76.315045] w83697hf/hg WDT: No W83697HF/HG 
could be found
Feb 18 11:13:15 so2 kernel: [   76.380941] w83877f_wdt: I/O address 0x0443 
already in use
Feb 18 11:13:15 so2 kernel: [   76.431168] machzwd: MachZ ZF-Logic Watchdog 
driver initializing.
Feb 18 11:13:15 so2 kernel: [   76.431179] machzwd: no ZF-Logic found
Feb 18 11:13:15 so2 kernel: [   76.448188] Xen WatchDog Timer Driver v0.01
Feb 18 11:13:15 so2 kernel: [   76.448270] xen_wdt: cannot register miscdev on 
minor=130 (-16)
Feb 18 11:13:15 so2 kernel: [   76.448276] wdt: probe of wdt failed with error 
-16
Feb 18 11:13:15 so2 kernel: [   76.464220] SoftDog: cannot register miscdev on 
minor=130 (err=-16)
Feb 18 11:13:15 so2 sbd: [12125]: notice: Using watchdog device: /dev/watchdog
Feb 18 11:13:15 so2 sbd: [12125]: info: Set watchdog timeout to 30 seconds.


> 
> 
> Regards,
>     Lars



 

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to