date:20170103

Re: [ClusterLabs] sbd: Cannot open watchdog device: /dev/watchdog

2017-01-03 Thread Klaus Wenninger

On 01/03/2017 09:02 PM, Muhammad Sharfuddin wrote:
> On 01/03/2017 09:49 PM, Kristoffer Grönlund wrote:
>> Muhammad Sharfuddin  writes:
>>
>>> Hello,
>>>
>>> pacemaker does not start on this machine(Fujitsu PRIMERGY RX2540 M1) 
>>> with following error in  the logs:
>>>
>>> sbd: [13236]: ERROR: Cannot open watchdog device: /dev/watchdog: No such 
>>> file or directory
>> Does /dev/watchdog exist? 
> No
> ls -l /dev/watch*
> ls: cannot access /dev/watch*: No such file or directory
Then you probably don't have one at all.
Maybe no hardware,the driver is not loaded or e.g.
udev doesn't create the node for some reason.
For a test at least you can try loading loading softdog.

[kwenning@kwenning pacemaker]$ sudo modprobe softdog
[sudo] password for kwenning:
[kwenning@kwenning pacemaker]$ ls -l /dev/watchdog
crw---. 1 root root 10, 130 Jan  3 13:39 /dev/watchdog

>> If you have more than one watchdog device, you can configure
>> sbd to use a different device using the -w option.
>>
>> Cheers,
>> Kristoffer
>>
>>> System Info:
>>>
>>> sbd-1.2.1-8.7.x86_64  corosync-2.3.3-7.12.x86_64 pacemaker-1.1.12-7.1.x86_64
>>>
>>> lsmod | egrep "(wd|dog)"
>>> iTCO_wdt   13480  0
>>> iTCO_vendor_support13718  1 iTCO_wdt
>>>
>>> dmidecode | grep -A3 '^System Information'
>>> System Information
>>>  Manufacturer: FUJITSU
>>>  Product Name: PRIMERGY RX2540 M1
>>>  Version: GS01
>>>
>>> logs:
>>>
>>> 2017-01-03T21:00:26.890503+05:00 prdnode1 sbd: [13235]: info: Watchdog 
>>> enabled.
>>> 2017-01-03T21:00:26.899817+05:00 prdnode1 sbd: [13238]: info: Servant 
>>> starting for device 
>>> /dev/disk/by-id/wwn-0x60e00d28002825b5-part1
>>> 2017-01-03T21:00:26.900175+05:00 prdnode1 sbd: [13238]: info: Device 
>>> /dev/disk/by-id/wwn-0x60e00d28002825b5-part1 uuid: 
>>> fda42d64-ca74-4578-90c8-976ea7ff5f6e
>>> 2017-01-03T21:00:26.900418+05:00 prdnode1 sbd: [13239]: info: Monitoring 
>>> Pacemaker health
>>> 2017-01-03T21:00:27.901022+05:00 prdnode1 sbd: [13236]: ERROR: Cannot 
>>> open watchdog device: /dev/watchdog: No such file or directory
>>> 2017-01-03T21:00:27.912098+05:00 prdnode1 sbd: [13236]: WARN: Servant 
>>> for pcmk (pid: 13239) has terminated
>>> 2017-01-03T21:00:27.941950+05:00 prdnode1 sbd: [13236]: WARN: Servant 
>>> for /dev/disk/by-id/wwn-0x60e00d28002825b5-part1 (pid: 
>>> 13238) has terminated
>>> 2017-01-03T21:00:27.949401+05:00 prdnode1 sbd.sh[13231]: sbd failed; 
>>> please check the logs.
>>> 2017-01-03T21:00:27.992606+05:00 prdnode1 sbd.sh[13231]: SBD failed to 
>>> start; aborting.
>>> 2017-01-03T21:00:27.993061+05:00 prdnode1 systemd[1]: sbd.service: 
>>> control process exited, code=exited status=1
>>> 2017-01-03T21:00:27.993339+05:00 prdnode1 systemd[1]: Failed to start 
>>> Shared-storage based fencing daemon.
>>> 2017-01-03T21:00:27.993610+05:00 prdnode1 systemd[1]: Dependency failed 
>>> for Pacemaker High Availability Cluster Manager.
>>> 2017-01-03T21:00:27.994054+05:00 prdnode1 systemd[1]: Unit sbd.service 
>>> entered failed state.
>>>
>>> please help.
>>>
>>> -- 
>>> Regards,
>>>
>>> Muhammad Sharfuddin
>>> 
>>>
>>> ___
>>> Users mailing list: Users@clusterlabs.org
>>> http://lists.clusterlabs.org/mailman/listinfo/users
>>>
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
> Regards,
>
> Muhammad Sharfuddin
>
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org



___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] sbd: Cannot open watchdog device: /dev/watchdog

2017-01-03 Thread Kristoffer Grönlund

Muhammad Sharfuddin  writes:

> Hello,
>
> pacemaker does not start on this machine(Fujitsu PRIMERGY RX2540 M1) 
> with following error in  the logs:
>
> sbd: [13236]: ERROR: Cannot open watchdog device: /dev/watchdog: No such 
> file or directory

Does /dev/watchdog exist? If so, it may be opened by a different
process. If you have more than one watchdog device, you can configure
sbd to use a different device using the -w option.

Cheers,
Kristoffer

>
> System Info:
>
> sbd-1.2.1-8.7.x86_64  corosync-2.3.3-7.12.x86_64 pacemaker-1.1.12-7.1.x86_64
>
> lsmod | egrep "(wd|dog)"
> iTCO_wdt   13480  0
> iTCO_vendor_support13718  1 iTCO_wdt
>
> dmidecode | grep -A3 '^System Information'
> System Information
>  Manufacturer: FUJITSU
>  Product Name: PRIMERGY RX2540 M1
>  Version: GS01
>
> logs:
>
> 2017-01-03T21:00:26.890503+05:00 prdnode1 sbd: [13235]: info: Watchdog 
> enabled.
> 2017-01-03T21:00:26.899817+05:00 prdnode1 sbd: [13238]: info: Servant 
> starting for device 
> /dev/disk/by-id/wwn-0x60e00d28002825b5-part1
> 2017-01-03T21:00:26.900175+05:00 prdnode1 sbd: [13238]: info: Device 
> /dev/disk/by-id/wwn-0x60e00d28002825b5-part1 uuid: 
> fda42d64-ca74-4578-90c8-976ea7ff5f6e
> 2017-01-03T21:00:26.900418+05:00 prdnode1 sbd: [13239]: info: Monitoring 
> Pacemaker health
> 2017-01-03T21:00:27.901022+05:00 prdnode1 sbd: [13236]: ERROR: Cannot 
> open watchdog device: /dev/watchdog: No such file or directory
> 2017-01-03T21:00:27.912098+05:00 prdnode1 sbd: [13236]: WARN: Servant 
> for pcmk (pid: 13239) has terminated
> 2017-01-03T21:00:27.941950+05:00 prdnode1 sbd: [13236]: WARN: Servant 
> for /dev/disk/by-id/wwn-0x60e00d28002825b5-part1 (pid: 
> 13238) has terminated
> 2017-01-03T21:00:27.949401+05:00 prdnode1 sbd.sh[13231]: sbd failed; 
> please check the logs.
> 2017-01-03T21:00:27.992606+05:00 prdnode1 sbd.sh[13231]: SBD failed to 
> start; aborting.
> 2017-01-03T21:00:27.993061+05:00 prdnode1 systemd[1]: sbd.service: 
> control process exited, code=exited status=1
> 2017-01-03T21:00:27.993339+05:00 prdnode1 systemd[1]: Failed to start 
> Shared-storage based fencing daemon.
> 2017-01-03T21:00:27.993610+05:00 prdnode1 systemd[1]: Dependency failed 
> for Pacemaker High Availability Cluster Manager.
> 2017-01-03T21:00:27.994054+05:00 prdnode1 systemd[1]: Unit sbd.service 
> entered failed state.
>
> please help.
>
> -- 
> Regards,
>
> Muhammad Sharfuddin
> 
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-- 
// Kristoffer Grönlund
// kgronl...@suse.com

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] sbd: Cannot open watchdog device: /dev/watchdog

2017-01-03 Thread Muhammad Sharfuddin


Hello,

pacemaker does not start on this machine(Fujitsu PRIMERGY RX2540 M1) 
with following error in  the logs:


sbd: [13236]: ERROR: Cannot open watchdog device: /dev/watchdog: No such 
file or directory


System Info:

sbd-1.2.1-8.7.x86_64  corosync-2.3.3-7.12.x86_64 pacemaker-1.1.12-7.1.x86_64

lsmod | egrep "(wd|dog)"
iTCO_wdt   13480  0
iTCO_vendor_support13718  1 iTCO_wdt

dmidecode | grep -A3 '^System Information'
System Information
Manufacturer: FUJITSU
Product Name: PRIMERGY RX2540 M1
Version: GS01

logs:

2017-01-03T21:00:26.890503+05:00 prdnode1 sbd: [13235]: info: Watchdog 
enabled.
2017-01-03T21:00:26.899817+05:00 prdnode1 sbd: [13238]: info: Servant 
starting for device 
/dev/disk/by-id/wwn-0x60e00d28002825b5-part1
2017-01-03T21:00:26.900175+05:00 prdnode1 sbd: [13238]: info: Device 
/dev/disk/by-id/wwn-0x60e00d28002825b5-part1 uuid: 
fda42d64-ca74-4578-90c8-976ea7ff5f6e
2017-01-03T21:00:26.900418+05:00 prdnode1 sbd: [13239]: info: Monitoring 
Pacemaker health
2017-01-03T21:00:27.901022+05:00 prdnode1 sbd: [13236]: ERROR: Cannot 
open watchdog device: /dev/watchdog: No such file or directory
2017-01-03T21:00:27.912098+05:00 prdnode1 sbd: [13236]: WARN: Servant 
for pcmk (pid: 13239) has terminated
2017-01-03T21:00:27.941950+05:00 prdnode1 sbd: [13236]: WARN: Servant 
for /dev/disk/by-id/wwn-0x60e00d28002825b5-part1 (pid: 
13238) has terminated
2017-01-03T21:00:27.949401+05:00 prdnode1 sbd.sh[13231]: sbd failed; 
please check the logs.
2017-01-03T21:00:27.992606+05:00 prdnode1 sbd.sh[13231]: SBD failed to 
start; aborting.
2017-01-03T21:00:27.993061+05:00 prdnode1 systemd[1]: sbd.service: 
control process exited, code=exited status=1
2017-01-03T21:00:27.993339+05:00 prdnode1 systemd[1]: Failed to start 
Shared-storage based fencing daemon.
2017-01-03T21:00:27.993610+05:00 prdnode1 systemd[1]: Dependency failed 
for Pacemaker High Availability Cluster Manager.
2017-01-03T21:00:27.994054+05:00 prdnode1 systemd[1]: Unit sbd.service 
entered failed state.


please help.

--
Regards,

Muhammad Sharfuddin


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Antw: Re: [ClusterLabs Developers] announcement: schedule for resource-agents release 3.9.8

2017-01-03 Thread Kristoffer Grönlund

Ulrich Windl  writes:

 Kristoffer Grönlund  schrieb am 03.01.2017 um 11:55 in
> Nachricht <878tqsjtv4@suse.com>:
>> Oyvind Albrigtsen  writes:
>> 
>>> Hi,
>>>
>>> This is a tentative schedule for resource-agents v3.9.8:
>>> 3.9.8-rc1: January 10.
>>> 3.9.8: January 31.
>>>
>>> I modified the corresponding milestones at
>>> https://github.com/ClusterLabs/resource-agents/milestones 
>>>
>>> If there's anything you think should be part of the release
>>> please open an issue, a pull request, or a bugzilla, as you see
>>> fit.
>>>
>> 
>> Hi Oyvind,
>> 
>> I think it's high time for a new release! My only suggestion would be to
>> call it 4.0.0, since there are much bigger changes from 3.9.7 than an
>> update to the patch release number would suggest.
>
> I don't know the semantics of everybody's release numbering, but for a
> three-level number a "compatibility"."feature"."bug-fix" pattern wouldn't be
> bad; that is only change the first number if there are incompatible changes
> (things may not work after ugrading from the previous level). Change the 
> second
> number whenever there are new features (the users may want to read about), and
> change only the last number if just bugs were fixed (without affecting the
> interfaces).
> And: There's nothing wrong with "10" following "9" ;-)
>
> And if you are just happy to throw out new versions (whatever they bring),
> call it "2017-01" ;-)

There was a recent talk by Rich Hickey on this topic, his way of putting
it was that versions basically boil down to X.Y where Y means "don't
care, just upgrade" and X means "anything can have changed, be very
careful" :)

For resource-agents and the releases historically, I personally think
having a single number that just increments each release makes as much
sense as anything else, at least in my experience there is just a single
development track where bug fixes, new features and backwards
incompatible changes mix freely, even if we do try to keep the
incompatible changes as rare as possible.

But, keeping the x.y.z triplet is easier to maintain in relation to the
older releases. 

Cheers,
Kristoffer

>
> Regards,
> Ulrich
>
>> 
>> Cheers,
>> Kristoffer
>> 
>>> If there's anything that hasn't received due attention, please
>>> let us know.
>>>
>>> Finally, if you can help with resolving issues consider yourself
>>> invited to do so. There are currently 49 issues and 38 pull
>>> requests still open.
>>>
>>>
>>> Cheers,
>>> Oyvind Albrigtsen
>>>
>>> ___
>>> Developers mailing list
>>> develop...@clusterlabs.org 
>>> http://lists.clusterlabs.org/mailman/listinfo/developers 
>>>
>> 
>> -- 
>> // Kristoffer Grönlund
>> // kgronl...@suse.com 
>> 
>> ___
>> Users mailing list: Users@clusterlabs.org 
>> http://lists.clusterlabs.org/mailman/listinfo/users 
>> 
>> Project Home: http://www.clusterlabs.org 
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
>> Bugs: http://bugs.clusterlabs.org 
>
>
>
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-- 
// Kristoffer Grönlund
// kgronl...@suse.com

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] Antw: Re: [ClusterLabs Developers] announcement: schedule for resource-agents release 3.9.8

2017-01-03 Thread Ulrich Windl

>>> Kristoffer Grönlund  schrieb am 03.01.2017 um 11:55 in
Nachricht <878tqsjtv4@suse.com>:
> Oyvind Albrigtsen  writes:
> 
>> Hi,
>>
>> This is a tentative schedule for resource-agents v3.9.8:
>> 3.9.8-rc1: January 10.
>> 3.9.8: January 31.
>>
>> I modified the corresponding milestones at
>> https://github.com/ClusterLabs/resource-agents/milestones 
>>
>> If there's anything you think should be part of the release
>> please open an issue, a pull request, or a bugzilla, as you see
>> fit.
>>
> 
> Hi Oyvind,
> 
> I think it's high time for a new release! My only suggestion would be to
> call it 4.0.0, since there are much bigger changes from 3.9.7 than an
> update to the patch release number would suggest.

I don't know the semantics of everybody's release numbering, but for a
three-level number a "compatibility"."feature"."bug-fix" pattern wouldn't be
bad; that is only change the first number if there are incompatible changes
(things may not work after ugrading from the previous level). Change the second
number whenever there are new features (the users may want to read about), and
change only the last number if just bugs were fixed (without affecting the
interfaces).
And: There's nothing wrong with "10" following "9" ;-)

And if you are just happy to throw out new versions (whatever they bring),
call it "2017-01" ;-)

Regards,
Ulrich

> 
> Cheers,
> Kristoffer
> 
>> If there's anything that hasn't received due attention, please
>> let us know.
>>
>> Finally, if you can help with resolving issues consider yourself
>> invited to do so. There are currently 49 issues and 38 pull
>> requests still open.
>>
>>
>> Cheers,
>> Oyvind Albrigtsen
>>
>> ___
>> Developers mailing list
>> develop...@clusterlabs.org 
>> http://lists.clusterlabs.org/mailman/listinfo/developers 
>>
> 
> -- 
> // Kristoffer Grönlund
> // kgronl...@suse.com 
> 
> ___
> Users mailing list: Users@clusterlabs.org 
> http://lists.clusterlabs.org/mailman/listinfo/users 
> 
> Project Home: http://www.clusterlabs.org 
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf 
> Bugs: http://bugs.clusterlabs.org 




___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] [ClusterLabs Developers] announcement: schedule for

2017-01-03 Thread Oyvind Albrigtsen


resource-agents release 4.0.0 (was 3.9.8)
Reply-To: 
In-Reply-To: <878tqsjtv4@suse.com>

User-Agent: Mutt

Hi Kristoffer,

That makes sense. I have now updated Milestones to call it 4.0.0.


Oyvind Albrigtsen


On 03/01/17 11:55 +0100, Kristoffer Grönlund wrote:

Oyvind Albrigtsen  writes:


Hi,

This is a tentative schedule for resource-agents v3.9.8:
3.9.8-rc1: January 10.
3.9.8: January 31.

I modified the corresponding milestones at
https://github.com/ClusterLabs/resource-agents/milestones

If there's anything you think should be part of the release
please open an issue, a pull request, or a bugzilla, as you see
fit.



Hi Oyvind,

I think it's high time for a new release! My only suggestion would be to
call it 4.0.0, since there are much bigger changes from 3.9.7 than an
update to the patch release number would suggest.

Cheers,
Kristoffer


If there's anything that hasn't received due attention, please
let us know.

Finally, if you can help with resolving issues consider yourself
invited to do so. There are currently 49 issues and 38 pull
requests still open.


Cheers,
Oyvind Albrigtsen

___
Developers mailing list
develop...@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/developers



--
// Kristoffer Grönlund
// kgronl...@suse.com


___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] [ClusterLabs Developers] announcement: schedule for resource-agents release 3.9.8

2017-01-03 Thread Kristoffer Grönlund

Oyvind Albrigtsen  writes:

> Hi,
>
> This is a tentative schedule for resource-agents v3.9.8:
> 3.9.8-rc1: January 10.
> 3.9.8: January 31.
>
> I modified the corresponding milestones at
> https://github.com/ClusterLabs/resource-agents/milestones
>
> If there's anything you think should be part of the release
> please open an issue, a pull request, or a bugzilla, as you see
> fit.
>

Hi Oyvind,

I think it's high time for a new release! My only suggestion would be to
call it 4.0.0, since there are much bigger changes from 3.9.7 than an
update to the patch release number would suggest.

Cheers,
Kristoffer

> If there's anything that hasn't received due attention, please
> let us know.
>
> Finally, if you can help with resolving issues consider yourself
> invited to do so. There are currently 49 issues and 38 pull
> requests still open.
>
>
> Cheers,
> Oyvind Albrigtsen
>
> ___
> Developers mailing list
> develop...@clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/developers
>

-- 
// Kristoffer Grönlund
// kgronl...@suse.com

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] announcement: schedule for resource-agents release 3.9.8

2017-01-03 Thread Oyvind Albrigtsen


Hi,

This is a tentative schedule for resource-agents v3.9.8:
3.9.8-rc1: January 10.
3.9.8: January 31.

I modified the corresponding milestones at
https://github.com/ClusterLabs/resource-agents/milestones

If there's anything you think should be part of the release
please open an issue, a pull request, or a bugzilla, as you see
fit.

If there's anything that hasn't received due attention, please
let us know.

Finally, if you can help with resolving issues consider yourself
invited to do so. There are currently 49 issues and 38 pull
requests still open.


Cheers,
Oyvind Albrigtsen

___
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] sbd: Cannot open watchdog device: /dev/watchdog

Re: [ClusterLabs] sbd: Cannot open watchdog device: /dev/watchdog

[ClusterLabs] sbd: Cannot open watchdog device: /dev/watchdog

Re: [ClusterLabs] Antw: Re: [ClusterLabs Developers] announcement: schedule for resource-agents release 3.9.8

[ClusterLabs] Antw: Re: [ClusterLabs Developers] announcement: schedule for resource-agents release 3.9.8

Re: [ClusterLabs] [ClusterLabs Developers] announcement: schedule for

Re: [ClusterLabs] [ClusterLabs Developers] announcement: schedule for resource-agents release 3.9.8

[ClusterLabs] announcement: schedule for resource-agents release 3.9.8

8 matches

Site Navigation

Mail list logo

Footer information