[ClusterLabs] pacemaker-mgmtd start on boot

[Gao,Yan]

On 03/03/2015 04:22 PM, Fiber Mountain wrote:
> 
> Sorry if this is not the proper mailing list. I am running pacemaker
> 1.1.10 with corosync 2 on Ubuntu Server 14.04 LTS. I installed pacemaker
> manager (mgmtd) and the client (crm_gui). I am able to manually start
> mgmtd by issueing the “sudo /usr/lib/heartbeat/mgmtd” command, but for
> some reason, I cannot get it to automatically start at system boot. I
> added the following as suggested in features section of the FAQ on the
> clusterlab website:
>  
> service {
>         # Load the Pacemaker Cluster Resource Manager
>         name: pacemaker
>         ver:  0
> }
> and add
>         use_mgmtd: 1
> before the closing bracket.
This only works with corosync-1.x, which is able to help spawn
pacemaker daemons and mgmtd.

For corosync-2.x, Dori Seliskar kindly created a systemd file for it

http://ds.delo.si/pacemaker-mgmt/fedora20/

, which I haven't yet got the chance to put into the source.
You may want to give it a try.

BTW, you may also want to take a look at hawk or pcs-gui, unless
pacemaker-mgmt is really your favourite ;-) I will no longer add any new
features for pacemaker-mgmt.

Regards,
  Yan


> I also tried to move the use_mgmtd: 1 to be within the services { }
> section as I saw that in some of the blogs. But either way I try, when I
> reboot the system, mgmtd does not start.
> Not sure what I am doing wrong. My whole corosync.conf is as shown
> below. Any help would  be greatly appreciated.
>  
>  
> #cat corosync.conf
> totem {
>         version: 2
>         # How long before declaring a token lost (ms)
>         token: 3000
>         # How many token retransmits before forming a new configuration
>         token_retransmits_before_loss_const: 10
>         # How long to wait for join messages in the membership protocol (ms)
>         join: 60
>         # How long to wait for consensus to be achieved before starting
> a new round of membership configuration (ms)
>         consensus: 3600
>         # Turn off the virtual synchrony filter
>         vsftype: none
>         # Number of messages that may be sent by one processor on
> receipt of the token
>         max_messages: 20
>         # Limit generated nodeids to 31-bits (positive signed integers)
>         clear_node_high_bit: yes
>         # Disable encryption
>         secauth: off
>         # How many threads to use for encryption/decryption
>         threads: 0
>         # Optionally assign a fixed node id (integer)
>         # nodeid: 1234
>         # This specifies the mode of redundant ring, which may be none,
> active, or passive.
>         rrp_mode: none
>         interface {
>                 # The following values need to be set based on your
> environment
>                 ringnumber: 0
>                 bindnetaddr: 10.0.6.0
>                 mcastaddr: 226.94.1.1
>                 mcastport: 5406
>         }
> }
> service {
>         ver: 0
>         name: pacemaker
>         use_mgmtd: 1
> }
> amf {
>         mode: disabled
> }
> quorum {
>         # Quorum for the Pacemaker Cluster Resource Manager
>         provider: corosync_votequorum
>         expected_votes: 1
> }
> aisexec {
>         user:   root
>         group:  root
> }
> logging {
>         fileline: off
>         to_stderr: yes
>         to_logfile: no
>         to_syslog: yes
>         syslog_facility: daemon
>         debug: off
>         timestamp: on
>         logger_subsys {
>                 subsys: AMF
>                 debug: off
>                 tags: enter|leave|trace1|trace2|trace3|trace4|trace6
>         }
> }
> 
> Thanks,
> Keith
>  
>  
> 
> 
> _______________________________________________
> Users mailing list: Users at 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
> 

-- 
Gao,Yan <ygao at suse.com>
Senior Software Engineer
SUSE LINUX GmbH