Discussion:
iscsi initiator logs?
v i n c e
2008-04-14 18:35:46 UTC
Permalink
Hello all,

I added edited my /etc/ietd.conf in my target and restarted - now it
has a different target-lun exported; I try to stop and start my iscsi-
initiator, and it is unable to "read" the NEW target, but seems like
there is some log it is reading and persistently wants to load the old
target-lun even after I stop'ed the iscsi service and ensured that the
PIDs are gone:

service iscsi start
iscsid dead but pid file exists
Turning off network shutdown. Starting iSCSI daemon: [ OK ]
[ OK ]
Setting up iSCSI targets: Login session [iface: default, target: iqn.
2001-04.com.mylab:storage.disktest, portal: 192.168.17.1,3260]
Login session [iface: default, target: iqn.2008-04.com.mylab:storage.
00A0D1E35826, portal: 192.168.17.3,3260]
iscsiadm: initiator reported error (5 - encountered iSCSI login
failure)
iscsiadm: Could not log into all portals. Err 107.

...............

Can someone please let me know where the log exists in the iscsi-
initiator? or anyway to allow the initiator software to "refresh" and
rediscover?

thanks in advance!

Best,

Vince
Konrad Rzeszutek
2008-04-14 11:21:24 UTC
Permalink
Post by v i n c e
Hello all,
I added edited my /etc/ietd.conf in my target and restarted - now it
has a different target-lun exported; I try to stop and start my iscsi-
initiator, and it is unable to "read" the NEW target, but seems like
there is some log it is reading and persistently wants to load the old
target-lun even after I stop'ed the iscsi service and ensured that the
service iscsi start
iscsid dead but pid file exists
Turning off network shutdown. Starting iSCSI daemon: [ OK ]
[ OK ]
Setting up iSCSI targets: Login session [iface: default, target: iqn.
2001-04.com.mylab:storage.disktest, portal: 192.168.17.1,3260]
Login session [iface: default, target: iqn.2008-04.com.mylab:storage.
00A0D1E35826, portal: 192.168.17.3,3260]
iscsiadm: initiator reported error (5 - encountered iSCSI login
failure)
iscsiadm: Could not log into all portals. Err 107.
...............
Can someone please let me know where the log exists in the iscsi-
initiator? or anyway to allow the initiator software to "refresh" and
rediscover?
Do iscsiadm -m node -T 2001-04.com.mylab:storage.disktest -o delete

And that will delete the node info from the persistent cache.
Mike Christie
2008-04-14 19:44:36 UTC
Permalink
Post by v i n c e
Hello all,
I added edited my /etc/ietd.conf in my target and restarted - now it
has a different target-lun exported; I try to stop and start my iscsi-
initiator, and it is unable to "read" the NEW target, but seems like
there is some log it is reading and persistently wants to load the old
target-lun even after I stop'ed the iscsi service and ensured that the
service iscsi start
iscsid dead but pid file exists
Turning off network shutdown. Starting iSCSI daemon: [ OK ]
[ OK ]
Setting up iSCSI targets: Login session [iface: default, target: iqn.
2001-04.com.mylab:storage.disktest, portal: 192.168.17.1,3260]
Login session [iface: default, target: iqn.2008-04.com.mylab:storage.
00A0D1E35826, portal: 192.168.17.3,3260]
iscsiadm: initiator reported error (5 - encountered iSCSI login
failure)
iscsiadm: Could not log into all portals. Err 107.
...............
Can someone please let me know where the log exists in the iscsi-
initiator? or anyway to allow the initiator software to "refresh" and
rediscover?
When you do discovery the cache should get refreshed for you if you are
just adding and removing targets. So if you do

- iscsiadm -m discovery .....
- edit ietd.conf
- return iscsiadm -m discovery ...
- the new target should get discovered and the old one should be removed.

If you are using the rc code then you can pass in -o new|delete|update
to control the behavior.
v i n c e
2008-04-14 21:56:04 UTC
Permalink
thanks a lot both!!!

so, just as an FYI, it does not automatically refresh when I re-issue
the "iscsiadm -m discovery, etc.... however when I opt to do with the
"-o delete" option, it clears it in persistent cache ...

thanks again!

- v.
Post by Mike Christie
Post by v i n c e
Hello all,
I added edited my /etc/ietd.conf in my target and restarted - now it
has a different target-lun exported; I try to stop and start my iscsi-
initiator, and it is unable to "read" the NEW target, but seems like
there is some log it is reading and persistently wants to load the old
target-lun even after I stop'ed the iscsi service and ensured that the
service iscsi start
iscsid dead but pid file exists
Turning off network shutdown. Starting iSCSI daemon: [ OK ]
[ OK ]
Setting up iSCSI targets: Login session [iface: default, target: iqn.
2001-04.com.mylab:storage.disktest, portal: 192.168.17.1,3260]
Login session [iface: default, target: iqn.2008-04.com.mylab:storage.
00A0D1E35826, portal: 192.168.17.3,3260]
iscsiadm: initiator reported error (5 - encountered iSCSI login
failure)
iscsiadm: Could not log into all portals. Err 107.
...............
Can someone please let me know where the log exists in the iscsi-
initiator? or anyway to allow the initiator software to "refresh" and
rediscover?
When you do discovery the cache should get refreshed for you if you are
just adding and removing targets. So if you do
- iscsiadm -m discovery .....
- edit ietd.conf
- return iscsiadm -m discovery ...
- the new target should get discovered and the old one should be removed.
If you are using the rc code then you can pass in -o new|delete|update
to control the behavior.
Loading...