Ok,
This 139 error really came from a source code change I did.
I had to pacth heartbeat in order to operate at Ethernet level and I
replaced UPD based ucasts with Ethernet frames directed at each unicast
node.
Along the way, like Nuno said, I was causing a segmentation fault... I
was able to solve that. All is fine now.
BTW: what does the list think about this "move ucasts to Ethernet
frames" change we did ? We simply pick up the original UDP payload and
transmit it with Ethernet frames. On the receivinbg side we pick up the
frame, extract the payload and everything goes fine. We use libpcap for
the L2 manipulations. Any comments ?
see more bellow....
On Wed, 2008-05-21 at 09:30 +0100, David Lee wrote:
> I think rc=139 could also happen when a shared library is missing.
> Heartbeat often tries to invoke other heartbeat-related programs and those
> other programs themselves require various "*.so" files. If such a ".so"
> file is absent this might cause rc=139.
ok. I understand this. thx
>
> The command "ldd {program-name}" should list the ".so" requirements of a
> particular {program-name} and where they are on your system. So try that
> "ldd ..." with the various heartbeat binaries on your system, and look for
> indications of "not found" or similar.
>
> If this is the case then it suggests an error in the packaging of your
> heartbeat package. Let us (the list) know your findings (including your
> package version, where your package came from etc.).
>
> (The packaging can, in principle, ensure that all dependencies are
> fulfilled. But the actual practice (by the packager) of doing this can
> sometimes accidentally miss a dependency.)
got it :)... there was no problem on that side. we use our own packaging
and that part was correct.
>
> Hope that helps.
>
> --
>
> : David Lee I.T. Service :
> : Senior Systems Programmer Computer Centre :
> : UNIX Team Leader Durham University :
> : South Road :
> : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE :
> : Phone: +44 191 334 2752 U.K. :
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
