date:20160603

[ClusterLabs] mail server (postfix)

2016-06-03 Thread Dimitri Maziuk

Hi all,

quick question: is anyone running an MTA on an active-passive cluster?
Specifically, I need to do a stop - wait for drbd fs to move over -
update symlinks - then start again -- on both nodes. So that on the
active node the MTA runs with "mail gateway" postfix config in
/drbd/etc/postfix and on the passive: with "send-only" config in
/etc/postfix.

Off the top of my head it looks like defining two postfix resources that
both start/stop the same postfix only at different times/on different
nodes should do the trick. Any gotchas I'm not seeing? Better ways to
accomplish it?

(I know running an MTA that way is not the Approved Way(tm), I have my
reasons for wanting to it like this.)

TIA
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
___
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] Error "xml does not conform to the schema" upon "pcs cluster standby" command

2016-06-03 Thread Jan Pokorný

Hello Nikhil,

On 03/06/16 16:33 +0530, Nikhil Utane wrote:
> The node is up alright.
> 
> [root@airv_cu pcs]# pcs cluster status
> Cluster Status:
>  Stack: corosync
>  Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition WITHOUT quorum
>  Last updated: Fri Jun  3 11:01:32 2016 Last change: Fri Jun  3
> 09:57:52 2016 by hacluster via crmd on airv_cu
>  2 nodes and 0 resources configured
> 
> Upon entering command "pcs cluster standby airv_cu" getting below error.
> Error: cannot load cluster status, xml does not conform to the schema.
> 
> What could be wrong?

if you have a decently recent versions of both pacemaker and pcs (ca 3
months old or newer) it's entirely possible that this commit will
resolve it for you on the pacemaker side:

https://github.com/ClusterLabs/pacemaker/pull/1040/commits/87a82a165ccacaf1a0c48b5e1fad684a8dd2d8c9

I'm just about to provide update to the expected test results and then
it (the whole pull request) is expected to land soon after that.

-- 
Jan (Poki)


pgpMOIycmzA3c.pgp
Description: PGP signature
___
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] Can't get nfs4 to work.

2016-06-03 Thread Stephano-Shachter, Dylan

I had the line,

RPCNFSDARGS="-N 2 -N 4"

which I changed to

RPCNFSDARGS="-N 2"

It turns out someone else who had initially set up the nfs server had
disabled v4 explicitly.

On Fri, Jun 3, 2016 at 10:25 AM, Kai Dupke  wrote:

> On 06/03/2016 04:17 PM, Dylan Stephano-Shachter wrote:
> > Okay turns out the issue was not related to pacemaker (I thought it was).
> > It was just in issue with the nfs config file.
>
> Which was? Even if it is trivial, it might help us to avoid such and
> give the right hint the next time.
>
> regards,
> Kai Dupke
> Senior Product Manager
> Server Product Line
> --
> Sell not virtue to purchase wealth, nor liberty to purchase power.
> Phone:  +49-(0)5102-9310828 Mail: kdu...@suse.com
> Mobile: +49-(0)173-5876766  WWW:  www.suse.com
>
> SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany)
> GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg)
>
> ___
> 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
>
___
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] Can't get nfs4 to work.

2016-06-03 Thread Kai Dupke

On 06/03/2016 04:17 PM, Dylan Stephano-Shachter wrote:
> Okay turns out the issue was not related to pacemaker (I thought it was).
> It was just in issue with the nfs config file.

Which was? Even if it is trivial, it might help us to avoid such and
give the right hint the next time.

regards,
Kai Dupke
Senior Product Manager
Server Product Line
-- 
Sell not virtue to purchase wealth, nor liberty to purchase power.
Phone:  +49-(0)5102-9310828 Mail: kdu...@suse.com
Mobile: +49-(0)173-5876766  WWW:  www.suse.com

SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany)
GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg)

___
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] Can't get nfs4 to work.

2016-06-03 Thread Stephano-Shachter, Dylan

Okay turns out the issue was not related to pacemaker (I thought it was).
It was just in issue with the nfs config file.

On Thu, Jun 2, 2016 at 5:04 PM, Jan Pokorný  wrote:

> On 02/06/16 02:35 +0200, Dennis Jacobfeuerborn wrote:
> > On 01.06.2016 20:25, Stephano-Shachter, Dylan wrote:
> >> I have just finished setting up my HA nfs cluster and I am having a
> small
> >> problem. I would like to have nfs4 working but whenever I try to mount I
> >> get the following message,
> >>
> >> mount: no type was given - I'll assume nfs because of the colon
> >
> > I'm not sure if the type "nfs" is supposed to work with v4 as well but
> > on my systems the mounts use the explicit type "nfs4" so you can try
> > mounting with "-t nfs4".
>
> $ rpm -qf $(man -w mount.nfs)
> > nfs-utils-1.3.3-7.rc4.fc22.x86_64
>
> $ man mount.nfs | fmt -w70 | grep -A2 Under
> >   Under Linux 2.6.32 and later kernel versions, mount.nfs can
> >   mount all NFS file system versions.  Under earlier Linux
> >   kernel versions, mount.nfs4 must be used  for mounting NFSv4
> >   file systems while mount.nfs must be used for NFSv3 and v2.
>
> --
> Jan (Poki)
>
> ___
> 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
>
>
___
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] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

2016-06-03 Thread Ken Gaillot

On 06/02/2016 08:01 PM, Andrew Beekhof wrote:
> On Fri, May 20, 2016 at 1:53 AM, Ken Gaillot  wrote:
>> A recent thread discussed a proposed new feature, a new environment
>> variable that would be passed to resource agents, indicating whether a
>> stop action was part of a recovery.
>>
>> Since that thread was long and covered a lot of topics, I'm starting a
>> new one to focus on the core issue remaining:
>>
>> The original idea was to pass the number of restarts remaining before
>> the resource will no longer tried to be started on the same node. This
>> involves calculating (fail-count - migration-threshold), and that
>> implies certain limitations: (1) it will only be set when the cluster
>> checks migration-threshold; (2) it will only be set for the failed
>> resource itself, not for other resources that may be recovered due to
>> dependencies on it.
>>
>> Ulrich Windl proposed an alternative: setting a boolean value instead. I
>> forgot to cc the list on my reply, so I'll summarize now: We would set a
>> new variable like OCF_RESKEY_CRM_recovery=true
> 
> This concept worries me, especially when what we've implemented is
> called OCF_RESKEY_CRM_restarting.

Agreed; I plan to rename it yet again, to OCF_RESKEY_CRM_start_expected.

> The name alone encourages people to "optimise" the agent to not
> actually stop the service "because its just going to start again
> shortly".  I know thats not what Adam would do, but not everyone
> understands how clusters work.
> 
> There are any number of reasons why a cluster that intends to restart
> a service may not do so.  In such a scenario, a badly written agent
> would cause the cluster to mistakenly believe that the service is
> stopped - allowing it to start elsewhere.
> 
> Its true there are any number of ways to write bad agents, but I would
> argue that we shouldn't be nudging people in that direction :)

I do have mixed feelings about that. I think if we name it
start_expected, and document it carefully, we can avoid any casual mistakes.

My main question is how useful would it actually be in the proposed use
cases. Considering the possibility that the expected start might never
happen (or fail), can an RA really do anything different if
start_expected=true? If the use case is there, I have no problem with
adding it, but I want to make sure it's worthwhile.

>> whenever a start is
>> scheduled after a stop on the same node in the same transition. This
>> would avoid the corner cases of the previous approach; instead of being
>> tied to migration-threshold, it would be set whenever a recovery was
>> being attempted, for any reason. And with this approach, it should be
>> easier to set the variable for all actions on the resource
>> (demote/stop/start/promote), rather than just the stop.
>>
>> I think the boolean approach fits all the envisioned use cases that have
>> been discussed. Any objections to going that route instead of the count?
>> --
>> Ken Gaillot 

___
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] Error "xml does not conform to the schema" upon "pcs cluster standby" command

2016-06-03 Thread Klaus Wenninger

On 06/03/2016 01:39 PM, Nikhil Utane wrote:
> Thanks for your response Klaus.
> Any command to add the cluster name?
> All examples use 'pcs cluster setup' command. But if my cluster is
> already running, how do I update it?
> I tried with crm_attribute:
> crm_attribute -t crm_config -n cluster-name -v mycluster
>
> It has updated in cib but pcs status still doesn't show the cluster name.

Somewhere in the back of my mind something is telling me it wanted to
have the name in corosync.conf
as well.

totem {
...
cluster_name: mycluster
...
}

>
> 
>   
>  name="have-watchdog" value="true"/>
>  name="dc-version" value="1.1.14-5a6cdd1"/>
>  name="cluster-infrastructure" value="corosync"/>
>  name="cluster-name" value="mycluster"/>
>   
>
> [root@airv_cu root]# pcs status
> Cluster name:
>
> -Regards
> Nikhil
>
>
> On Fri, Jun 3, 2016 at 4:46 PM, Klaus Wenninger  > wrote:
>
> On 06/03/2016 01:03 PM, Nikhil Utane wrote:
> > Hi,
> >
> > The node is up alright.
> >
> > [root@airv_cu pcs]# pcs cluster status
> > Cluster Status:
> >  Stack: corosync
> >  Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition
> WITHOUT quorum
> >  Last updated: Fri Jun  3 11:01:32 2016 Last change: Fri Jun
> >  3 09:57:52 2016 by hacluster via crmd on airv_cu
> >  2 nodes and 0 resources configured
> >
> > Upon entering command "pcs cluster standby airv_cu" getting
> below error.
> > Error: cannot load cluster status, xml does not conform to the
> schema.
> >
> > What could be wrong?
> >
> > [root@airv_cu pcs]# pcs cluster cib
> >  epoch="4"
> > num_updates="5" admin_epoch="0" cib-last-written="Fri Jun  3
> 09:57:52
> > 2016" update-origin="airv_cu" update-client="crmd"
> > update-user="hacluster" have-quorum="0" dc-uuid="1">
> >   
> > 
> >   
> >  > name="have-watchdog" value="true"/>
> >  > name="dc-version" value="1.1.14-5a6cdd1"/>
> >  > name="cluster-infrastructure" value="corosync"/>
> Your cluster doesn't have a name. iirc pcs (at least I've seen
> that in a
> version I was working with) doesn't like that.
>
> Something like:
>  name="cluster-name" value="mycluster"/>
>
> >   
> > 
> > 
> >   
> >   
> > 
> > 
> > 
> >   
> >   
> >  > crm-debug-origin="do_state_transition" join="member"
> expected="member">
> >   
> > 
> >   
> >   
> > 
> >   
> > 
> >   
> > 
> >   
> > 
> >
> > -Thanks
> > Nikhil
> >
> >
> >
> > ___
> > 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
>
>
> ___
> 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
>
>

___
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] Error "xml does not conform to the schema" upon "pcs cluster standby" command

2016-06-03 Thread Nikhil Utane

Thanks for your response Klaus.
Any command to add the cluster name?
All examples use 'pcs cluster setup' command. But if my cluster is already
running, how do I update it?
I tried with crm_attribute:
crm_attribute -t crm_config -n cluster-name -v mycluster

It has updated in cib but pcs status still doesn't show the cluster name.


  




  

[root@airv_cu root]# pcs status
Cluster name:

-Regards
Nikhil


On Fri, Jun 3, 2016 at 4:46 PM, Klaus Wenninger  wrote:

> On 06/03/2016 01:03 PM, Nikhil Utane wrote:
> > Hi,
> >
> > The node is up alright.
> >
> > [root@airv_cu pcs]# pcs cluster status
> > Cluster Status:
> >  Stack: corosync
> >  Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition WITHOUT quorum
> >  Last updated: Fri Jun  3 11:01:32 2016 Last change: Fri Jun
> >  3 09:57:52 2016 by hacluster via crmd on airv_cu
> >  2 nodes and 0 resources configured
> >
> > Upon entering command "pcs cluster standby airv_cu" getting below error.
> > Error: cannot load cluster status, xml does not conform to the schema.
> >
> > What could be wrong?
> >
> > [root@airv_cu pcs]# pcs cluster cib
> >  > num_updates="5" admin_epoch="0" cib-last-written="Fri Jun  3 09:57:52
> > 2016" update-origin="airv_cu" update-client="crmd"
> > update-user="hacluster" have-quorum="0" dc-uuid="1">
> >   
> > 
> >   
> >  > name="have-watchdog" value="true"/>
> >  > name="dc-version" value="1.1.14-5a6cdd1"/>
> >  > name="cluster-infrastructure" value="corosync"/>
> Your cluster doesn't have a name. iirc pcs (at least I've seen that in a
> version I was working with) doesn't like that.
>
> Something like:
>  name="cluster-name" value="mycluster"/>
>
> >   
> > 
> > 
> >   
> >   
> > 
> > 
> > 
> >   
> >   
> >  > crm-debug-origin="do_state_transition" join="member" expected="member">
> >   
> > 
> >   
> >   
> > 
> >   
> > 
> >   
> > 
> >   
> > 
> >
> > -Thanks
> > Nikhil
> >
> >
> >
> > ___
> > 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
>
>
> ___
> 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
>
___
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] Error "xml does not conform to the schema" upon "pcs cluster standby" command

2016-06-03 Thread Nikhil Utane

Hi,

The node is up alright.

[root@airv_cu pcs]# pcs cluster status
Cluster Status:
 Stack: corosync
 Current DC: airv_cu (version 1.1.14-5a6cdd1) - partition WITHOUT quorum
 Last updated: Fri Jun  3 11:01:32 2016 Last change: Fri Jun  3
09:57:52 2016 by hacluster via crmd on airv_cu
 2 nodes and 0 resources configured

Upon entering command "pcs cluster standby airv_cu" getting below error.
Error: cannot load cluster status, xml does not conform to the schema.

What could be wrong?

[root@airv_cu pcs]# pcs cluster cib

  

  



  


  
  



  
  

  

  
  

  

  

  


-Thanks
Nikhil
___
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] mail server (postfix)

Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

Re: [ClusterLabs] Can't get nfs4 to work.

Re: [ClusterLabs] Can't get nfs4 to work.

Re: [ClusterLabs] Can't get nfs4 to work.

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

Re: [ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

[ClusterLabs] Error "xml does not conform to the schema" upon "pcs cluster standby" command

9 matches

Site Navigation

Mail list logo

Footer information