[Openais] Segmentation Fault
sdake at mvista.com
Mon Jan 31 10:36:03 PST 2005
You are using the older (2nd generation) implementation of the
protocol. This bug was in our bugzilla along with several (10+) other
issues relating to the protocol. Because of this the protocol was
reeimplemented based upon totem (3rd generation protocol). This
reeimplementation fixed the issue you describe. We have a bug or two
with the new protocol but I'd expect those issues to be resolved fairly
I'd recommend upgrading to the latest bk or wait until we do a freshmeat
development release which should be next Monday.
On Mon, 2005-01-31 at 09:45, Liam Howlett wrote:
> I seem to have found a bug with the aisexec that causes a segmentation
> fault on one node.
> Here is how to reproduce the fault:
> The software is setup and running no all three nodes.
> - Ctrl-z the last node to join.
> - fg the last node after it is reported to be gone to the rest of the
> - This or a similar message is printed multiple times on all nodes:
> STATE group arut 3 gmi arut 8 highest 7 barrier 8 starting group arut
> - A segmentation fault seems to happen on the oldest node.
> Running on RHEL 3.0 AS with kernel 2.4.21-20.ELsmp
> This is on a dual exon node (all three are the same)
> with 4gbs of ram
> Compiled with GCC:
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.3/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> Thread model: posix
> gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)
> Please let me know if I can give you any other information to help.
> maybe I should try one of the newer nightly builds?
> Liam R. Howlett
> Openais mailing list
> Openais at lists.osdl.org
More information about the Openais