On 08/05/2016 07:34 PM, [email protected] wrote: > Hello All, > > I'm seeing these messages in my messages log, as well as experiencing > corosync problems around the same time. I have searched high and low > for information on this error code and have found very little. > > From /var/log/messages: > iscsid: Kernel reported iSCSI connection 1:0 error (1022 - Invalid or > unknown error code) state (3) > iscsid: connection1:0 is operational after recovery (1 attempts) > iscsid: Kernel reported iSCSI connection 1:0 error (1022 - Invalid or > unknown error code) state (3) > iscsid: connection1:0 is operational after recovery (1 attempts)
Is there also something about a iscsi ping timing out in the initiator kernel log? Something like: "ping timeout of %d secs expired" ? > > The system is CentOS 7.2, running iscsi-initiator-utils-6.2.0.873-32. > I'm connecting to a QNAP TurboNAS 869 as the target. The target isn't > logging any sort of error messages that can help in the debugging of the > issue. > I did have Jumbo Frames enabled on the switch and set MTU to 9000 on the > initiators and the target, but set everything back to 1500 after > problems began with no discernible effect. > > If anyone could provide some insight as to why I'm seeing those messages > and how to correct the problem, I would appreciate it greatly. > > Thank you for your time. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
