<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt">yes, stupid spelling mistake. So once I got the spelling mistake fixed fixed, it still did not start. So in the <br>/var/log/corosync/corosync.log<br>Is the fowling error message. I was able to fix it as it states by adding in <br>consensus: 3200<br>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? <br><br>Apr 30 13:38:06 corosync [SERV ] Unloading all Corosync service engines.<br>Apr 30 13:38:06 corosync [SERV ] Service engine unloaded: corosync extended virtual synchrony service<br>Apr 30 13:38:06 corosync [SERV ] Service engine unloaded: corosync configuration service<br>Apr 30 13:38:06
corosync [SERV ] Service engine unloaded: corosync cluster closed process group service v1.01<br>Apr 30 13:38:06 corosync [SERV ] Service engine unloaded: corosync cluster config database access v1.01<br>Apr 30 13:38:06 corosync [SERV ] Service engine unloaded: corosync profile loading service<br>Apr 30 13:38:06 corosync [SERV ] Service engine unloaded: corosync cluster quorum service v0.1<br>Apr 30 13:38:20 corosync [MAIN ] Corosync Cluster Engine ('1.2.0'): started and ready to provide service.<br>Apr 30 13:38:20 corosync [MAIN ] Corosync built-in features: nss<br>Apr 30 13:38:20 corosync [MAIN ] Successfully read main configuration file '/etc/corosync/corosync.conf'.<br>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).<br>Apr 30 13:38:20 corosync [MAIN ] Corosync Cluster Engine exiting with status -9 at
main.c:1359.<br><br><br><div>Thanks<br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp><br><b><span style="font-weight: bold;">To:</span></b> Ski Mountain <ski_the_mountain@yahoo.com><br><b><span style="font-weight: bold;">Cc:</span></b> sheepdog@lists.wpkg.org<br><b><span style="font-weight: bold;">Sent:</span></b> Thu, April 28, 2011 9:55:31 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Sheepdog] corosync.conf<br></font><br>
At Thu, 28 Apr 2011 06:43:41 -0700 (PDT),<br>Ski Mountain wrote:<br>> I am having some corosync configuration issues. I am very unfamiliar with <br>> corosync. <br>> <br>> <br>> <br>> When I try to start up corosync I get this error in syslog<br>> <br>> Apr 28 08:59:31 duo corosync[3614]: parse error in config: parse error in <br>> config: .<br>> Apr 28 08:59:31 duo corosync[3614]: [MAIN ] Corosync Cluster Engine <br>> ('1.2.0'): started and ready to provide service.<br>> Apr 28 08:59:31 duo corosync[3614]: [MAIN ] Corosync built-in features: nss<br>> Apr 28 08:59:31 duo corosync[3614]: [MAIN ] Successfully read main <br>> configuration file '/etc/corosync/corosync.conf'.<br>> Apr 28 08:59:31 duo corosync[3614]: [MAIN ] parse error in config: parse <br>> error in config: .<br>> Apr 28 08:59:31 duo corosync[3614]: [MAIN ]
Corosync Cluster Engine exiting <br>> with status -9 at main.c:1331.<br>> <br>> and the "corosync.conf" pretty much copied from <br><span>> <a target="_blank" href="http://sourceforge.net/apps/trac/sheepdog/wiki/Corosync%20Config">http://sourceforge.net/apps/trac/sheepdog/wiki/Corosync%20Config</a>, with the </span><br>> bindnetaddr modified. What else do I need to do? I am asuming that I need to <br>> incurment ringnumber for each node, is that it. What could be causing the <br>> syntax error, this log is quite lacking in details. <br>> <br>> <br>> Thanks<br>> <br>> # Please read the corosync.conf 5 manual page<br>> compatibility: whitetank<br>> totem {<br>> version: 2<br>> secauth: off<br>> threads: 0<br>> # Note, fail_recv_const is only needed if you're<br>> # having problems with corosync crashing under<br>>
# heavy sheepdog traffic. This crash is due to<br>> # delayed/resent/misordered multicast packets.<br>> # fail_recv_const: 5000<br>> interface {<br>> ringnumber: 0<br>> bindnetaddr: 10.1.2.145<br>> mcastaddr: 226.94.1.1<br>> mcastport: 5405<br>> }<br>> }<br>> logging {<br>> fileline: off<br>> to_stderr: no<br>> to_logfile: yes<br>> to_syslog: yes<br>> # the pathname of the log file<br>> logfile: /var/log/corosyn/corosync.log<br><br>I think you don't create /var/log/corosyn (misstype of<br>/var/log/corosync/corosync.log?).<br><br>Thanks,<br><br>Kazutaka<br></div></div>
</div></body></html>