Msst=tcp Lost The Connection. System Error Is Broken Pipe
Contents |
to XSMG242I? Technote (troubleshooting) Problem(Abstract) When sending from IBM Sterling Connect:Direct xsmg621i for z/OS to Connect:Direct for UNIX, error XSMG242I may be
Xsmg600i
followed by errors XIPT016I, XSMG621I and XSMG631I. Are these errors related to the initial XSMG242I?
A Receive From The Remote Node Operation Failed.
This article does not address the root cause of the XSMG242I. See below for a link to a possible resolution. Symptom The following sequence
Xsmg604i
of errors may occur when Connect:Direct for z/OS sends to Connect:Direct for UNIX. On the z/OS side: XSMG242I 'The Session Manager could not create a user profile.' On the UNIX side: MSGI=XSMG242I MSST=Create user profile - sdsc_create failed MSGI=XIPT016I MSGT=TCP lost the connection. System error is Connection reset by peer. system error is broken pipe connect direct Message ID XIPT016I, rc=16, fdbk=73. MSGI=XSMG621I MSGT=A receive from the remote node operation failed. Message ID XSMG621I, rc=8, fdbk=0. MSGI=XSMG631I MSGT=SMGR failed to receive an FMH. Diag=XIPT016I. Message ID XSMG631I, rc=16, fdbk=16. Environment This may occur when sending from Connect:Direct for z/OS to Connect:Direct for UNIX. Resolving the problem Yes, these errors are all related to the initial XSMG242I. Once that error is resolved, the secondary errors will no longer occur. This Technote may assist in resolving the XSMG242I: Technote 1529661 Cross reference information Segment Product Component Platform Version Edition Commerce Sterling Connect:Direct for UNIX Document information More support for: Sterling Connect:Direct for z/OS Software version: 5.0, 5.1, 5.2 Operating system(s): z/OS Reference #: 1965534 Modified date: 02 September 2015 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
party Communication; STERLINGNFX Technote (troubleshooting) Problem(Abstract) C:D UNIX stats XIPT016I + XSMG621I + XSMG631I + XSMG600I Symptom The combination of error message id xsmg600i messages below is the result of a non-C:D application trying to connect msst=a receive from the remote node operation failed. to the C:D UNIX port. This could be a health check from a system monitor facility, a hardware load xsqf007i balancer, or something like an FTP Client being mistakenly used to connect to C:D UNIX. e.g. A FTP client trying to connect to C:D port 1364. The TCP session will be http://www-01.ibm.com/support/docview.wss?uid=swg21965534 established ( SYN, SYN+ACK, ACK ) but then the session will hang. This is because the FTP Client is waiting as it expects the next packet to be sent by the FTP Server. The Server side is actually C:D UNIX which is waiting as it is expecting a FMH68 from the Client side. The session ends when the FTP Client times out. http://www-01.ibm.com/support/docview.wss?uid=swg21556234 The message "XIPT016I -TCP lost the connection. System error is Broken pipe." is issued when the timeout occurs. A similar sequence of messages are issued for outbound C:D Secure+ sessions when the remote system has no C:D sessions available. The difference is that there will be TCQ status change messages in the C:D UNIX stats before the XIPT016I and after the XSMG600I. See article NFX9956 for further details. Error Message C:D UNIX stats when non-C:D application attempts to connect to to C:D UNIX port. E XIPT 01/06/2011 16:31:44 ndm_error_set(): rc=16 fdbk=0 msgid=XIPT016I stext=TCP lost the connection. System error is Broken pipe. E XSMG 01/06/2011 16:31:44 ndm_error_set(): rc=8 fdbk=0 msgid=XSMG621I stext=A receive from the remote node operation failed. E XSMG 01/06/2011 16:31:44 ndm_error_set(): rc=16 fdbk=16 msgid=XSMG631I stext=SMGR failed to receive an FMH. Diag=XIPT016I. E XSMG 01/06/2011 16:31:44 ndm_error_set(): rc=16 fdbk=16 msgid=XSMG600I stext=SMGR (snode) didn't receive FMH68 during session start. E CXIT 01/06/2011 16:31:44 Snode SMGR exited. Pid=1200220. Exitcode=0. Messages when outbound session using Secure+ is rejected by remote C:D because no sessions are available (e.g. remote C:D zOS reje
STERLINGPRI Technote (troubleshooting) Problem(Abstract) Snode SMGR Not http://www-01.ibm.com/support/docview.wss?uid=swg21656901 Shutting Down Following Short Network Outage (SCI4099) Symptom XIPT016I Error: TCP lost the connection. System error is &OSMSG. XSMG607I Error: SMGR received an invalid FMH from the remote SMGR. Unable to transfer system error file on restarting transfer following interrupted network connection. Session manager and associated files not shutting down XSMG621I Error: A receive from the remote node operation failed. Cause tcp.max.time.to.wait is set to zero (infinity). This means that, following a glitch system error is in the network connection, the session manager at the Snode is not shutting down. In turn this means that the destination file, which has already been opened for a write, is not closed again. Therefore no subsequent write attempts can succeed. Resolving the problem Set tcp.max.time.to.wait to a value other than zero. Historical Number PRI133 Product Alias/Synonym Fact Connect:Direct UNIX All Releases SCI4099 Document information More support for: Sterling Connect:Direct for UNIX Software version: 3.8, 4.0, 4.1 Operating system(s): AIX, HP-UX, Linux, Solaris Reference #: 1538509 Modified date: 30 July 2012 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
Problem(Abstract) When trying to send from a Windows server to a UNIX server, receiving errors related to the certificates private key. Symptom IBM Sterling Connect:Direct (C:D) for Windows version 4.6.0.2 build 35, displays the error CSPA317E Error loading certificate private key rc 8, fdbk 168 IBM Sterling Connect:Direct for UNIX, version 4.1.0.2, destination server, displays the errors Message ID XIPT016I, rc=16, fdbk=0.|MSST=TCP lost the connection. System error is Broken pipe. Message ID XIPT008I, rc=8, fdbk=0.|MSST=TCP write failed. System error is Error 0. Message ID XSMG623I, rc=8, fdbk=8.|MSST=The send response operation failed. Cause Connect:Direct Windows can not decrypt the private key: CipherSuites: DES-CBC3-SHA cdspssl: SSL_CTX_use_PrivateKey_file err=168, file C:\Program Files\Sterling Commerce\Connect Direct v4.6.00\Server\Secure+\Certificates\keycert2013_copy.txt failed cdspssl: Error queue first 0D0680A8:lib(13):func(104):reason(168) cdspssl: Error queue last 140B0009:lib(20):func(176):reason(9) .. asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag:tasn_dec.c:1002: asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 Type=PKCS8_PRIV_KEY_INFO PKCS12 routines:PKCS12_DECRYPT_D2I:decode error:.\crypto\pkcs12\p12_decr.c:140: PEM routines:PEM_ASN1_read_bio:ASN1 lib:.\crypto\pem\pem_pkey.c:122: SSL routines:SSL_CTX_use_PrivateKey_file:PEM lib:.\ssl\ssl_rsa.c:709: Environment IBM Sterling Connect:Direct for Windows 4.6.02 IBM Connect:Direct for Unix 4.1.02 Resolving the problem 1. Decrypt the key using openssl: # openssl pkcs8 -in /tmp/oldpriv.key -out /tmp/newpriv.rsa Enter Password: # cat /tmp/newpriv.rsa -----BEGIN RSA PRIVATE KEY----- ... -----END RSA PRIVATE KEY----- # 2. Re-encrypt using the following command: openssl pkcs8 -topk8 -v2 des -in /tmp/newpriv.rsa -out /tmp/oldpriv.newkey Enter Encryption Password: Verifying - Enter Encryption Password: 3. Create new Keycert file using new encrypted private key above and existing certificate Document information More support for: Sterling Connect:Direct for