Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #3411 > unrolled thread
| Started by | msouri2003@gmail.com |
|---|---|
| First post | 2013-06-04 07:37 -0700 |
| Last post | 2013-06-05 17:52 -0700 |
| Articles | 5 — 4 participants |
Back to article view | Back to comp.programming
a problem with C++ msouri2003@gmail.com - 2013-06-04 07:37 -0700
Re: a problem with C++ Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-06-04 08:29 -0700
Re: a problem with C++ blmblm@myrealbox.com <blmblm.myrealbox@gmail.com> - 2013-06-04 17:26 +0000
Re: a problem with C++ msouri2003@gmail.com - 2013-06-04 08:44 -0700
Re: a problem with C++ Geoff <geoff@invalid.invalid> - 2013-06-05 17:52 -0700
| From | msouri2003@gmail.com |
|---|---|
| Date | 2013-06-04 07:37 -0700 |
| Subject | a problem with C++ |
| Message-ID | <c50a5019-8d3f-4e13-af42-24baf28eda86@googlegroups.com> |
Hi I use a program in C++ and get this error frequently. Could you please help me to fix it? Unable to read the cmd header on the left child context, other MPI error , error stack: Read failed (1298): an existing connection was forcibly closed by the remote host. (errorno 10054) Aborting: mpiexec on pc failed to communicate with smpd on pc. Other MPI error, error stack: Read failed (1298): an existing connection was forcibly closed by the remote host. (errorno 10054)
[toc] | [next] | [standalone]
| From | Daniel Pitts <newsgroup.nospam@virtualinfinity.net> |
|---|---|
| Date | 2013-06-04 08:29 -0700 |
| Message-ID | <CJnrt.28933$xl6.17439@newsfe15.iad> |
| In reply to | #3411 |
On 6/4/13 7:37 AM, msouri2003@gmail.com wrote: > Hi > I use a program in C++ and get this error frequently. Could you please help me to fix it? > Unable to read the cmd header on the left child context, other MPI > error , error stack: > Read failed (1298): an existing connection was forcibly closed by the > remote host. (errorno 10054) > Aborting: mpiexec on pc failed to communicate with smpd on pc. Other > MPI error, error stack: > Read failed (1298): an existing connection was forcibly closed by the > remote host. (errorno 10054) > That is not a problem with C++, but a problem with the program. We can't help fix a program we can't see. This is not comp.programming.psychics. Actually, it looks more like a network problem, or a problem with your remote software. Either way, you're either asking the wrong question or asking the question wrong.
[toc] | [prev] | [next] | [standalone]
| From | blmblm@myrealbox.com <blmblm.myrealbox@gmail.com> |
|---|---|
| Date | 2013-06-04 17:26 +0000 |
| Message-ID | <b16mapF7pu7U1@mid.individual.net> |
| In reply to | #3412 |
In article <CJnrt.28933$xl6.17439@newsfe15.iad>, Daniel Pitts <newsgroup.nospam@virtualinfinity.net> wrote: > On 6/4/13 7:37 AM, msouri2003@gmail.com wrote: > > Hi > > I use a program in C++ and get this error frequently. Could you please > help me to fix it? > > Unable to read the cmd header on the left child context, other MPI > > error , error stack: > > Read failed (1298): an existing connection was forcibly closed by the > > remote host. (errorno 10054) > > Aborting: mpiexec on pc failed to communicate with smpd on pc. Other > > MPI error, error stack: > > Read failed (1298): an existing connection was forcibly closed by the > > remote host. (errorno 10054) > > > That is not a problem with C++, but a problem with the program. > > We can't help fix a program we can't see. This is not > comp.programming.psychics. > > Actually, it looks more like a network problem, or a problem with your > remote software. Either way, you're either asking the wrong question or > asking the question wrong. The OP *might* try asking the question again in comp.parallel.mpi -- "mpiexec" in the error message makes me think this is an MPI-based program, and while comp.parallel.mpi isn't very active, someone there might have some useful thoughts to share about what the error messages mean. -- B. L. Massingill ObDisclaimer: I don't speak for my employers; they return the favor.
[toc] | [prev] | [next] | [standalone]
| From | msouri2003@gmail.com |
|---|---|
| Date | 2013-06-04 08:44 -0700 |
| Message-ID | <06090309-8a56-47d3-b33d-897a77cd6b3c@googlegroups.com> |
| In reply to | #3411 |
On Tuesday, June 4, 2013 6:07:19 PM UTC+3:30, msour...@gmail.com wrote: > Hi > > I use a program in C++ and get this error frequently. Could you please help me to fix it? > > Unable to read the cmd header on the left child context, other MPI > > error , error stack: > > Read failed (1298): an existing connection was forcibly closed by the > > remote host. (errorno 10054) > > Aborting: mpiexec on pc failed to communicate with smpd on pc. Other > > MPI error, error stack: > > Read failed (1298): an existing connection was forcibly closed by the > Dear Daniel thank you for your reply. i think the problem is not about program. some times make internet connect or disconnect causes this error. or running another program.
[toc] | [prev] | [next] | [standalone]
| From | Geoff <geoff@invalid.invalid> |
|---|---|
| Date | 2013-06-05 17:52 -0700 |
| Message-ID | <s7nvq8piqulockmrh8tuhhgfadgvqgobrs@4ax.com> |
| In reply to | #3411 |
On Tue, 4 Jun 2013 07:37:19 -0700 (PDT), msouri2003@gmail.com wrote: >Hi >I use a program in C++ and get this error frequently. Could you please help me to fix it? >Unable to read the cmd header on the left child context, other MPI >error , error stack: >Read failed (1298): an existing connection was forcibly closed by the >remote host. (errorno 10054) >Aborting: mpiexec on pc failed to communicate with smpd on pc. Other >MPI error, error stack: >Read failed (1298): an existing connection was forcibly closed by the >remote host. (errorno 10054) This smells suspiciously like a Windows Sockets error code. WSAECONNRESET10054 Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.programming
csiph-web