Jan Kalcic wrote:
Dave Blaschke wrote:
Jan Kalcic wrote:
Jan Kalcic wrote:
Hi All,
very strange problem. Heartbeat reset the baud rate to 19200 even
though
the value in ha.cf is 115200. Also, no matter if I set it with stty,
when I start heartbeat it always reset the baud to 19200.
Jan
After several tries I found what the problem is. The line "baud" in
ha.cf must be BEFORE the line "serial". It's incredible how such a
stupid thing can block everything. I don't totally see the logic behind
this and why this is not documented. Maybe it is somewhere, but not
extremely noticeable at all.
Hope this can help someone in the future even if I think two lines in
the documentation would be very very handy. I strongly recommend this.
It is mentioned in the global option section for ha.cf at
http://www.linux-ha.org/ha.cf:
----------------------------------------------------------------------------
Global ha.cf options
It is important to note that certain options in the ha.cf file are
global in nature, and that ordering of these global options is
important in configuring the ha.cf file, since each directive is
interpreted as it is encountered in ha.cf.
These global options are:
*
use_logd <#use_logd>
*
logfacility <#logfacility> /- (deprecated)/
*
logfile <#logfile> /- (deprecated)/
*
debugfile <#debugfile> /- (deprecated)/
*
udpport <#udpport>
*
baud <#baud>
It is recommended that these options be placed first in the ha.cf file
when they are entered. In particular, placing the logging entries
first is especially recommended.
The default values for each of these pages can be found on the web
</ha.cf/DefaultValues>.
------------------------------------------------------------------------------
This doesn't mention the relationship between baud and serial, but in
fact when the serial directive is encountered, the HBcomm/serial
plugin is invoked and during init it looks for baud - if baud has
already been specified then that value is used, otherwise the default
(19200) is used. Probably could use a little clarification under the
serial directive.
Hi Dave,
yes for sure. Few words like the yours would be useful at all.
Things such this are very boring and not always immediately catchable.
Especially with crm, where a lot of data flows in the cable and the
default baud is not enough, the error messages (maybe bad cable?) can
point you to the wrong direction. Also because, once the baud is set to
115200 in ha.cf and the log says that the serial interface has been
initialized, is difficult, at least at the first, to imagine that the
problem you are facing is because of a baud too low, or better, is
because of the baud rate you set is not set. This is rather tricky.
Regards,
Jan
I have added a one-line summary of the above to the serial description,
as well as for bcast and ucast which will use udpport if it is specified
prior to them...
Regards,
Jan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
u
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
