Re: iscsi connection errors

gen > > Am Freitag, 5. Oktober 2012 23:29:53 UTC+2 schrieb (unbekannt): > >> >> On Oct 5, 2012, at 3:39 PM, squadra wrote: >> >> > Hi, >> > >> > from time to time i see connection errors like this to our equallogic >> 6100xv / 4100e stack

Re: iscsi connection errors

Hello Mike, Am Samstag, 6. Oktober 2012 05:15:11 UTC+2 schrieb Mike Christie: > > On Oct 5, 2012, at 2:39 PM, squadra > > wrote: > > Hi, > > from time to time i see connection errors like this to our equallogic > 6100xv / 4100e stack. > > ct 5 21:22:20 xxx ker

Re: iscsi connection errors

> > from time to time i see connection errors like this to our equallogic > 6100xv / 4100e stack. > > > > ct 5 21:22:20 xxx kernel: connection4:0: detected conn error (1020) > > Oct 5 21:22:21 xxx iscsid: Kernel reported iSCSI connection 4:0 error > (1020 - ISC

Re: iscsi connection errors

server works and the multipath connections are 2 of 2. Some ideas? Best Regards. El viernes, 5 de octubre de 2012 21:39:37 UTC+2, squadra escribió: > > Hi, > > from time to time i see connection errors like this to our equallogic > 6100xv / 4100e stack. > > ct 5 21:22:20 xx

Re: iscsi connection errors

On Oct 5, 2012, at 2:39 PM, squadra wrote: > Hi, > > from time to time i see connection errors like this to our equallogic 6100xv > / 4100e stack. > > ct 5 21:22:20 xxx kernel: connection4:0: detected conn error (1020) Do you see something before this? Maybe somethin

Re: iscsi connection errors

On Oct 5, 2012, at 3:39 PM, squadra wrote: > Hi, > > from time to time i see connection errors like this to our equallogic 6100xv > / 4100e stack. > > ct 5 21:22:20 xxx kernel: connection4:0: detected conn error (1020) > Oct 5 21:22:21 xxx iscsid: Kernel reported iSCSI

iscsi connection errors

Hi, from time to time i see connection errors like this to our equallogic 6100xv / 4100e stack. ct 5 21:22:20 xxx kernel: connection4:0: detected conn error (1020) Oct 5 21:22:21 xxx iscsid: Kernel reported iSCSI connection 4:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed

Re: Need help debugging 1011 connection errors

Just to update this thread... we updated to the latest kernel on this machine and have no other problems as anticipated. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To view this discussion on the web visit https://groups.google.com/d/msg/op

RE: Need help debugging 1011 connection errors

Understood. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@google

Re: Need help debugging 1011 connection errors

On 06/12/2012 12:09 PM, Mike Christie wrote: > On 06/12/2012 11:55 AM, Mike Christie wrote: >> On 06/12/2012 11:45 AM, Mike Christie wrote: >>> On 06/12/2012 11:41 AM, Mike Christie wrote: On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: >> This indicates something went screwy. The

Re: Need help debugging 1011 connection errors

On 06/12/2012 11:55 AM, Mike Christie wrote: > On 06/12/2012 11:45 AM, Mike Christie wrote: >> On 06/12/2012 11:41 AM, Mike Christie wrote: >>> On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: > This indicates something went screwy. The kernel has that el5 string, so > are you using

Re: Need help debugging 1011 connection errors

Awesome. I'll do that and hopefully everything is happy afterward including these random connection issues. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To view this discussion on the web visit https://groups.google.com/d/msg/open-iscsi/-/gr

Re: Need help debugging 1011 connection errors

On 06/12/2012 11:45 AM, Mike Christie wrote: > On 06/12/2012 11:41 AM, Mike Christie wrote: >> On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: This indicates something went screwy. The kernel has that el5 string, so are you using Centos or RHEL? If so what is the iscsi tools vers

Re: Need help debugging 1011 connection errors

On 06/12/2012 11:41 AM, Mike Christie wrote: > On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: >>> This indicates something went screwy. The kernel has that el5 string, so >>> are you using Centos or RHEL? If so what is the iscsi tools version >> >> It is RHEL5 and the tools are as follow

Re: Need help debugging 1011 connection errors

On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote: >> This indicates something went screwy. The kernel has that el5 string, so >> are you using Centos or RHEL? If so what is the iscsi tools version > > It is RHEL5 and the tools are as follows: > > iscsi-initiator-utils-6.2.0.872-13.el5 >

Re: Need help debugging 1011 connection errors

>This indicates something went screwy. The kernel has that el5 string, so >are you using Centos or RHEL? If so what is the iscsi tools version It is RHEL5 and the tools are as follows: iscsi-initiator-utils-6.2.0.872-13.el5 >Is there anything else in the log before or after that? Something abo

Re: Need help debugging 1011 connection errors

On 06/12/2012 11:18 AM, awiddersh...@hotmail.com wrote: > I seem to be getting this over and over again in the logs: > > Jun 12 09:13:40 example-server kernel: connection0:0: iscsi: detected conn > error (1011) 1011 is just a generic error code meaning there was a connection problem. We do not

Need help debugging 1011 connection errors

I seem to be getting this over and over again in the logs: Jun 12 09:13:40 example-server kernel: connection0:0: iscsi: detected conn error (1011) Jun 12 09:13:40 example-server iscsid: Kernel reported iSCSI connection 0:0 error (1011) state (3) Jun 12 09:13:43 example-server iscsid: connection

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

Yeah, I am fine with adding the GPL2 headers. Thanks for the merging. Regards, Aastha. On 4 October 2011 06:44, Mike Christie wrote: > On 09/08/2011 07:23 AM, Ankit Jain wrote: > > On Thu, Sep 8, 2011 at 2:26 PM, Aastha Mehta wrote: > >> Sorry, please ignore the previous patch. There was some

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

On 09/08/2011 07:23 AM, Ankit Jain wrote: > On Thu, Sep 8, 2011 at 2:26 PM, Aastha Mehta wrote: >> Sorry, please ignore the previous patch. There was some minor error in that. >> Re-attaching the patch here. > > +#include > +#include > +#include > +#include "iscsi_if.h" > +#include"kern_error_tab

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

On Thu, Sep 8, 2011 at 2:26 PM, Aastha Mehta wrote: > Sorry, please ignore the previous patch. There was some minor error in that. > Re-attaching the patch here. +#include +#include +#include +#include "iscsi_if.h" +#include"kern_error_table.h" +#define NUM_ERRORS 22 You can probably clean up th

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

On Thu, Sep 8, 2011 at 2:26 PM, Aastha Mehta wrote: > Sorry, please ignore the previous patch. There was some minor error in that. > Re-attaching the patch here. +#include +#include +#include +#include "iscsi_if.h" +#include"kern_error_table.h" +#define NUM_ERRORS 22 You can probably clean up th

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

Sorry, please ignore the previous patch. There was some minor error in that. Re-attaching the patch here. Thanks, Aastha. On 8 September 2011 01:44, Aastha Mehta wrote: > Hi, > > Thanks for the feedback. I have included changes mentioned by different > people. Attaching patch again. Please revi

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

is message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://group

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

On Wed, Aug 31, 2011 at 10:27 PM, Aastha Mehta wrote: > Hello, > > Attached is the patch for the first kernel TODO item in the TODO list > circulated earlier. I could not send the patch through git send-email, so > have attached it here. I'm new to the code base. Some comments inline: >diff --gi

Re: Re: [PATCH 1/1] added code to display verbose messages on session connection errors

Yeah I could do that. On 5 September 2011 18:13, Ulrich Windl wrote: > >>> Aastha Mehta schrieb am 03.09.2011 um 07:50 in > Nachricht > : > > Hi, > > > > Thanks for the suggestions. There is already an enumeration of the error > > codes given in the iscsi_if.h. The #defines cannot use the same n

Antw: Re: [PATCH 1/1] added code to display verbose messages on session connection errors

>>> Aastha Mehta schrieb am 03.09.2011 um 07:50 in >>> Nachricht : > Hi, > > Thanks for the suggestions. There is already an enumeration of the error > codes given in the iscsi_if.h. The #defines cannot use the same names, but > it can be done with slightly different names. > So I shall modify t

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

Before I patch again, would like to show you the files. Have added a default case in the err_code_to_string() function. Also removed the extra err_string variable I used previously in the function. Each case now directly returns the appropriate message from the table directly, as no other work is d

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

Hi, I have not done any changes to prom_lex.c. The diff shows something because of difference in the two git sources downloaded. How do I drop the changes? Will git diff --check suffice? Please confirm if I should #define the error messages or not. If yes, will macro name pattern like M_ISCSI_ERR_

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

On 08/31/2011 11:57 AM, Aastha Mehta wrote: > Hello, > > Attached is the patch for the first kernel TODO item in the TODO list > circulated earlier. I could not send the patch through git send-email, so > have attached it here. > > Thanks, > Aastha. > - You do not need the changes to a/utils/fw

Re: [PATCH 1/1] added code to display verbose messages on session connection errors

Hi, Thanks for the suggestions. There is already an enumeration of the error codes given in the iscsi_if.h. The #defines cannot use the same names, but it can be done with slightly different names. So I shall modify the following things in the code - 1. #define the error messages and use those 2.

Antw: [PATCH 1/1] added code to display verbose messages on session connection errors

>>> Aastha Mehta schrieb am 31.08.2011 um 18:57 in >>> Nachricht : > Hello, > > Attached is the patch for the first kernel TODO item in the TODO list > circulated earlier. I could not send the patch through git send-email, so > have attached it here. Hi! Why not having "char *err_table[NUM_ERR

[PATCH 1/1] added code to display verbose messages on session connection errors

google.com/group/open-iscsi?hl=en. From ef75092e47544e126b259114ce87cdf395ca3d9d Mon Sep 17 00:00:00 2001 From: Aastha Mehta Date: Mon, 29 Aug 2011 10:18:17 -0700 Subject: [PATCH 1/1] added code to display verbose messages on session connection errors --- usr/Makefile |

Re: iSCSI connection errors with SLES10 SP3 update

On 12/20/2010 09:56 AM, Hannes Reinecke wrote: > Hi all, > > I just noticed that I've botched up header digests with the latest > update for SLES10 SP3. So if you got trouble connecting and get > loads of 'iscsi: detected conn error (1011)' please switch off > header digests. > > I'm working on f

iSCSI connection errors with SLES10 SP3 update

Hi all, I just noticed that I've botched up header digests with the latest update for SLES10 SP3. So if you got trouble connecting and get loads of 'iscsi: detected conn error (1011)' please switch off header digests. I'm working on fixing this and will let you know once the issue is fixed. Sorr

Re: iscsi timeouts and connection errors

Oops, I should have added, in our testing, disabling the conn- balancing made no difference with respect to throughput/IO numbers... On May 26, 10:00 am, Taylor wrote: > FYI, to disbale connection load balancing on equallogics, you run... > > Login into the array as grpadmin; at the CLI> prompt,

Re: iscsi timeouts and connection errors

FYI, to disbale connection load balancing on equallogics, you run... Login into the array as grpadmin; at the CLI> prompt, type this command: CLI> grpparams conn-balancing disable This command can be done w/o a reboot or restart of the arrays and becomes effective immediately on all members in t

Re: iscsi timeouts and connection errors

Thanks for the suggestions, I did change the io scheduler to make sure it was same as other server we were testing on. Not using iptables, and cpu frequency scaling or whatever its called is not enabled. To us this looks like an issue with worse network performance with later kernels. The kernel

Re: iscsi timeouts and connection errors

On 05/25/2010 04:15 PM, Taylor wrote: So far blowing away SUSE 11 and installing OpenSuse has resolved the Just so you know , the SUSE developers are good at keeping SLES up to date and even have fixes that are not yet upstream, so it is sometimes best to just get their newest SLES kernels.

Re: iscsi timeouts and connection errors

So far blowing away SUSE 11 and installing OpenSuse has resolved the problem, however, throughput numbers have dropped by about half. We were getting nearly 5 Gbit /sec when testing across 5 LUNs, now we are getting more like 2.6 Gbit/sec, but we've had no disconnect errors. Now the question is,

Re: iscsi timeouts and connection errors

On 05/25/2010 03:01 PM, Taylor Lewick wrote: Ok, will find out about the equallogic setting. So if we are using dm-multipath, we should not set those noop values to 0, but possibly increase them for high IO loads? Yes, but set them lower than your scsi command timeout (/sys//block/sdX/device

Re: iscsi timeouts and connection errors

Ok, will find out about the equallogic setting. So if we are using dm-multipath, we should not set those noop values to 0, but possibly increase them for high IO loads? On Tue, May 25, 2010 at 2:47 PM, Mike Christie wrote: > On 05/24/2010 11:22 PM, Taylor wrote: >> >> Yes, when I get to office t

Re: iscsi timeouts and connection errors

On 05/24/2010 11:22 PM, Taylor wrote: Yes, when I get to office tomorrow I can attach screen output of make fail, as well as support info with equallogic. I guess to a different point, I understand if we are just killing the disk that can cause problems, but how can I set it up so that IO is slo

Re: iscsi timeouts and connection errors

Yeah, and netstat -in does show a few RX-ERR on the two 10 Gig NICs we are connecting to the iSCSI san with. So I don't know if thats because of the extremely high IO load. i.e., iostat is reporting 600,000 Kbytes/sec in writes across 4 LUNs during our heavy testing. -- You received this message

Re: iscsi timeouts and connection errors

Here is the output of the make, showing the compile completed for the iscsi binaries, but failed for kernel code... Compilation complete Output file --- Built iSCSI daemon: usr/iscsid Built management application:

Re: iscsi timeouts and connection errors

On 24 May 2010 at 9:06, Taylor wrote: > Adjusting node.conn[0].timeo.noop_out_interval and > node.conn[0].timeo.noop_out_timeout to 0 > didn't seem to make a difference. But increasing the value of /sys/ > block/sd#/device/timeout from 30 to a higher number, like 360, seems > to have improved thi

Re: iscsi timeouts and connection errors

Yes, when I get to office tomorrow I can attach screen output of make fail, as well as support info with equallogic. I guess to a different point, I understand if we are just killing the disk that can cause problems, but how can I set it up so that IO is slow or queues, and doesn't cause disconnec

Re: iscsi timeouts and connection errors

Hey, We actually have a good relationship with EQL/Dell. Could you give me your support number for the issue and who you worked with? I will contact some of the support people we work with and get more info directly. On 05/24/2010 10:17 PM, Mike Christie wrote: Called equallogic, and they s

Re: iscsi timeouts and connection errors

(3)" messages. do you see those messages and the "Target requests logout within 3 seconds for connection" errors or just the 1011 message? After that message do you see something about a host or target reset? We are running tests on 3 to 4o filesystems where we loop and

Re: iscsi timeouts and connection errors

Mike and all, okay, noted about the ping timeout messages. I set both of those values by running: iscsiadm --mode node --o update -n node.conn[0].timeo.noop_out_interval -v 10 iscsiadm --mode node --o update -n node.conn[0].timeo.noop_out_timeout -v 10 I verifed the settings took via iscsiadm --

Re: iscsi timeouts and connection errors

On 05/24/2010 11:06 AM, Taylor wrote: Adjusting node.conn[0].timeo.noop_out_interval and node.conn[0].timeo.noop_out_timeout to 0 didn't seem to make a difference. But increasing the value of /sys/ If it did not make a difference then it might not have got set right. If you set them to 0, the

Re: iscsi timeouts and connection errors

Adjusting node.conn[0].timeo.noop_out_interval and node.conn[0].timeo.noop_out_timeout to 0 didn't seem to make a difference. But increasing the value of /sys/ block/sd#/device/timeout from 30 to a higher number, like 360, seems to have improved things... Is that something you would expect? Do y

Re: iscsi timeouts and connection errors

Mike, thanks for the reply. The first line in the log i posted shows the ping timeout. Or were you wanting to see something else? Let me know what specifically you are looking for. Yes we are using multipath, I can post multipath.conf if that helps. I tried tweaking various settings in iscisd.c

Re: iscsi timeouts and connection errors

On 05/21/2010 03:43 PM, Taylor wrote: We have a SLES 11 server connected to an Equallogic 10 Gig disk array. Initially everything seemed to work just fine. When doing some IO testing against the mounted volumes, in which we cause very high IO loads, i.e. 95 to 100% as reported by iostat, we sta

iscsi timeouts and connection errors

fload parameters on the iscsi NICs, and adjusting iscsid.conf timeouts. We are running a 2.6.27 kernel with open-iscsi 2.0.870-26.5. Does anyone have any suggestions on how we can avoide these timeouts and connection errors? -- You received this message because you are subscribed to the Google G

Re: connection errors centos 5.2

On 02/24/2010 03:49 PM, Murray wrote: On Feb 24, 2:19 pm, Mike Christie wrote: On 02/23/2010 02:04 PM, Jonathan Murray wrote: after about 24 hours, we see the following in /var/log/messages (not in order) iscsid: connect failed (111) iscsi: cmd 0x28 is not queued (8) iscsi: cmd 0x2a is n

Re: connection errors centos 5.2

On Feb 24, 2:19 pm, Mike Christie wrote: > On 02/23/2010 02:04 PM, Jonathan Murray wrote: > > > after about 24 hours, we see the following in /var/log/messages (not in > > order) > > > iscsid: connect failed (111) > > iscsi: cmd 0x28 is not queued (8) > > iscsi: cmd 0x2a is not queued (8) > > is

Re: connection errors centos 5.2

On Feb 24, 2:19 pm, Mike Christie wrote: > On 02/23/2010 02:04 PM, Jonathan Murray wrote: > > > after about 24 hours, we see the following in /var/log/messages (not in > > order) > > > iscsid: connect failed (111) > > iscsi: cmd 0x28 is not queued (8) > > iscsi: cmd 0x2a is not queued (8) > > is

Re: connection errors centos 5.2

On 02/23/2010 02:04 PM, Jonathan Murray wrote: after about 24 hours, we see the following in /var/log/messages (not in order) iscsid: connect failed (111) iscsi: cmd 0x28 is not queued (8) iscsi: cmd 0x2a is not queued (8) iscsi: detected conn error (1011) Kernel reported iSCSI connection 1:0 e

Re: connection errors centos 5.2

We've run into some issues in the past with iSCSI disconnects. As an FYI, one thing that has helped is is to put dm-multipath in the middle and add another iface. This allows one path to fail and you still get access to the device. I know it doesn't necessarily answer your question, but may h

connection errors centos 5.2

I am using iscsi to connect a Centos 5.2 server to a Promise Tech Vtrak M610i On the linux box, I have iscsi-initiator-utils-6.2.0.868-0.18.el5 2.6.18-92.1.13.el5.centos.plus #1 SMP Wed Oct 1 13:41:35 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux The Promise array is on a separate subnet from the

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > Evan Broder wrote: >> Evan Broder wrote: >>> Just got another round of failures with the new debugging patch in. >>> Traffic dump at >>> , >>> syslog (including the kernel log) at >>>

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Evan Broder wrote: >> Just got another round of failures with the new debugging patch in. >> Traffic dump at >> , >> syslog (including the kernel log) at >>

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Just got another round of failures with the new debugging patch in. > Traffic dump at > , > syslog (including the kernel log) at >

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: Could you also run with this patch? In the open-iscsi source do patch -p1 -i path-to-patch/remove-undef-tcp.patch then rebuild with make DEBUG_TCP=1 DEBUG_SCSI=1 make DEBUG_TCP=1 DEBUG_SCSI=1 install > I'll hopefully have a l

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > I think wiresharp/ethereal will spit out the data in the packets by > default and I am not sure of a way to ask it to drop the data and just > send the packet info. Ok - sorry for taking a while in getting this collected. I have a tcpdump from one of the failures at

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > > Incidentally, to what extent is user data exposed in the dump? I've > asked some friends to let me run their VMs on citadel-station to try and > increase the probability of an incident occurring, but they presumably > wouldn't appreciate me sending out logs if data from thei

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > Are you doing iscsi root? iscsid is running as root - is that what you mean? > How do you know they become unresponsive? Do you have a ssh session > and at this time you cannot contact the vm or do you have a console on > the vm and at that time you cannot run any commands

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Evan Broder wrote: >> Ok - I'm running a few of my VMs, and setup some simple monitoring to >> let me know if an error gets logged. I'll get back to the list if/when I >> find anything. >> >> - Evan > > I'm no longer seeing the "detected conn error", but I am still seeing > th

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Ok - I'm running a few of my VMs, and setup some simple monitoring to > let me know if an error gets logged. I'll get back to the list if/when I > find anything. > > - Evan I'm no longer seeing the "detected conn error", but I am still seeing the symptoms of the problems: on

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > Not with just the above info. I t could be happening for a variety of > reasons. > > It looks like the target is either disconnecting us (this is why I was > looking for a TCP_CLOSE in the debug output) because we goofed on some > iscsi protocol issue but normally I would

Re: Frequent Connection Errors with Dell Equallogic RAID

a reliable way of generating the errors. They > don't seem to happen when there's no iSCSI traffic, but they also didn't > occur when we ran a program that generates rapid, random reads and writes. > > I'd rather not put production VMs on this server while we're test

Re: Frequent Connection Errors with Dell Equallogic RAID

;t occur when we ran a program that generates rapid, random reads and writes. I'd rather not put production VMs on this server while we're testing. Do you have any theories on how we could trigger these connection errors, if they're still occurring? - Evan --~--~-~--~---

Re: Frequent Connection Errors with Dell Equallogic RAID

tal os 10.5.128.128 on Evan> all four servers, and the current portal is 10.5.128.129 on all Evan> servers. It doesn't change after one of the connection errors. That suggests the load balancer is not involved here. You might check the event logs on the array to see if t

Re: Frequent Connection Errors with Dell Equallogic RAID

zhaoyuqiang wrote: > Hi, > Someone solved the issue like this with running opensuse10.3. you can > try download source code from > http://www.open-iscsi.org/bits/open-iscsi-2.0-865.13.tar.gz > and > complie for Ubuntu, it's like scsi_tr

Re: Frequent Connection Errors with Dell Equallogic RAID

Ulrich Windl wrote: > On 8 Dec 2008 at 17:52, Pasi Kärkkäinen wrote: > >> iscsiadm -m session -P3 >> > > Hi, > > being curious: My version if iscsiadm (version 2.0-754) doesn't know about > the "- > P3". What ist it expected to do? > In older versions you might be able to do iscsiadm -m ses

Re: Frequent Connection Errors with Dell Equallogic RAID

our servers on a dedicated storage network. We've been regularly > experiencing connection errors: > > Dec 8 00:50:36 aperture-science kernel: [1010621.595904] > connection1:0: iscsi: detected conn error (1011) > Dec 8 00:50:37 aperture-science iscsid: Kernel reported iSCSI > con

Re: Frequent Connection Errors with Dell Equallogic RAID

On Wed, Dec 10, 2008 at 12:45:04PM +0100, Ulrich Windl wrote: > > On 8 Dec 2008 at 17:52, Pasi Kärkkäinen wrote: > > > iscsiadm -m session -P3 > > > > Hi, > > being curious: My version if iscsiadm (version 2.0-754) doesn't know about > the "- > P3". What ist it expected to do? > It just pr

Re: Frequent Connection Errors with Dell Equallogic RAID

On 8 Dec 2008 at 17:52, Pasi Kärkkäinen wrote: > iscsiadm -m session -P3 > Hi, being curious: My version if iscsiadm (version 2.0-754) doesn't know about the "- P3". What ist it expected to do? Regards, Ulrich --~--~-~--~~~---~--~~ You received this message

Re: Frequent Connection Errors with Dell Equallogic RAID

Hello, I would strongly suggest using the code version Mike mentioned. I use ubuntu 8.04/8.10 with that code without issues w/EQL arrays. Running the older transport kernel module has caused NOOP errors. The initiator sends out NOOPs w/different SN numbers than what the array is expecting. Up

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > > If you can play around on the box, it would be helpful to run the > open-iscsi tarball release. Build it with Oh yeah that is here: http://www.open-iscsi.org/bits/open-iscsi-2.0-870.1.tar.gz --~--~-~--~~~---~--~~ You received this messag

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Mike Christie wrote: >> Is the only log error that bit about: >> >> iqn.2001-05.com.equallogic:0-8a0906-2b6e7d402-891497db5ca48925-xvm-volume-1' >> >> from initiator '10.5.128.16:53712, iqn >> 1993-08.org.debian:01:bce099ff4d44' was closed. > Yeah, that's the only thing that e

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > Is the only log error that bit about: > > iqn.2001-05.com.equallogic:0-8a0906-2b6e7d402-891497db5ca48925-xvm-volume-1' > > from initiator '10.5.128.16:53712, iqn > 1993-08.org.debian:01:bce099ff4d44' was closed. Yeah, that's the only thing that ever shows up. It's immediatel

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Pasi Kärkkäinen wrote: >> On Mon, Dec 08, 2008 at 02:57:44PM -0500, Evan Broder wrote: >> >>> Yeah. Our storage network is completely isolated, so we thought about >>> trying to disable CHAP, but we couldn't find an option to turn it off in >>> the Equallogic config. >>> >>

Re: Frequent Connection Errors with Dell Equallogic RAID

Pasi Kärkkäinen wrote: > On Mon, Dec 08, 2008 at 02:57:44PM -0500, Evan Broder wrote: > >> Yeah. Our storage network is completely isolated, so we thought about >> trying to disable CHAP, but we couldn't find an option to turn it off in >> the Equallogic config. >> >> > > In your volume pr

Re: Frequent Connection Errors with Dell Equallogic RAID

Paul Koning wrote: > You might check the event logs on the array to see if there are any > messages there around the same time. > >paul > > There isn't anything. There's a message for the disconnect, and a message for the reconnect. - Evan --~--~-~--~~~--

Re: Frequent Connection Errors with Dell Equallogic RAID

On Mon, Dec 08, 2008 at 02:57:44PM -0500, Evan Broder wrote: > > Mike Christie wrote: > > Evan Broder wrote: > >> A group I work with is currently using a Dell Equallogic RAID with > >> four servers on a dedicated storage network. We've been regularly

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > Mike Christie wrote: >> Evan Broder wrote: >>> A group I work with is currently using a Dell Equallogic RAID with >>> four servers on a dedicated storage network. We've been regularly >>> experiencing connection errors: >&g

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > Evan Broder wrote: >> A group I work with is currently using a Dell Equallogic RAID with >> four servers on a dedicated storage network. We've been regularly >> experiencing connection errors: >> >> Dec 8 00:50:36 aperture-science ker

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: > A group I work with is currently using a Dell Equallogic RAID with > four servers on a dedicated storage network. We've been regularly > experiencing connection errors: > > Dec 8 00:50:36 aperture-science kernel: [1010621.595904] > connection1:0: isc

Re: Frequent Connection Errors with Dell Equallogic RAID

Pasi Kärkkäinen wrote: > On Mon, Dec 08, 2008 at 05:48:22AM -0800, Evan Broder wrote: > >> A group I work with is currently using a Dell Equallogic RAID with >> four servers on a dedicated storage network. We've been regularly >> experiencing connection errors: &

Re: Frequent Connection Errors with Dell Equallogic RAID

Mike Christie wrote: > Evan Broder wrote: > #define ISCSI_TRANSPORT_VERSION "2.0-724" >> >> The userspace utilities are 2.0.865. >> > > Are these the Ubuntu tools or did you get them from open-iscsi.org? If > they are ubuntu ones is there more version info on the ubuntu package? > What is the

Re: Frequent Connection Errors with Dell Equallogic RAID

Evan Broder wrote: >>> #define ISCSI_TRANSPORT_VERSION "2.0-724" > > The userspace utilities are 2.0.865. > Are these the Ubuntu tools or did you get them from open-iscsi.org? If they are ubuntu ones is there more version info on the ubuntu package? What is the iscsi package named in ubuntu

Re: Frequent Connection Errors with Dell Equallogic RAID

On Mon, Dec 08, 2008 at 05:48:22AM -0800, Evan Broder wrote: > > A group I work with is currently using a Dell Equallogic RAID with > four servers on a dedicated storage network. We've been regularly > experiencing connection errors: > > Dec 8 00:50:36 aperture-science

Frequent Connection Errors with Dell Equallogic RAID

A group I work with is currently using a Dell Equallogic RAID with four servers on a dedicated storage network. We've been regularly experiencing connection errors: Dec 8 00:50:36 aperture-science kernel: [1010621.595904] connection1:0: iscsi: detected conn error (1011) Dec 8 00:50:37 ape

Re: Connection Errors

On Thu, Jul 03, 2008 at 02:33:02PM -0700, swejis wrote: > > > > Looks like a tcp-reset was received ? Would it help if I start the > > > initiator by hand and increased debug-level ? > > > > No. It looks like the target dropped the connection on us. Did you see > > anything on the target logs? >

Re: Connection Errors

> > Looks like a tcp-reset was received ? Would it help if I start the > > initiator by hand and increased debug-level ? > > No. It looks like the target dropped the connection on us. Did you see > anything on the target logs? I am afraid not, this target unfortunately leaves much to wish for, a

Re: Connection Errors

swejis wrote: > I increased the I/O on the initiator yesterday by placing the LUN > holding our mySQL database on this server. Everything looks 'quite' > well part from the error I got this morning. All nop time out set to > zero. > > Jul 1 07:15:23 manjula syslog-ng[17906]: STATS: dropped 0 > J

Re: Connection Errors

I increased the I/O on the initiator yesterday by placing the LUN holding our mySQL database on this server. Everything looks 'quite' well part from the error I got this morning. All nop time out set to zero. Jul 1 07:15:23 manjula syslog-ng[17906]: STATS: dropped 0 Jul 1 07:20:38 manjula kerne

Re: Connection Errors

Yet again I must have done something wrong since I was unable to set the timeout values to zero. Yesterday I removed all "saved data" meaning the nodes and send_targets directory from /etc/isci and reran the discovery, now the values where indeed set. I did this yesterday on two machines (one 64 a

  1   2   >