[Sheepdog] corosync.conf

[MORITA Kazutaka]

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