[ClusterLabs] DRBD Split brain

2017-12-12 Thread Антон Сацкий
Hi list
Need your help.
Got 2  servers use Pacemaker  Corosync Drbd

[root@voipserver ~]# pcs config
Cluster Name: ClusterKrusher
Corosync Nodes:
 voipserver.primary voipserver.backup
Pacemaker Nodes:
 voipserver.backup voipserver.primary

Resources:
 Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=32 ip=172.20.11.10
  Operations: monitor interval=30s (ClusterIP-monitor-interval-30s)
  start interval=0s timeout=20s (ClusterIP-start-interval-0s)
  stop interval=0s timeout=20s (ClusterIP-stop-interval-0s)
 Master: WebDataClone
  Meta Attrs: master-node-max=1 clone-max=2 notify=true master-max=1
clone-node-max=1
  Resource: WebData (class=ocf provider=linbit type=drbd)
   Attributes: drbd_resource=r0
   Operations: demote interval=0s timeout=90 (WebData-demote-interval-0s)
   monitor interval=60s (WebData-monitor-interval-60s)
   promote interval=0s timeout=90 (WebData-promote-interval-0s)
   start interval=0s timeout=240 (WebData-start-interval-0s)
   stop interval=0s timeout=100 (WebData-stop-interval-0s)
 Resource: WebFS (class=ocf provider=heartbeat type=Filesystem)
  Attributes: device=/dev/drbd1 directory=/replica fstype=ext3
  Operations: monitor interval=20 timeout=40 (WebFS-monitor-interval-20)
  start interval=0s timeout=60 (WebFS-start-interval-0s)
  stop interval=0s timeout=60 (WebFS-stop-interval-0s)
 Resource: Asterisk (class=lsb type=asterisk)
  Operations: monitor interval=15 timeout=15 (Asterisk-monitor-interval-15)
  start interval=0s timeout=15 (Asterisk-start-interval-0s)
  stop interval=0s timeout=15 (Asterisk-stop-interval-0s)
 Resource: MYSQL (class=lsb type=mysql)
  Operations: monitor interval=15 timeout=15 (MYSQL-monitor-interval-15)
  start interval=0s timeout=15 (MYSQL-start-interval-0s)
  stop interval=0s timeout=15 (MYSQL-stop-interval-0s)

Stonith Devices:
Fencing Levels:

Location Constraints:
Ordering Constraints:
  promote WebDataClone then start WebFS (kind:Mandatory)
  start WebFS then start MYSQL (kind:Mandatory)
  start ClusterIP then start Asterisk (kind:Mandatory)
Colocation Constraints:
  WebFS with WebDataClone (score:INFINITY) (with-rsc-role:Master)
  MYSQL with WebFS (score:INFINITY)
  Asterisk with ClusterIP (score:INFINITY)
Ticket Constraints:

Alerts:
 No alerts defined

Resources Defaults:
 resource-stickiness: 100
Operations Defaults:
 No defaults set

Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: ClusterKrusher
 dc-version: 1.1.16-12.el7_4.2-94ff4df
 have-watchdog: false
 stonith-enabled: false

Quorum:
  Options:
===


After some tibe got in logs
[root@voipserver ~]#  cat  /var/log/messages |grep drbd
Dec 12 14:08:52 voipserver kernel: block drbd1: role( Secondary -> Primary )
Dec 12 14:08:52 voipserver Filesystem(WebFS)[64935]: INFO: Running start
for /dev/drbd1 on /replica
Dec 12 14:08:52 voipserver kernel: EXT4-fs (drbd1): mounting ext3 file
system using the ext4 subsystem
Dec 12 14:08:53 voipserver kernel: EXT4-fs (drbd1): mounted filesystem with
ordered data mode. Opts: (null)
Dec 12 14:18:13 voipserver Filesystem(WebFS)[3134]: INFO: Running stop for
/dev/drbd1 on /replica
Dec 12 14:18:17 voipserver Filesystem(WebFS)[3319]: INFO: Running start for
/dev/drbd1 on /replica
Dec 12 14:18:17 voipserver kernel: EXT4-fs (drbd1): mounting ext3 file
system using the ext4 subsystem
Dec 12 14:18:17 voipserver kernel: EXT4-fs (drbd1): mounted filesystem with
ordered data mode. Opts: (null)
Dec 12 14:44:07 voipserver Filesystem(WebFS)[11669]: INFO: Running stop for
/dev/drbd1 on /replica
Dec 12 14:44:07 voipserver kernel: block drbd1: role( Primary -> Secondary )
Dec 12 14:44:07 voipserver kernel: block drbd1: 3552 KB (888 bits) marked
out-of-sync by on disk bit-map.
Dec 12 14:44:08 voipserver kernel: block drbd1: disk( UpToDate -> Failed )
Dec 12 14:44:08 voipserver kernel: block drbd1: 3552 KB (888 bits) marked
out-of-sync by on disk bit-map.
Dec 12 14:44:08 voipserver kernel: block drbd1: disk( Failed -> Diskless )
Dec 12 14:44:08 voipserver kernel: drbd r0: Terminating drbd_w_r0
Dec 12 14:44:19 voipserver kernel: drbd: loading out-of-tree module taints
kernel.
Dec 12 14:44:19 voipserver kernel: drbd: module verification failed:
signature and/or required key missing - tainting kernel
Dec 12 14:44:19 voipserver systemd-modules-load: Inserted module 'drbd'
Dec 12 14:44:19 voipserver kernel: drbd: initialized. Version: 8.4.10-1
(api:1/proto:86-101)
Dec 12 14:44:19 voipserver kernel: drbd: GIT-hash:
a4d5de01fffd7e4cde48a080e2c686f9e8cebf4c build by mockbuild@, 2017-09-15
14:23:22
Dec 12 14:44:19 voipserver kernel: drbd: registered as block device major
147
Dec 12 14:45:02 voipserver Filesystem(WebFS)[1400]: WARNING: Couldn't find
device [/dev/drbd1]. Expected /dev/??? to exist
Dec 12 14:45:03 voipserver kernel: drbd r0: Starting worker thread 

Re: [ClusterLabs] MYSQL data on DRBD

2017-10-25 Thread Антон Сацкий
Digimer  yes U r right i need   to run Mysql on one server
but somehow  when i run
pcs resource create MYSQL lsb:mysql
pacameker  also trying to start mysql on a backup server

Oct 25 12:43:42 voipserver.primary pengine[21418]:  warning: Processing
failed op start for MYSQL on voipserver.backup: unknown error (1)
Oct 25 12:43:42 voipserver.primary pengine[21418]:  warning: Processing
failed op start for MYSQL on voipserver.backup: unknown error (1)
Oct 25 12:43:43 voipserver.primary pengine[21418]:  warning: Processing
failed op start for MYSQL on voipserver.backup: unknown error (1)
Oct 25 12:43:43 voipserver.primary pengine[21418]:  warning: Processing
failed op start for MYSQL on voipserver.backup: unknown error (1)

On Tue, Oct 24, 2017 at 10:55 PM, Digimer <li...@alteeve.ca> wrote:

> On 2017-10-24 10:31 AM, Ken Gaillot wrote:
> > On Tue, 2017-10-24 at 13:48 +0300, Антон Сацкий wrote:
> >> HI list
> >> need  inf how to setup cluster MYSQL
> >> if DB files and  libs are on DRBD
> >
> > Hi Antony,
> >
> > There was a recent discussion of such a setup on this list. The general
> > conclusion was that it poses problems, especially during mysql
> > upgrades. A better possibility might be to use mysql native replication
> > between the two servers. If desired, a pair of servers on a DRBD
> > cluster could be used for each endpoint instead of a single server.
> >
> >>
> >> PS only one instance of mysql  is running
>
> Running MySQL on one node at a time with DRBD replicating should be just
> fine. The trick comes when you want to run it in two+ places at the same
> time.
>
> Anthony,
>
> You setup a colocated service with DRBD -> FS -> MySQL -> virtual IP and
> run DRBD in single primary. With proper fencing (which you need anyway),
> you'll be just fine.
>
> --
> Digimer
> Papers and Projects: https://alteeve.com/w/
> "I am, somehow, less interested in the weight and convolutions of
> Einstein’s brain than in the near certainty that people of equal talent
> have lived and died in cotton fields and sweatshops." - Stephen Jay Gould
>
> ___
> 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
>



-- 
Best regards
Antony
tel.   +380669197533
tel2. +380636564340
Paypal http://paypal.me/Satskiy
<http://paypal.me/Satskiy?ppid=PPC000654=PL=en_PL(en_DK)=NN8XJS9XEP22C=21db79ac-ef8d-11e5-9553-9c8e992ea258==4d776c21ca7d2=4d776c21ca7d2=4d776c21ca7d2_tpcid=ppme-social-business-profile-created=main:email=main:email=op=em=ci=sys>
satski...@gmail.com <mail%3asatski...@gmail.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] MYSQL data on DRBD

2017-10-24 Thread Антон Сацкий
HI list
need  inf how to setup cluster MYSQL
if DB files and  libs are on DRBD
PS only one instance of mysql  is running


-- 
Best regards
Antony
tel.   +380669197533
tel2. +380636564340
Paypal http://paypal.me/Satskiy

satski...@gmail.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] Stopped DRBD

2017-10-17 Thread Антон Сацкий
Hi list need your help


[root@voipserver ~]# pcs status
Cluster name: ClusterKrusher
Stack: corosync
Current DC: voipserver.backup (version 1.1.16-12.el7_4.2-94ff4df) -
partition with quorum
Last updated: Tue Oct 17 19:46:05 2017
Last change: Tue Oct 17 19:28:22 2017 by root via cibadmin on
voipserver.primary

2 nodes configured
3 resources configured

Node voipserver.backup: standby
Online: [ voipserver.primary ]

Full list of resources:

 ClusterIP  (ocf::heartbeat:IPaddr2):   Started voipserver.primary
 Master/Slave Set: DrbdDataClone [DrbdData]
 Masters: [ voipserver.primary ]
 Stopped: [ voipserver.backup ]

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled



BUT IN FACT
[root@voipserver ~]# drbd-overview
NOTE: drbd-overview will be deprecated soon.
Please consider using drbdtop.

 1:r0/0  Connected Primary/Secondary UpToDate/UpToDate


Is it normal behavior or a BUG

-- 
Best regards
Antony
tel.   +380669197533
tel2. +380636564340
Paypal http://paypal.me/Satskiy

satski...@gmail.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] hi list

2016-09-30 Thread Антон Сацкий
Greeting for everyone
Got a question is it normal?

below i can see

Running /etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 start
IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO: Adding inet
address 10.0.10.113/24 with broadcast address 10.0.10.255 to device eth1
IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO: Bringing
device eth1 up

but when i run ifconfig
i cant see 10.0.10.113 as eth1:0


BUT IT EXIST
i can ping 10.0.10.113  from pouter  and it is this  server

PS
heartbeat.x86_64
3.0.4-2.el6
@epe

Centos  6.8



Sep 30 15:02:24 voipserver.drbd heartbeat: [1568]: WARN: string2msg_ll:
node [asterisk.retail.ua] failed authentication
Sep 30 15:02:28 voipserver.drbd heartbeat: [1568]: info: Heartbeat shutdown
in progress. (1568)
Sep 30 15:02:28 voipserver.drbd heartbeat: [2768]: info: Giving up all HA
resources.
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Releasing
resource group: voipserver.drbd drbddisk::r0
Filesystem::/dev/drbd0::/replica::ext4 IPaddr::
10.0.10.113/24/eth1/10.0.10.255 mysqld asterisk httpd
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/httpd  stop
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/asterisk  stop
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/mysqld  stop
Sep 30 15:02:29 voipserver.drbd heartbeat: [1568]: WARN: string2msg_ll:
node [asterisk.retail.ua] failed authentication
ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
/etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 stop
IPaddr(IPaddr_10.0.10.113)[2960]:2016/09/30_15:02:30 INFO: IP status =
ok, IP_CIP=
/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_10.0.10.113)[2934]:
2016/09/30_15:02:30 INFO:  Success
ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
/etc/ha.d/resource.d/Filesystem /dev/drbd0 /replica ext4 stop
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
Running stop for /dev/drbd0 on /replica
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
Trying to unmount /replica
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
unmounted /replica successfully
/usr/lib/ocf/resource.d//heartbeat/Filesystem(Filesystem_/dev/drbd0)[3042]:
2016/09/30_15:02:31 INFO:  Success
ResourceManager(default)[2781]:2016/09/30_15:02:31 info: Running
/etc/ha.d/resource.d/drbddisk r0 stop
Sep 30 15:02:31 voipserver.drbd heartbeat: [2768]: info: All HA resources
relinquished.
Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: WARN: 1 lost packet(s)
for [voipbackup.drbd] [358:360]
Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: info: No pkts missing
from voipbackup.drbd!
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing HBFIFO
process 1578 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing HBWRITE
process 1580 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing HBREAD
process 1581 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process 1578
exited. 3 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process 1580
exited. 2 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process 1581
exited. 1 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: voipserver.drbd
Heartbeat shutdown complete.
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info: Pacemaker support:
false
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: WARN: Logging daemon is
disabled --enabling logging daemon is recommended
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info:
**
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info: Configuration
validated. Starting heartbeat 3.0.4
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: heartbeat: version
3.0.4
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Heartbeat
generation: 1475232448
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: glib: UDP
Broadcast heartbeat started on port 694 (694) interface eth1
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: glib: UDP
Broadcast heartbeat closed on port 694 interface eth1 - Status: 1
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_TriggerHandler: Added signal manual handler
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_TriggerHandler: Added signal manual handler
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_SignalHandler: Added signal handler for signal 17
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Local status now
set to: 'up'
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Link
voipserver.drbd:eth1 up.
Sep 30 15:13:31 voipserver.drbd heartbeat: [1570]: info: Link
voipbackup.drbd:eth1 up.
Sep 30 15:13:31 voipserver.drbd heartbeat: [1570]: info: Status update for
node voipbackup.drbd: status active