[Pacemaker] Openais log and cpu occupation

Andrew Beekhof andrew at beekhof.net
Mon Oct 5 09:09:19 UTC 2009


On Sun, Oct 4, 2009 at 7:19 PM, Fausto Lombardi <faulomba at gmail.com> wrote:
> The permissions of what?
>
> The log file that I insert in openas.conf is created and written correctly
> but the logs is still written in messages file.

the log file directive is ignored by pacemaker.
because some processes run as root and some as hacluster, the ones
running as hacluster wont be able to write to the logs.

> I would that in messages file is written only the error/warning logs.

you can specify this in syslog-ng.conf

>
> This is my openais.conf:
>
> # Please read the openais.conf.5 manual page
>
> aisexec {
>     # Run as root - this is necessary to be able to manage resources with
> Pacemaker
>     user:    root
>     group:    root
> }
>
> service {
>     # Load the Pacemaker Cluster Resource Manager
>     ver:       0
>     name:      pacemaker
>     use_mgmtd: yes
>     use_logd:  no
> }
>
> totem {
>     version: 2
>
>     # How long before declaring a token lost (ms)
>     token:          5000
>
>     # 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:           1000
>
>     # How long to wait for consensus to be achieved before starting a new
> round of membership configuration (ms)
>     consensus:      2500
>
>     # 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
>
>     # Stagger sending the node join messages by 1..send_join ms
>     send_join: 45
>
>     # 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
>
> #    rrp_mode:    passive
>
>     # Optionally assign a fixed node id (integer)
>     # nodeid:         1234
>
>     interface {
>         ringnumber: 0
>
>         # The following values need to be set based on your environment
>         bindnetaddr: 192.168.1.0
>         mcastaddr: 226.94.1.1
>         mcastport: 5405
>     }
> #    interface {
> #        ringnumber: 1
> #
> #        # The following values need to be set based on your environment
> #        bindnetaddr: 172.16.0.0
> #        mcastaddr: 226.95.1.1
> #        mcastport: 5505
> #    }
> }
>
> logging {
>     debug: off
>     fileline: off
>     to_file: on
>     to_syslog: off
>     to_stderr: off
>     logfile: /var/log/openais.log
>     syslog_facility: daemon
>     timestamp: on
> }
>
> amf {
>     mode: disabled
> }
>
>
>
> 2009/10/4 E-Blokos <infos at e-blokos.com>
>>
>> did you check permissions ?
>>
>> ----- Original Message -----
>> From: Fausto Lombardi
>> To: pacemaker at clusterlabs.org
>> Sent: Sunday, October 04, 2009 1:09 PM
>> Subject: Re: [Pacemaker] Openais log and cpu occupation
>>
>>
>> The problem fo the log??
>>
>> Thanks.
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> ________________________________
>>
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>> _______________________________________________
>> Pacemaker mailing list
>> Pacemaker at oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
>




More information about the Pacemaker mailing list