Re: [ClusterLabs] DRBD Insufficient Privileges Error
On 11/20/2016 01:58 PM, Jasim Alam wrote: > Hi, > > > > I am trying to setup two node H/A cluster with DRBD. Following is my > configuration > > > > /[root@node-1 ~]# pcs config/ > > /Cluster Name: Cluster-1/ > > /Corosync Nodes:/ > > /node-1 node-2 / > > /Pacemaker Nodes:/ > > /node-1 node-2 / > > / / > > /Resources: / > > / Resource: vip (class=ocf provider=heartbeat type=IPaddr2)/ > > / Attributes: ip=103.9.185.211 cidr_netmask=32 / > > / Operations: start interval=0s timeout=20s (vip-start-interval-0s)/ > > / stop interval=0s timeout=20s (vip-stop-interval-0s)/ > > / monitor interval=30s (vip-monitor-interval-30s)/ > > /Resource: apache (class=ocf provider=heartbeat type=apache)/ > > / Attributes: configfile=/etc/httpd/conf/httpd.conf > statusurl=http://localhost/server-status / > > / Operations: start interval=0s timeout=40s (apache-start-interval-0s)/ > > / stop interval=0s timeout=60s (apache-stop-interval-0s)/ > > / monitor interval=1min (apache-monitor-interval-1min)/ > > /Master: StorageClone/ > > / Meta Attrs: master-max=1 master-node-max=1 clone-max=2 > clone-node-max=1 notify=true / > > / Resource: storage (class=ocf provider=linbit type=drbd)/ > > / Attributes: drbd_resource=drbd0 / > > / Operations: start interval=0s timeout=240 (storage-start-interval-0s)/ > > / promote interval=0s timeout=90 > (storage-promote-interval-0s)/ > > / demote interval=0s timeout=90 (storage-demote-interval-0s)/ > > / stop interval=0s timeout=100 (storage-stop-interval-0s)/ > > / monitor interval=60s (storage-monitor-interval-60s)/ > > / / > > /Stonith Devices: / > > /Fencing Levels: / > > / / > > /Location Constraints:/ > > / Resource: apache/ > > /Enabled on: node-1 (score:50) (id:location-apache-node-1-50)/ > > /Ordering Constraints:/ > > / start vip then start apache (kind:Mandatory) > (id:order-vip-apache-mandatory)/ > > /Colocation Constraints:/ > > / vip with apache (score:INFINITY) (id:colocation-vip-apache-INFINITY)/ > > / / > > /Resources Defaults:/ > > /No defaults set/ > > /Operations Defaults:/ > > /No defaults set/ > > / / > > /Cluster Properties:/ > > /cluster-infrastructure: corosync/ > > /cluster-name: Cluster-1/ > > /dc-version: 1.1.13-10.el7_2.4-44eb2dd/ > > /have-watchdog: false/ > > /no-quorum-policy: ignore/ > > /stonith-enabled: false/ > > > > The problem is I am getting insufficient privilege error on second node > > > > /[root@node-1 ~]# pcs status/ > > /Cluster name: PSD-1/ > > /Last updated: Mon Nov 21 01:44:52 2016 Last change: Mon Nov 21 > 01:19:17 2016 by root via cibadmin on node-1/ > > /Stack: corosync/ > > /Current DC: node-1 (version 1.1.13-10.el7_2.4-44eb2dd) - partition with > quorum/ > > /2 nodes and 4 resources configured/ > > / / > > /Online: [ node-1 node-2 ]/ > > / / > > /Full list of resources:/ > > / / > > /vip(ocf::heartbeat:IPaddr2): Started node-1/ > > /apache (ocf::heartbeat:apache):Started node-1/ > > /Master/Slave Set: StorageClone [storage]/ > > / storage(ocf::linbit:drbd): FAILED node-2 (unmanaged)/ > > / Masters: [ node-1 ]/ > > / / > > /Failed Actions:/ > > /* storage_stop_0 on node-2 'insufficient privileges' (4): call=16, > status=complete, exitreason='none',/ > > /last-rc-change='Mon Nov 21 01:19:17 2016', queued=0ms, exec=2ms/ > > / / > > / / > > /PCSD Status:/ > > / node-1: Online/ > > / node-2: Online/ > > / / > > /Daemon Status:/ > > / corosync: active/disabled/ > > / pacemaker: active/disabled/ > > / pcsd: active/enabled/ > > > > but DRBD seems okay for both nodes > > > > / [root@node-1 ~]# drbd-overview / > > / 0:drbd0/0 Connected Primary/Secondary UpToDate/UpToDate/ > > // > > / [root@node-2 ~]# drbd-overview / > > / 0:drbd0/0 Connected Secondary/Primary UpToDate/UpToDate/ > > > > Log of node2 > > > > /[root@node-2 ~]# tail -n 10 /var/log/messages/ > > /Nov 21 01:19:17 node-2 crmd[4060]: notice: State transition S_NOT_DC > -> S_PENDING [ input=I_PENDING cause=C_FSA_INTERNAL > origin=do_election_count_vote ]/ > > /Nov 21 01:19:17 node-2 crmd[4060]: notice: State transition S_PENDING > -> S_NOT_DC [ input=I_NOT_DC cause=C_HA_MESSAGE > origin=do_cl_join_finalize_respond ]/ > > /Nov 21 01:19:17 node-2 crmd[4060]: error: Failed to retrieve > meta-data for ocf:linbit:drbd/ Pacemaker is unable to get the metadata for the resource agent. Try getting it manually: OCF_ROOT=/usr/lib/ocf /usr/lib/ocf/resource.d/linbit/drbd meta-data If that works, check whether selinux is blocking it. > > /Nov 21 01:19:17 node-2 crmd[4060]: warning: No metadata found for > drbd::ocf:linbit: Input/output error (-5)/ > > /Nov 21 01:19:17 node-2 crmd[4060]: error: No metadata for > linbit::ocf:drbd/ > > /Nov 21 01:19:17 node-2 crmd[4060]: notice: Operation > storage_monitor_
[ClusterLabs] Stonith : meta-data contains no resource-agent element
Hello Pacemaker admins, We have recently updated to Pacemaker version 1.1.15 Before that we were using Pacemaker version 1.1.10 With Pacemaker version 1.1.10, our Stonith ssh agent use to work. Now once we upgraded to Pacemaker version 1.1.15 we see below errors for basic Stonith configuration as explained in [http://clusterlabs.org/doc/crm_fencing.html] = crm configure primitive st-ssh stonith:external/ssh params hostlist="node1 node2" ERROR: stonith:external/ssh: meta-data contains no resource-agent element ERROR: None ERROR: stonith:external/ssh: meta-data contains no resource-agent element ERROR: stonith:external/ssh: no such resource agent Additional info Below is stonith -L output = /home/root# stonith -L apcmaster apcsmart baytech cyclades drac3 external/drac5 external/dracmc-telnet external/hetzner external/hmchttp external/ibmrsa external/ibmrsa-telnet external/ipmi external/ippower9258 external/kdumpcheck external/libvirt external/nut external/rackpdu external/riloe external/sbd external/ssh external/vcenter external/vmware external/xen0 external/xen0-ha ibmhmc meatware null nw_rpc100s rcd_serial rps10 ssh suicide wti_nps = Above agents are in /usr/lib/stonith/plugins directory Please can anyone provide solution to resolve above issue. Thanks Jitendra ___ Users mailing list: Users@clusterlabs.org http://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] Stonith : meta-data contains no resource-agent element
Hello Pacemaker admins, We have recently updated to Pacemaker version 1.1.15 Before that we were using Pacemaker version 1.1.10 With Pacemaker version 1.1.10, our Stonith ssh agent use to work. Now once we upgraded to Pacemaker version 1.1.15 we see below errors for basic Stonith configuration as explained in [http://clusterlabs.org/doc/crm_fencing.html] = crm configure primitive st-ssh stonith:external/ssh params hostlist="node1 node2" ERROR: stonith:external/ssh: meta-data contains no resource-agent element ERROR: None ERROR: stonith:external/ssh: meta-data contains no resource-agent element ERROR: stonith:external/ssh: no such resource agent Additional info Below is stonith -L output = /home/root# stonith -L apcmaster apcsmart baytech cyclades drac3 external/drac5 external/dracmc-telnet external/hetzner external/hmchttp external/ibmrsa external/ibmrsa-telnet external/ipmi external/ippower9258 external/kdumpcheck external/libvirt external/nut external/rackpdu external/riloe external/sbd external/ssh external/vcenter external/vmware external/xen0 external/xen0-ha ibmhmc meatware null nw_rpc100s rcd_serial rps10 ssh suicide wti_nps = Above agents are in /usr/lib/stonith/plugins directory Please can anyone provide solution to resolve above issue. Thanks Jitendra ___ Users mailing list: Users@clusterlabs.org http://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: How to specify two different subnets in NFS exportfs cluster resource on RHEL 7?
>>> "MOLLO RICCARDO (Fornitori Gruppo ISP)" schrieb am 21.11.2016 um 10:04 in Nachricht <66217ee78fcc4f79af051c1ed7655...@exc13tmpmr04.sede.corp.sanpaoloimi.com>: > Hello guys, > > I have a question: > > I'm configuring a NFS export resource on a RHEL 7 cluster, and I need to let > a shared directory be mountable from clients belonging to different > subnetworks. > For example, the following command obviously works fine (with only one > network defined): > > pcs resource create TEST-EXPORTFS ocf:heartbeat:exportfs > clientspec=192.168.1.0/24 options=rw,sync,no_root_squash directory=/test > fsid=1 > > but how can I add a second network in the "clientspec" parameter (for > example: 192.168.100.0/24) so clients from both subnets can mount the shared > directory? Just add a second exportfs resource! > It's easy to do using the good old /etc/exports, but no idea about doing > this via exportfs cluster resource. > > I haven't been able to find any help in the official documentation (neither > from RedHat nor from Linux-HA). > > Thanks in advance for any precious help. > > > -- > > Riccardo Mollo > > > Prima di stampare, pensa all'ambiente ** Think about the environment before > printing > > > > Il presente messaggio, inclusi gli eventuali allegati, ha natura aziendale e > potrebbe contenere informazioni confidenziali e/o riservate. Chiunque lo > ricevesse per errore, ? pregato di avvisare tempestivamente il mittente e di > cancellarlo. > E' strettamente vietata qualsiasi forma di utilizzo, riproduzione o > diffusione non autorizzata del contenuto di questo messaggio o di parte di > esso. > Pur essendo state assunte le dovute precauzioni per ridurre al minimo il > rischio di trasmissione di virus, si suggerisce di effettuare gli opportuni > controlli sui documenti allegati al presente messaggio. Non si assume alcuna > responsabilit? per eventuali danni o perdite derivanti dalla presenza di > virus. > > Per lo svolgimento delle attivit? di investimento nel Regno Unito, la > societ? ? autorizzata da Banca d'Italia ed ? soggetta alla vigilanza limitata > della Financial Conduct Authority ( FCA ) e della Prudential Regulation > Authority ( PRA ) . Maggiori informazioni in merito ai poteri di vigilanza > della Financial Conduct Authority ( FCA ) e della Prudential Regulation > Authority ( PRA ) sono a disposizione previa richiesta. > > Nel Regno Unito Intesa Sanpaolo S.p.A. opera attraverso la filiale di > Londra, sita in 90 Queen Street, London EC4N 1SA, registrata in Inghilterra & > Galles sotto No.FC016201, Branch No.BR36 > > In osservanza dei requisito imposti dal Internal Revenue Service (Agenzia > delle Entrate degli Stati Uniti), qualunque discussione relativa a temi di > natura fiscale contenuta in questo messaggio o nei suoi allegati non e' > intesa ne' e' stata scritta per essere utilizzata, ne' puo' essere utilizata > per (i) evitare l'imposizione di gravami fiscali secondo il codice tributario > vigente negli Stati Uniti o (ii) per promuovere, sollecitare o raccomandare > una operazione finanziaria o altra transazione indirizzata ad un altro > destinatario. > > Nella Repubblica d'Irlanda, Intesa Sanpaolo Bank Ireland plc ? regolamentata > dalla Banca Centrale d'Irlanda ed ? parte del Gruppo Bancario Intesa Sanpaolo > S.p.A. Registrata in Irlanda come societ? numero 125216 - IVA Reg. IE4817418C > IE, sita in, KBC House, 4 George Dock, IFSC, Dublino 1, Irlanda. > > *** > > > > This email (including any attachment) is a corporate message and may contain > confidential and/or privileged and/or proprietary information. If you have > received this email in error, please notify the sender immediately, do not > use or share it and destroy this email. Any unauthorised use, copying or > disclosure of the material in this email or of parts hereof (including > reliance thereon) is strictly forbidden. > We have taken precautions to minimize the risk of transmitting software > viruses but nevertheless advise you to carry out your own virus checks on any > attachment of this message. We accept no liability for loss or damage caused > by software viruses. > > For the conduct of investment business in the UK, the Company is authorised > by Banca d'Italia and subject to limited regulation in the UK by the > Financial Conduct Authority ( FCA ) and the Prudential Regulation Authority ( > PRA ). Details about the extent of our regulation by the Financial Conduct > Authority ( FCA ) and the Prudential Regulation Authority ( PRA ) are > available from us on request. > > In the UK Intesa Sanpaolo S.p.A. operates through its London Branch, located > at 90 Queen Street, London EC4N 1SA. Registered in England & Wales under > No.FC016201, Branch No.BR36 > > To comply with requirements imposed by the IRS, we inform you that any > discussion of U.S. federal tax issues contained herein (
[ClusterLabs] How to specify two different subnets in NFS exportfs cluster resource on RHEL 7?
Hello guys, I have a question: I'm configuring a NFS export resource on a RHEL 7 cluster, and I need to let a shared directory be mountable from clients belonging to different subnetworks. For example, the following command obviously works fine (with only one network defined): pcs resource create TEST-EXPORTFS ocf:heartbeat:exportfs clientspec=192.168.1.0/24 options=rw,sync,no_root_squash directory=/test fsid=1 but how can I add a second network in the "clientspec" parameter (for example: 192.168.100.0/24) so clients from both subnets can mount the shared directory? It's easy to do using the good old /etc/exports, but no idea about doing this via exportfs cluster resource. I haven't been able to find any help in the official documentation (neither from RedHat nor from Linux-HA). Thanks in advance for any precious help. -- Riccardo Mollo Prima di stampare, pensa all'ambiente ** Think about the environment before printing Il presente messaggio, inclusi gli eventuali allegati, ha natura aziendale e potrebbe contenere informazioni confidenziali e/o riservate. Chiunque lo ricevesse per errore, ? pregato di avvisare tempestivamente il mittente e di cancellarlo. E' strettamente vietata qualsiasi forma di utilizzo, riproduzione o diffusione non autorizzata del contenuto di questo messaggio o di parte di esso. Pur essendo state assunte le dovute precauzioni per ridurre al minimo il rischio di trasmissione di virus, si suggerisce di effettuare gli opportuni controlli sui documenti allegati al presente messaggio. Non si assume alcuna responsabilit? per eventuali danni o perdite derivanti dalla presenza di virus. Per lo svolgimento delle attivit? di investimento nel Regno Unito, la societ? ? autorizzata da Banca d'Italia ed ? soggetta alla vigilanza limitata della Financial Conduct Authority ( FCA ) e della Prudential Regulation Authority ( PRA ) . Maggiori informazioni in merito ai poteri di vigilanza della Financial Conduct Authority ( FCA ) e della Prudential Regulation Authority ( PRA ) sono a disposizione previa richiesta. Nel Regno Unito Intesa Sanpaolo S.p.A. opera attraverso la filiale di Londra, sita in 90 Queen Street, London EC4N 1SA, registrata in Inghilterra & Galles sotto No.FC016201, Branch No.BR36 In osservanza dei requisito imposti dal Internal Revenue Service (Agenzia delle Entrate degli Stati Uniti), qualunque discussione relativa a temi di natura fiscale contenuta in questo messaggio o nei suoi allegati non e' intesa ne' e' stata scritta per essere utilizzata, ne' puo' essere utilizata per (i) evitare l'imposizione di gravami fiscali secondo il codice tributario vigente negli Stati Uniti o (ii) per promuovere, sollecitare o raccomandare una operazione finanziaria o altra transazione indirizzata ad un altro destinatario. Nella Repubblica d'Irlanda, Intesa Sanpaolo Bank Ireland plc ? regolamentata dalla Banca Centrale d'Irlanda ed ? parte del Gruppo Bancario Intesa Sanpaolo S.p.A. Registrata in Irlanda come societ? numero 125216 - IVA Reg. IE4817418C IE, sita in, KBC House, 4 George Dock, IFSC, Dublino 1, Irlanda. *** This email (including any attachment) is a corporate message and may contain confidential and/or privileged and/or proprietary information. If you have received this email in error, please notify the sender immediately, do not use or share it and destroy this email. Any unauthorised use, copying or disclosure of the material in this email or of parts hereof (including reliance thereon) is strictly forbidden. We have taken precautions to minimize the risk of transmitting software viruses but nevertheless advise you to carry out your own virus checks on any attachment of this message. We accept no liability for loss or damage caused by software viruses. For the conduct of investment business in the UK, the Company is authorised by Banca d'Italia and subject to limited regulation in the UK by the Financial Conduct Authority ( FCA ) and the Prudential Regulation Authority ( PRA ). Details about the extent of our regulation by the Financial Conduct Authority ( FCA ) and the Prudential Regulation Authority ( PRA ) are available from us on request. In the UK Intesa Sanpaolo S.p.A. operates through its London Branch, located at 90 Queen Street, London EC4N 1SA. Registered in England & Wales under No.FC016201, Branch No.BR36 To comply with requirements imposed by the IRS, we inform you that any discussion of U.S. federal tax issues contained herein (including any attachments) was not intended or written to be used, and cannot be used by you, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting, marketing or recommending any transaction or matter addressed herein to another party. In the Republic of Ireland, Intesa Sanpaolo Bank Ireland plc is regulated by the Central Bank of Ireland and is a member of the Intes
