Proxmox VE iSCSI strange log on Synology Storage

302 views
Skip to first unread message

juniper

unread,
Jan 31, 2018, 1:25:11 PM1/31/18
to open-iscsi
Hi,

i have a cluster of 5 server connected (iSCSI) with a Synology RS3617xs+ (10GBE interface);

all seems working fine but on Synology i have some strange log:

continuous:

2018-01-31T18:39:33+01:00 mksyn kernel: iscsi_target_parameters.c:44:iscsi_login_rx_data rx_data returned 0, expecting 48.
2018-01-31T18:39:35+01:00 mksyn kernel: iscsi_target_parameters.c:44:iscsi_login_rx_data rx_data returned 0, expecting 48.
2018-01-31T18:39:35+01:00 mksyn kernel: iscsi_target_parameters.c:44:iscsi_login_rx_data rx_data returned 0, expecting 48.
2018-01-31T18:40:05+01:00 mksyn kernel: SYSTEM:    Last message 'iscsi_target_paramet' repeated 15 times, suppressed by syslog-ng on mksyn
2018-01-31T18:40:05+01:00 mksyn kernel: iscsi_target_parameters.c:44:iscsi_login_rx_data rx_data returned 0, expecting 48.
2018-01-31T18:40:05+01:00 mksyn kernel: iscsi_target_parameters.c:44:iscsi_login_rx_data rx_data returned 0, expecting 48.
2018-01-31T18:40:09+01:00 mksyn kernel: iscsi_target_parameters.c:44:iscsi_login_rx_data rx_data returned 0, expecting 48.

and

2018-01-31T18:42:55+01:00 mksyn kernel: [121563.213710] iSCSI_F:iscsi_target_login.c:1213:iscsi_target_login_sess_out iSCSI Login negotiation failed - I[10.10.200.153:48182], T[]
2018-01-31T18:42:58+01:00 mksyn kernel: [121566.126965] iSCSI_F:iscsi_target_login.c:1213:iscsi_target_login_sess_out iSCSI Login negotiation failed - I[10.10.200.154:34932], T[]
2018-01-31T18:42:59+01:00 mksyn kernel: [121567.084450] iSCSI_F:iscsi_target_login.c:1213:iscsi_target_login_sess_out iSCSI Login negotiation failed - I[10.10.200.151:43236], T[]
2018-01-31T18:43:03+01:00 mksyn kernel: [121570.732065] iSCSI_F:iscsi_target_login.c:1213:iscsi_target_login_sess_out iSCSI Login negotiation failed - I[10.10.200.150:51542], T[]
2018-01-31T18:43:05+01:00 mksyn kernel: [121573.008544] iSCSI_F:iscsi_target_login.c:1213:iscsi_target_login_sess_out iSCSI Login negotiation failed - I[10.10.200.152:42280], T[]
2018-01-31T18:43:05+01:00 mksyn kernel: [121573.342183] iSCSI_F:iscsi_target_login.c:1213:iscsi_target_login_sess_out iSCSI Login negotiation failed - I[10.10.200.153:48186], T[]

Do you have some hints about? I contacted Synology Support but without any results...

The Lee-Man

unread,
Feb 1, 2018, 2:20:26 PM2/1/18
to open-iscsi

Are you using CHAP? Is it set up correctly? If you are using CHAP I suggest disabling it (on both sides) and trying again?

The "Login negotiation failed" message looks customized but is coming from iscsi_target_login_sess_out(), which is only called when a login fails. That's likely because the login is failing to read the ISCSI header (which is 48 bytes), as noted by the "rx_data return 0, expecting 48" message. So the login is failing at the initial ISCSI Header phase.

Has something occurred, like systems or the target rebooting?
 

Franz Angeli

unread,
Feb 1, 2018, 2:29:11 PM2/1/18
to open-...@googlegroups.com
No I don't use authentication at all and all works fine, I have only tons of this logs.. 

Tomorrow I'll try to trace some sessions (tcpdump) trying to debug what happens. 



--
You received this message because you are subscribed to a topic in the Google Groups "open-iscsi" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-iscsi/1J_Z0hdRc2g/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-iscsi+unsubscribe@googlegroups.com.
To post to this group, send email to open-...@googlegroups.com.
Visit this group at https://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.

juniper

unread,
Feb 2, 2018, 3:21:16 AM2/2/18
to open-iscsi
is possible that "TARGET_THREAD_SET_COUNT" set to 4 by module is too low considering i have 5 cluster node accessing to Synology Storage?

The Lee-Man

unread,
Feb 4, 2018, 4:21:21 PM2/4/18
to open-iscsi
On Friday, February 2, 2018 at 12:21:16 AM UTC-8, juniper wrote:
is possible that "TARGET_THREAD_SET_COUNT" set to 4 by module is too low considering i have 5 cluster node accessing to Synology Storage?

Please feel free to try increasing that number -- I have no idea if it will help or not -- but I suspect that isn't the issue.
Reply all
Reply to author
Forward
0 new messages