[Sheepdog] corosync.conf

[Ski Mountain]

yes, stupid spelling mistake.  So once I got the spelling mistake fixed fixed, 
it still did not start.  So in the 

/var/log/corosync/corosync.log
Is the fowling error message.  I was able to fix it as it states by adding in 
consensus: 3200
just above the interface line.  Just thought I should reply in case others has 
the same issue as I did when copying the included configuration files.  Any idea 
why that line is not included in the example?  


Apr 30 13:38:06 corosync [SERV  ] Unloading all Corosync service engines.
Apr 30 13:38:06 corosync [SERV  ] Service engine unloaded: corosync extended 
virtual synchrony service
Apr 30 13:38:06 corosync [SERV  ] Service engine unloaded: corosync 
configuration service
Apr 30 13:38:06 corosync [SERV  ] Service engine unloaded: corosync cluster 
closed process group service v1.01
Apr 30 13:38:06 corosync [SERV  ] Service engine unloaded: corosync cluster 
config database access v1.01
Apr 30 13:38:06 corosync [SERV  ] Service engine unloaded: corosync profile 
loading service
Apr 30 13:38:06 corosync [SERV  ] Service engine unloaded: corosync cluster 
quorum service v0.1
Apr 30 13:38:20 corosync [MAIN  ] Corosync Cluster Engine ('1.2.0'): started and 
ready to provide service.
Apr 30 13:38:20 corosync [MAIN  ] Corosync built-in features: nss
Apr 30 13:38:20 corosync [MAIN  ] Successfully read main configuration file 
'/etc/corosync/corosync.conf'.
Apr 30 13:38:20 corosync [MAIN  ] parse error in config: The consensus timeout 
parameter (1200 ms) must be atleast 1.2 * token (1200 ms).
Apr 30 13:38:20 corosync [MAIN  ] Corosync Cluster Engine exiting with status -9 
at main.c:1359.



Thanks




________________________________
From: MORITA Kazutaka <morita.kazutaka at lab.ntt.co.jp>
To: Ski Mountain <ski_the_mountain at yahoo.com>
Cc: sheepdog at lists.wpkg.org
Sent: Thu, April 28, 2011 9:55:31 AM
Subject: Re: [Sheepdog] corosync.conf

At Thu, 28 Apr 2011 06:43:41 -0700 (PDT),
Ski Mountain wrote:
> I am having some corosync configuration issues.  I am very unfamiliar with 
> corosync.  
> 
> 
> 
> When I try to start up corosync I get this error in syslog
> 
> Apr 28 08:59:31 duo corosync[3614]: parse error in config: parse error in 
> config: .
> Apr 28 08:59:31 duo corosync[3614]:   [MAIN  ] Corosync Cluster Engine 
> ('1.2.0'): started and ready to provide service.
> Apr 28 08:59:31 duo corosync[3614]:   [MAIN  ] Corosync built-in features: nss
> Apr 28 08:59:31 duo corosync[3614]:   [MAIN  ] Successfully read main 
> configuration file '/etc/corosync/corosync.conf'.
> Apr 28 08:59:31 duo corosync[3614]:   [MAIN  ] parse error in config: parse 
> error in config: .
> Apr 28 08:59:31 duo corosync[3614]:   [MAIN  ] Corosync Cluster Engine exiting 

> with status -9 at main.c:1331.
> 
> and the "corosync.conf" pretty much copied from 
> http://sourceforge.net/apps/trac/sheepdog/wiki/Corosync%20Config, with the 
> bindnetaddr modified.  What else do I need to do?  I am asuming that I need to 

> incurment ringnumber for each node, is that it.  What could be causing the 
> syntax error, this log is quite lacking in details.  
> 
> 
> Thanks
> 
>  # Please read the corosync.conf 5 manual page
>  compatibility: whitetank
>  totem {
>   version: 2
>   secauth: off
>   threads: 0
>   # Note, fail_recv_const is only needed if you're
>   # having problems with corosync crashing under
>   # heavy sheepdog traffic. This crash is due to
>   # delayed/resent/misordered multicast packets.
>   # fail_recv_const: 5000
>   interface {
>   ringnumber: 0
>   bindnetaddr: 10.1.2.145
>   mcastaddr: 226.94.1.1
>   mcastport: 5405
>   }
>  }
>  logging {
>   fileline: off
>   to_stderr: no
>   to_logfile: yes
>   to_syslog: yes
>   # the pathname of the log file
>   logfile: /var/log/corosyn/corosync.log

I think you don't create /var/log/corosyn (misstype of
/var/log/corosync/corosync.log?).

Thanks,

Kazutaka
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/sheepdog/attachments/20110430/14eea2dc/attachment-0003.html>