[Pacemaker] Openais log and cpu occupation

[Steven Dake]

The openais logging service will use the syslog LOG_NOTICE level.  To
filter in syslog, syslog must be appropriately configured.  The to_file
directive is really meant for debugging and not deployment.  There is no
way to set filter (except to filter debug) levels on to_file directives.
I recommend against using it.

This madness is hopefully addressed in corosync more appropriately.

Regards
-steve

On Sun, 2009-10-04 at 19:19 +0200, Fausto Lombardi 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.
> I would that in messages file is written only the error/warning logs.
> 
> 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