Re: iscsid: connection198:0 is operational after recovery
On 20 Feb 2009 at 11:29, Konrad Rzeszutek wrote: > > On Fri, Feb 20, 2009 at 05:11:24PM +0100, Ulrich Windl wrote: > > > > Hello, > > > > I noticed that I see messages like > > > > Feb 19 01:39:50 rkdvmso1 iscsid: connection198:0 is operational after > > recovery (1 > > attempts) > > > > but no messages telling me that the connection is down (timed out/not > > responding). > > So it's hard to guess when the problem actually occurred. Not knowing the > > sources, > > could it be that the message priority for the failure message (if there is > > any) is > > set too low? > > Try to set 'loglevel=8' on the bootup argument. Also edit /etc/sysconfig/init > and > set the LOG to 8 (if you are using a Red Hat variant of OS). Hi! OK, you are telling me that mesasages are created, but at a lower priority. The issue still is that the failure message should have a higher (or at least equal) priority than the recovery message IMHO. Regards, Ulrich --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsid: connection198:0 is operational after recovery
Hi, I faced this sort of problem on Solaris server.You should check the consistency of your connectivity. For me it was due to the high latency between server and storage.Sometimes latency was getting very high.My server and storage was connected using a nortel switch and there were no separate vlan for the data network. Problem got resolved once I created separate data vlan and changed existing port. Cheers.. Storage Solution Group. --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsid: connection198:0 is operational after recovery
Ulrich Windl wrote: > Hello, > > I noticed that I see messages like > > Feb 19 01:39:50 rkdvmso1 iscsid: connection198:0 is operational after > recovery (1 > attempts) > > but no messages telling me that the connection is down (timed out/not > responding). > So it's hard to guess when the problem actually occurred. Not knowing the > sources, > could it be that the message priority for the failure message (if there is > any) is > set too low? > the iscsid message indicating the failure is the same priority as the one indicating it is up. You should see something about a conn error. You also might see something about a ping or nop timing out. Depending on the versions you are using that might come from the kernel or iscsid. Also, if the kernel had detected the problem then in the kernel logs you should see something about a conn error. --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsid: connection198:0 is operational after recovery
On Fri, Feb 20, 2009 at 05:11:24PM +0100, Ulrich Windl wrote: > > Hello, > > I noticed that I see messages like > > Feb 19 01:39:50 rkdvmso1 iscsid: connection198:0 is operational after > recovery (1 > attempts) > > but no messages telling me that the connection is down (timed out/not > responding). > So it's hard to guess when the problem actually occurred. Not knowing the > sources, > could it be that the message priority for the failure message (if there is > any) is > set too low? Try to set 'loglevel=8' on the bootup argument. Also edit /etc/sysconfig/init and set the LOG to 8 (if you are using a Red Hat variant of OS). --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
iscsid: connection198:0 is operational after recovery
Hello, I noticed that I see messages like Feb 19 01:39:50 rkdvmso1 iscsid: connection198:0 is operational after recovery (1 attempts) but no messages telling me that the connection is down (timed out/not responding). So it's hard to guess when the problem actually occurred. Not knowing the sources, could it be that the message priority for the failure message (if there is any) is set too low? Regards, Ulrich --~--~-~--~~~---~--~~ 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...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
