search for: iscsid

...nnection loss on my dom0 (Gentoo 2.6.20-xen-r6, xen 3.1.1). Happening several times a day. open-iscsi version is 2.0.865.12. Target iscsi is the open-e DSS product. Here is a snip of my messages log file: May 5 16:52:50 ying connection226:0: iscsi: detected conn error (1011) May 5 16:52:51 ying iscsid: connect failed (111) May 5 16:52:51 ying iscsid: Kernel reported iSCSI connection 226:0 error (1011) state (3) May 5 16:52:53 ying connection215:0: iscsi: detected conn error (1011) May 5 16:52:53 ying iscsid: connect failed (111) May 5 16:52:53 ying iscsid: connect failed (111) May 5 16:52:...

...ice sdb: drive cache: write back > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: 629145600 512-byte > hdwr sectors (322123 MB) > Apr 29 10:24:41 vz-10 kernel: sdb: Write Protect is off > Apr 29 10:24:41 vz-10 kernel: SCSI device sdb: drive cache: write back > Apr 29 10:24:41 vz-10 iscsid: connection1:0 is operational now > Apr 29 10:24:44 vz-10 udevd-event[23432]: wait_for_sysfs: waiting > for '/sys/devices/platform/host1/session1/target1:0:0/1:0:0:0/ > ioerr_cnt' failed > Apr 29 10:25:06 vz-10 iscsid: Nop-out timedout after 15 seconds on > connection 1:...

I have a set of CentOS 5.7 workstations, on which I have turned of iscsid using 'chkconfig iscid off'. However, when some of them reboot, iscsid starts anyway. Also, when I do an 'service --status-all", iscsid is listed twice (this is true on both the workstations where iscsid starts and the ones where iscsid doesn't start), which seems to indicate...

Hi all, I have the strangest problem on one of our backup server. iscsi doesn't start at all, and gives the following error: [root at 2U-NAS ~]# /etc/init.d/iscsi status iscsid is stopped [root at 2U-NAS ~]# /etc/init.d/iscsi start iscsid is stopped Starting iSCSI daemon: Unable to create pid file: /var/run/brcm_iscsiuio.pid [FAILED] Setting up iSCSI targets: iscsiadm: No records found! [ OK ] [root at...

....168.2.100,3260]: iscsiadm: initiator reported error (8 - connection timed out) The network connectivity is up, I can ping the san host from the initiator, the initiator is in the allow list on target and I haven''t any type of authentication on target. When I run the iscsiadm command the iscsid daemon report: iscsid: thread 0063bf90 removed from poll_list iscsid: exec thread 0063bf90 callback iscsid: put conn context 0x63bf90 iscsid: poll not connected 0 iscsid: get conn context 0x63bf90 iscsid: sched conn context 0x63bf90 event 2, tmo 0 iscsid: thread 0x63bf90 schedule: delay 0 state 3...

...2 = 8225280 bytes Disk /dev/dm-2 doesn't contain a valid partition table I am trying to mount this device /dev/hdb as a shared storage across to of my RAC nodes , by running iscsi service restart from one of the nodes , i see this message in the /var/log/messages Oct 17 13:03:37 htssclin4 iscsid[6202]: cannot make connection to 1.1.1.3:3260: Connection refused Oct 17 13:03:37 htssclin4 iscsid[6202]: Connection to Discovery Address 1.1.1.3 failed Oct 17 13:03:38 htssclin4 iscsid[6202]: Connected to Discovery Address 1.1.1.3 Oct 17 13:05:10 htssclin4 sshd(pam_unix)[6253]: session opened f...

...disk = [ ''phy:/dev/disk/by-id/scsi-360a9800043346863483437714a643833,hda,w'' ] At around noon today (though it''s happend a few times in the last few weeks) one of our switches was powered off. At that time, here is what I see in syslog of dom0: Nov 9 12:06:04 egovxen1 iscsid: connect failed (113) Nov 9 12:06:13 egovxen1 iscsid: connect failed (113) Nov 9 12:06:21 egovxen1 iscsid: connect failed (113) Nov 9 12:06:29 egovxen1 iscsid: connect failed (113) Nov 9 12:06:38 egovxen1 iscsid: connect failed (113) Nov 9 12:06:46 egovxen1 iscsid: connect failed (113) Nov 9...

...timeout = 5 Logs at the time of failure on mgr01: Nov 6 01:00:12 mgr01 kernel: connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4325764337, last ping 4325769337, now 4325774337 Nov 6 01:00:12 mgr01 kernel: connection1:0: detected conn error (1011) Nov 6 01:00:13 mgr01 iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3) Nov 6 01:00:15 mgr01 iscsid: connection1:0 is operational after recovery (1 attempts) Nov 6 01:00:38 mgr01 kernel: o2net: no longer connected to node rack105 (num 7) at 10.244.1.105:7777 Nov 6 01:00:38 mgr01 kernel: (3270,0):dlm_se...

Hi, How do I setup multiple password protected iSCSI targets on Linux? I know that mounting a password protected iSCSI target requires modify these records with the appropriate values: node.session.auth.username = My_ISCSI_USR_NAME node.session.auth.password = MyPassword discovery.sendtargets.auth.username = My_ISCSI_USR_NAME discovery.sendtargets.auth.password = MyPassword But, now I need

...-308.1.1.el5 it hangs on "starting iSCSI" and the weird thing is when I tried to switch back to the older 2.6.18-308.1.1.el5 kernel it works fine but the network script fails to start. I'm not really sure what I should do, if someone can give me an idea on what I need to do to fix the iSCSId issue on the new kernel or revert back to the old kernel and fix the network issue. The odd thing is both kernel load the e100 network driver but on the older kernel I can get the network script to start. I would appreciate some help. paul

...596.511204] connection2:0: detected conn error (1022) Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4295253788, last ping 4295258790, now 4295263808 Apr 4 11:18:42 funk kernel: connection2:0: detected conn error (1022) Apr 4 11:18:42 funk iscsid: Kernel reported iSCSI connection 2:0 error (1022 - Invalid or unknown error code) state (3) Apr 4 11:18:44 funk iscsid: connection2:0 is operational after recovery (1 attempts) Repeated a few times, until eventually Apr 4 11:19:44 funk kernel: Result: hostbyte=DID_TRANSPORT_DISRUPTED drive...

...runs latest BIOS'es and ethernet firmware. The servers in question are Dell PowerEdges from different generations, talking to an Equallogic diskarray over 1Gbit copper. Dells toolset is installed, OMSA as well as hitkit. The errors I'm seeing are looking like this: Apr 13 23:03:43 xen15-2 iscsid: Kernel reported iSCSI connection 25:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TCP connection closed) state (1) Apr 13 23:03:43 xen15-2 iscsid: Connection25:0 to [target: iqn.xxxxx, portal: a.b.c.d,3260] through [iface: eql.em2] is operational now Apr 13 23:03:48 xen15-2 iscsid: Connection9:0 to [t...

...it seems now I have iSCSI connection interrupted and not stable. During this phase the command [root at ov300 network-scripts]# iscsiadm -m session -P1 has in its output for the 2 interfaces Iface Netdev: p1p2.100 SID: 5 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FAILED Internal iscsid Session State: REOPEN ... SID: 6 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FREE Internal iscsid Session State: REOPEN and then Iface Netdev: p1p2.100 SID: 5 iSCSI Connection State: TRANSPORT WAIT iSCSI Session State: FREE Internal iscsid Session State: REOPEN ... Iface Netdev: p...

...and on rebooted I spotted an error about iscsi. Which surprised me, since I don't use iscsi. Yet there it is... % rpm -qf /etc/init.d/iscsi iscsi-initiator-utils-6.2.0.872-6.el5 And they're configured to start iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsid 0:off 1:off 2:off 3:on 4:on 5:on 6:off And I can't remove it % rpm -e iscsi-initiator-utils error: Failed dependencies: iscsi-initiator-utils is needed by (installed) mkinitrd-5.1.19.6-68.el5.i386 A physical machine still on 5.5 doesn't have iscsi %...

...hen i try to connect to iscsi target it doesnt work ... it just stays idle , i try something like: iscsiadm -m discovery -t st -p 172.20.2.76 show or with -m node .... --login ...etc, none works. using the same configuration on ubuntu gutsy, same version things work! i also made both /etc/iscsi/iscsid.conf identical ... no luck :( i did tcpdump too (-vv -n ) and then grep the ip of the iscsi target, i see no traffic to the iscsi target at all on the centos machine, i tried it on the other machine it works :S Is there anything else to check? firewalls are all shutdown on all nodes ... i tried s...

...y script from the xcp-storage-managers Debian package with its equivalent script shipped with XCP CentOS-based distro I could confirm that they are the same. What I did was to alter line 198 of the /usr/lib/xcp/sm/iscsilib.py file from cmd = ["/sbin/pidof", "-s", "/sbin/iscsid"] to cmd = ["/bin/pidof", "-s", "/usr/sbin/iscsid"] to reflect the actual path of the 'iscsid' binary in Debian. However, I think it's more 'debianistic' to get this path each time the script runs (something like 'which iscsid') or m...

...t /files/etc/default/ovirt/OVIRT_ISCSI_TARGET_IP $OVIRT_ISCSI_TARGET_IP +set /files/etc/default/ovirt/OVIRT_ISCSI_TARGET_PORT $OVIRT_ISCSI_TARGET_PORT +EOF + + if [[ -n "$OVIRT_ISCSI_CHAP_USERNAME" && -n "$OVIRT_ISCSI_CHAP_PASSWORD" ]]; then + log "setting iscsid.conf username/password" + augtool <<EOF +set /files/etc/iscsi/iscsid.conf/node.session.auth.authmethod CHAP +set /files/etc/iscsi/iscsid.conf/node.session.auth.username $OVIRT_ISCSI_CHAP_USERNAME +set /files/etc/iscsi/iscsid.conf/node.session.auth.password $OVIRT_ISCSI_CHAP_PASSWO...

...-1</owner> <group>-1</group> </permissions> </target> </pool> > Also, do you need to authenticate to the iSCSI target? Not yet. To rule out authentication issues for testing I turned off authentication. > The iscsiadm will use '/etc/iscsi/iscsid.conf'. See the > node.session.auth.{authmethod | username | password} fields, so > while iscsiadm may work, when libvirt goes to connect it fails. Thanks for pointing that out, but I don't think it's the case here. > Looking at the output in the system messages > log may h...

Hi all, I have a Dell server running cent 5.6, new install, connecting to an IBM DS3500. I have configured iscsi connections using iscsid and can log into the targets on the IBM. I can also mount the LUNs when accessing them from their active controller path. When I throw multipath into the mix, it fails completely. Multipath is working, when I run multipath -ll it shows me the correct active path and it is mapped to a device unde...

...>> error (1022) >> Apr 4 11:18:42 funk kernel: connection2:0: ping timeout of 5 secs expired, >> recv timeout 5, last rx 4295253788, last ping 4295258790, now 4295263808 >> Apr 4 11:18:42 funk kernel: connection2:0: detected conn error (1022) >> Apr 4 11:18:42 funk iscsid: Kernel reported iSCSI connection 2:0 error >> (1022 - Invalid or unknown error code) state (3) >> Apr 4 11:18:44 funk iscsid: connection2:0 is operational after recovery (1 >> attempts) >> >> Repeated a few times, until eventually >> >> >> Apr 4 11...