QNAP: Connection dropped after 10 minutes

[pierrezerbib]

Two connexion with iscsi 4 stop after 10mn.

This connexion is with Qnap 4.10

I look in log, but no information

[pierrezerbib]

Trace of log
Nov 23 12:49:50 iMac-de-pierre kernel[0]: iscsi: Task timeout for task 0x1ac33840 (sid: 0, cid: 0)
Nov 23 12:49:50 iMac-de-pierre kernel[0]: iscsi: Starting task 0x274ef4e0 (sid: 0, cid: 0)
Nov 23 12:49:50 iMac-de-pierre kernel[0]: iscsi: Sent PDU type 0x1 (sid: 0, cid: 0)
Nov 23 12:50:10 iMac-de-pierre kernel[0]: iscsi: Task timeout for task 0x274ef4e0 (sid: 0, cid: 0)
Nov 23 12:50:10 iMac-de-pierre kernel[0]: iscsi: Connection timeout (sid: 0, cid: 0)
Nov 23 12:50:10 iMac-de-pierre kernel[0]: iscsi: Deactivated connection (sid: 0, cid: 0)
Nov 23 12:50:10 iMac-de-pierre kernel[0]: iscsi: Releasing session (sid 0)
Nov 23 12:50:10 iMac-de-pierre kernel[0]: iscsi: Removed event sources (sid: 0, cid: 0)
Nov 23 12:50:10 iMac-de-pierre kernel[0]: iscsi: Released connection (sid: 0, cid: 0)
Nov 23 12:50:10 iMac-de-pierre iscsid[2325]: TCP timeout for iqn.2004-04.com.qnap:ts-410:iscsi.imac2.c4bb1a over portal 192.168.111.152.

[pierrezerbib]

Why a tcp timeout, is it normal

[nsinenian]

There is a task timeout, which means that the initiator sent a command and received no response from the target. To better understand the problem, I will need you to capture TCP traffic between your machine and the target. You can do this using WireShark (www.wireshark.com). Please save the log and post it here. You should start logging before login, and stop logging after you see the TCP timeout.

[pierrezerbib]

This is a capture
iscsi.pcapng.zip

[nsinenian]

Try the attached version (rename ZIP to DMG and install normally):
iSCSIInitiator-1.0.0-beta4++.zip

[Muthuramane]

@nsinenian: In the trace log, I seen the host sending the SCSI command opcode 0x1b(Start Stop Unit) for LUN0 but target respond as Reject(Reason: Invalid PDU field) to the host. To refer Frames 2735, 2736.
In Frame 2738, the target responded as FIN & ACK which means target closed the session but host initiator doesn't send FIN, ACK to target and also host sending the TUR to target in frame2762.

In Frame 2763, the target responded [RST] to the host.

We have to take look at
Why target responded as REJECT for opcode 0x1b?
Why host didn't close the session after receiving the FIN, ACK from target?

@pierrezerbib : Could you please collect target side log and look whether target supports SSU(0x1b) or not.

[nsinenian]

It has to do with the R/W flag set in the PDU that should have not been set. The new build I posted here changes that, and that's what I wanted Pierre to try out.

…

On Fri, Dec 16, 2016 at 5:15 PM, Muthuraman Elangovan < ***@***.***> wrote: @nsinenian <https://github.com/nsinenian>: In the trace log, I seen the host sending the SCSI command opcode 0x1b(Start Stop Unit) for LUN0 but target respond as Reject(Reason: Invalid PDU field) to the host. To refer Frames 2735, 2736. In Frame 2738, the target responded as FIN & ACK which means target closed the session but host initiator doesn't send FIN, ACK to target and also host sending the TUR to target in frame2762. In Frame 2763, the target responded [RST] to the host. We have to take look at Why target responded as REJECT for opcode 0x1b? Why host didn't close the session after receiving the FIN, ACK from target? @pierrezerbib <https://github.com/pierrezerbib> : Could you please collect target side log and look whether target supports SSU(0x1b) or not. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEH_QxKcPyV3qQjnNvdDiX1eKtRLx25dks5rIlbPgaJpZM4K6eP5> .

[nsinenian]

@pierrezerbib Did BETA-5 fix your problem? Please let me know.

[pierrezerbib]

where is possible to download Beta-5 ?

[nsinenian]

Same as all other BETA releases, under the releases page on GitHub: https://github.com/iscsi-osx/iSCSIInitiator/releases

[pierrezerbib]

Hi, it’s good actually. Only Osx tell iscis down , but iscis up

…

Le 4 mars 2017 à 02:19, Nareg Sinenian ***@***.***> a écrit : Same as all other BETA releases, under the releases page on GitHub: https://github.com/iscsi-osx/iSCSIInitiator/releases <https://github.com/iscsi-osx/iSCSIInitiator/releases> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWmaKlylkU8XQHgBe19pOaQyP7wBrptAks5riLwHgaJpZM4K6eP5>.

[nsinenian]

I don't know what your second sentence means. Does it work, or not?

[pierrezerbib]

Sorry my english is bad. My system indicates me that the iscsi record(disk) is to fall, but it is always and works

…

Le 4 mars 2017 à 12:50, Nareg Sinenian ***@***.***> a écrit : I don't know what your second sentence means. Does it work, or not? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWmaKtc1so_oeCMzIe5Y1Np9cYbbb8k-ks5riVADgaJpZM4K6eP5>.

[nsinenian]

No problem, thanks your testing and support.

[pierrezerbib]

Sorry I have an another problems, Actually on mac-mini El-capitan , iscsctl permission denied ?

…

Le 4 mars 2017 à 02:19, Nareg Sinenian ***@***.***> a écrit : Same as all other BETA releases, under the releases page on GitHub: https://github.com/iscsi-osx/iSCSIInitiator/releases <https://github.com/iscsi-osx/iSCSIInitiator/releases> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#76 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWmaKlylkU8XQHgBe19pOaQyP7wBrptAks5riLwHgaJpZM4K6eP5>.