Re: [ClusterLabs] big trouble with a DRBD resource

"Lentes, Bernd" writes: > In both cases i'm inside crmsh. > The difference is that i always enter the complete command from the highest > level of crm. This has the advantage that i can execute any command from the > history directly. > And this has a kind

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 10, 2017, at 2:11 PM, Lars Ellenberg lars.ellenb...@linbit.com wrote: > > if you use crmsh "interactively", > crmsh does implicitly use a shadow cib, > and will only commit changes once you "commit", > see "crm configure help commit" > Hi, i tested it: First try: crm(live)#

Re: [ClusterLabs] big trouble with a DRBD resource

On Wed, Aug 09, 2017 at 06:48:01PM +0200, Lentes, Bernd wrote: > > > - Am 8. Aug 2017 um 15:36 schrieb Lars Ellenberg > lars.ellenb...@linbit.com: > > > crm shell in "auto-commit"? > > never seen that. > > i googled for "crmsh autocommit pacemaker" and found that: >

Re: [ClusterLabs] big trouble with a DRBD resource

- Am 8. Aug 2017 um 15:36 schrieb Lars Ellenberg lars.ellenb...@linbit.com: > crm shell in "auto-commit"? > never seen that. i googled for "crmsh autocommit pacemaker" and found that: https://github.com/ClusterLabs/crmsh/blob/master/ChangeLog See line 650. Don't know what that means. >

Re: [ClusterLabs] big trouble with a DRBD resource

On Fri, Aug 04, 2017 at 06:20:22PM +0200, Lentes, Bernd wrote: > Hi, > > first: is there a tutorial or s.th. else which helps in understanding what > pacemaker logs in syslog and /var/log/cluster/corosync.log ? > I try hard to find out what's going wrong, but they are difficult to > understand,

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 7, 2017, at 10:43 PM, kgaillot kgail...@redhat.com wrote: > > The logs are very useful, but not particularly easy to follow. It takes > some practice and experience, but I think it's worth it if you have to > troubleshoot cluster events often. I will give my best. > > It's on

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 7, 2017, at 10:26 PM, kgaillot kgail...@redhat.com wrote: > > Unmanaging doesn't stop monitoring a resource, it only prevents starting > and stopping of the resource. That lets you see the current status, even > if you're in the middle of maintenance or what not. You can disable >

Re: [ClusterLabs] big trouble with a DRBD resource

On Mon, 2017-08-07 at 12:54 +0200, Lentes, Bernd wrote: > - On Aug 4, 2017, at 10:19 PM, Ken Gaillot kgail...@redhat.com wrote: > > > Unfortunately no -- logging, and troubleshooting in general, is an area > > we are continually striving to improve, but there are more to-do's than > > time to

Re: [ClusterLabs] big trouble with a DRBD resource

On Mon, 2017-08-07 at 21:16 +0200, Lentes, Bernd wrote: > - On Aug 4, 2017, at 10:19 PM, kgaillot kgail...@redhat.com wrote: > > > The cluster reacted promptly: > > crm(live)# configure primitive prim_drbd_idcc_devel ocf:linbit:drbd params > > drbd_resource=idcc-devel \ > >> op monitor

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 4, 2017, at 10:19 PM, kgaillot kgail...@redhat.com wrote: > The cluster reacted promptly: > crm(live)# configure primitive prim_drbd_idcc_devel ocf:linbit:drbd params > drbd_resource=idcc-devel \ >> op monitor interval=60 > WARNING: prim_drbd_idcc_devel: default timeout 20s for

Re: [ClusterLabs] big trouble with a DRBD resource

On Mon, 2017-08-07 at 15:23 +0200, Lentes, Bernd wrote: > - On Aug 4, 2017, at 10:19 PM, kgaillot kgail...@redhat.com wrote: > > > > > The "ERROR" message is coming from the DRBD resource agent itself, not > > pacemaker. Between that message and the two separate monitor operations, > > it

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 4, 2017, at 10:19 PM, kgaillot kgail...@redhat.com wrote: > > The "ERROR" message is coming from the DRBD resource agent itself, not > pacemaker. Between that message and the two separate monitor operations, > it looks like the agent will only run as a master/slave clone. Btw:

Re: [ClusterLabs] big trouble with a DRBD resource

- On Aug 6, 2017, at 12:05 PM, Kristoffer Grönlund kgronl...@suse.com wrote: >> What happened: >> I tried to configure a simple drbd resource following >> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Clusters_from_Scratch/index.html#idm140457860751296 >> I used this

Re: [ClusterLabs] big trouble with a DRBD resource

here is nice guide how to configure drbd, clvm... http://marcitland.blogspot.cz/2013/04/building-using-highly-available-esos.html S pozdravem Kristián Feldsam Tel.: +420 773 303 353, +421 944 137 535 E-mail.: supp...@feldhost.cz www.feldhost.cz - FeldHost™ – profesionální hostingové a serverové

Re: [ClusterLabs] big trouble with a DRBD resource

"Lentes, Bernd" writes: > Hi, > > first: is there a tutorial or s.th. else which helps in understanding what > pacemaker logs in syslog and /var/log/cluster/corosync.log ? > I try hard to find out what's going wrong, but they are difficult to > understand,

Re: [ClusterLabs] big trouble with a DRBD resource

On Fri, 2017-08-04 at 18:20 +0200, Lentes, Bernd wrote: > Hi, > > first: is there a tutorial or s.th. else which helps in understanding what > pacemaker logs in syslog and /var/log/cluster/corosync.log ? > I try hard to find out what's going wrong, but they are difficult to > understand, also

[ClusterLabs] big trouble with a DRBD resource

Hi, first: is there a tutorial or s.th. else which helps in understanding what pacemaker logs in syslog and /var/log/cluster/corosync.log ? I try hard to find out what's going wrong, but they are difficult to understand, also because of the amount of information. Or should i deal more with "crm