Hi Mike,
First my apologies for a late reply. I have resolved this issue. I
changed the install locations and it worked. Earlier i tried shared
home install. Basically, i had a shared oracle home and tried to
install the oracle software (binaries) to be shared by both nodes. But
later i installed the oracle softwares separate on both the nodes and
they worked fine. Appreciate your sincere efforts to help noobs like
me.

On Thu, Jun 11, 2009 at 1:02 PM, Mike Christie<micha...@cs.wisc.edu> wrote:
>
> On 06/10/2009 10:49 AM, sundar mahadevan wrote:
>> Hi Members,
>> First of all, I'm not too sure if this question is supposed to raise
>> here. Sorry if this is not the right place. Appreciate if you could
>> direct me to the right place. Thanks.
>>
>> OS: Oracle enterprise linux
>> rpm -qa | grep -i scsi
>>
>> scsi-target-utils-0.0-5.20080917snap.el5
>> iscsi-initiator-utils-6.2.0.868-0.18.el5
>>
>
> what kernel are you using (do uname -a)?
>
>> I'm trying to install oracle 9i rac. During instllation half way
>> through, i receive the following error messages. I encountered this
>> problem twice. In fact on the second attempt, the connection got
>> dropped at 10:54 and then somehow reconnected itself in a few seconds.
>> But later the connection dropped and did not comeback again. Please
>> help. Noob. Thanks in advance.
>>
>> Jun 10 10:54:37 sunny1pub kernel:  connection1:0: iscsi: detected conn
>> error (1011)
>> .
>> .
>> .
>> Jun 10 10:54:40 sunny1pub iscsid: connection1:0 is operational after
>> recovery (1 attempts)
>>
>>
>> Jun 10 10:27:14 sunny1pub kernel: o2net: accepted connection from node
>> sunny2pub.ezhome.com (num 1) at 10.1.1.2:7777
>> Jun 10 10:27:18 sunny1pub kernel: ocfs2_dlm: Node 1 joins domain
>> 1B9768E4C4FC4165A22E5E95E6A93F80
>> Jun 10 10:27:18 sunny1pub kernel: ocfs2_dlm: Nodes in domain
>> ("1B9768E4C4FC4165A22E5E95E6A93F80"): 0 1
>> Jun 10 10:54:37 sunny1pub kernel:  connection1:0: iscsi: detected conn
>> error (1011)
>> Jun 10 10:54:37 sunny1pub iscsid: Kernel reported iSCSI connection 1:0
>> error (1011) state (3)
>> Jun 10 10:54:37 sunny1pub tgtd: abort_task_set(979) found a01 0
>> Jun 10 10:54:37 sunny1pub tgtd: conn_close(88) connection closed 0x9e370c4 2
>> Jun 10 10:54:39 sunny1pub kernel: iscsi: host reset succeeded
>
>
> Is the initiator connected to the target running on the same box?
>
>
> It looks like a command took too long. If a command takes longer than
> the scsi command timeout (/sys/block/sdX/device/timeout) then the scsi
> layer will try to abort it (if that fails reset the lun and if that
> fails reset the host).
>
>
>> Jun 10 10:54:40 sunny1pub iscsid: received iferror -38
>> Jun 10 10:54:40 sunny1pub last message repeated 2 times
>> Jun 10 10:54:40 sunny1pub iscsid: connection1:0 is operational after
>> recovery (1 attempts)
>> Jun 10 10:57:57 sunny1pub kernel: ping timeout of 5 secs expired, last
>> rx 1740985, last ping 1745985, now 1750985
>
> The initiator sends a iscsi nop as a ping every x seconds. If we do not
> get a response we drop the sesison, try to relogin and retry the IO.
>
>> Jun 10 10:57:57 sunny1pub kernel:  connection1:0: iscsi: detected conn
>> error (1011)
>> Jun 10 10:57:59 sunny1pub iscsid: Kernel reported iSCSI connection 1:0
>> error (1011) state (3)
>> Jun 10 10:59:58 sunny1pub kernel:  session1: iscsi: session recovery
>> timed out after 120 secs
>
> it looks like something happened to the target or connection. We were
> not able to log back in after trying for 2 minutes
> (node.session.replacement_timeout).
>
>> Jun 10 10:59:58 sunny1pub kernel: iscsi: cmd 0x2a is not queued (8)
>> Jun 10 11:06:10 sunny1pub syslogd 1.4.1: restart.
>>
>> >
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to