1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed
This document (000020752) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise High Availability Extension 15 SP4
Situation
The systemd journal, by default also written to /var/log/messages, fills with similar messages when an iSCSI LUN is shared across multiple nodes.
Sep 07 10:42:32 alpha kernel: connection1:0: detected conn error (1020)
Sep 07 10:42:32 alpha iscsid[1373]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Sep 07 10:42:35 beta kernel: connection1:0: detected conn error (1020)
Sep 07 10:42:35 beta iscsid[1454]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Sep 07 10:42:32 alpha kernel: connection1:0: detected conn error (1020)
Sep 07 10:42:32 alpha iscsid[1373]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Sep 07 10:42:35 beta kernel: connection1:0: detected conn error (1020)
Sep 07 10:42:35 beta iscsid[1454]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (3)
Resolution
Check affected nodes for identical InitiatorName values in /etc/iscsi/initiatorname.iscsi.
If identical, a new InitiatorName can be generated with:
/sbin/iscsi-gen-initiatorname -f
The nodes can then be restarted appropriately to ensure that everything comes back up correctly.
If identical, a new InitiatorName can be generated with:
/sbin/iscsi-gen-initiatorname -f
The nodes can then be restarted appropriately to ensure that everything comes back up correctly.
Cause
These error messages are often indicative of non unique iSCSI initiator names being used across amongst nodes accessing the same LUN.
Specifically for SLES 15 SP4 with the release of SUSE-RU-2022:2300-1 the iSCSI InitiatorName is created on rpm installation rather than on first start of the iSCSI initiator.
This change was implemented for cases where root is read-only at startup time.
Specifically for SLES 15 SP4 with the release of SUSE-RU-2022:2300-1 the iSCSI InitiatorName is created on rpm installation rather than on first start of the iSCSI initiator.
This change was implemented for cases where root is read-only at startup time.
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020752
- Creation Date: 08-Sep-2022
- Modified Date:08-Sep-2022
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
