[erlang-questions] Corrupted term on distribution channel from a C-Node
Mon Apr 27 15:53:43 CEST 2015
An HTML attachment was scrubbed...
-------------- next part --------------
It's non deterministic for sure. We run both a primary and secondary app reading in the same data (multicast). One had this issue and the other did not. Although the hardware is slightly different, the versions and configurations are basically identical.
I believe we are running R16B03. I'll be able to double check tomorrow (can't believe I forgot to include that in the first email).
It's actually a slightly patched version to handle the issue of not being able to properly lock a tcp connection as the receive function would block but handle the heart beat response internally. That version can be found here:
I'm sending from my phone so apologies for any typos or mistakes.
Thanks again for your help!
On 27 Apr 2015 21:38, Jesper Louis Andersen <jesper.louis.andersen@REDACTED> wrote:
On Mon, Apr 27, 2015 at 11:45 AM, Peter Membrey <peter@REDACTED> wrote:
> Having gone through the message with the EDP and external term man pages,
> it looks like we're getting a corrupt SEND command. In both cases the
> cookie is not being encoded correctly (the cookie is definitely not empty),
> and in the second instance, we have a 0 where we'd expect a 103. The
> messages following both corrupted SEND messages were decodable with
> binary_to_term/1 and the payload looked good.
Is this nondeterministic? I wouldn't entirely rule out the possibility of
the hardware messing up, or some error in the code elsewhere manipulating
the wrong data. Not that I can pinpoint *that* is what is happening, but do
not rule it out from the start that this could be a hardware thing. What
version of Erlang is this? A recent one, or an earlier one?
More information about the erlang-questions