Seeking possible causes for an assertion error in socksm.c at line 600: hdr.pkt_type == MPIDI_NEM_TCP_SOCKSM_PKT_ID_INFO || ... #7052
tarunkumar987
started this conversation in
General
Replies: 2 comments 19 replies
-
|
Does it fail for all applications? If not, can you find a small reproducer? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Is there other activity going on during the run, for example, a port scan or some other application that is trying to make connection on a seemingly random port? The assertion is part of a initial handshake check and it appears it is receiving an unrecognized packet after the connection. |
Beta Was this translation helpful? Give feedback.
18 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are hitting following assertion:
Assertion failed in file ...nemesis/netmod/tcp/socksm.c at line 600: hdr.pkt_type == MPIDI_NEM_TCP_SOCKSM_PKT_ID_INFO || ...
I looked at the assert and it looks like this in file socksm.c
MPIU_Assert(hdr.pkt_type == MPIDI_NEM_TCP_SOCKSM_PKT_ID_INFO ||
hdr.pkt_type == MPIDI_NEM_TCP_SOCKSM_PKT_TMPVC_INFO);
We have tried multiple cores from 2 to 8 and the behaviour is same. Also process is aborted and a message appear to suggest that. Mostly it's process 0 which is aborted but I have seen other processes as well reporting the crash. We are using mpich-3.2.1. I'm trying to understand possible causes for this error? I have explored the forum and no possible causes, like machine going out of memory etc are applicable here. Please suggest.
Beta Was this translation helpful? Give feedback.
All reactions