Yeah, that should fail. It only deletes the record for the target
portal. It would not log it out.
>
> [db1: ~]# iscsiadm -m node --logoutall=all
> Logging out of session [sid: 1, target: target0, portal:
> 172.16.10.11,3260]
> iscsiadm: Could not logout of [sid: 1, target: target0, portal:
> 172.16.10.11,3260]:
> iscsiadm: initiator reported error (9 - internal error)
>
This should work. Can you run
iscsiadm -m session -P 3
and send the output.
internal error normally means the session is just getting started and so
we cannot log it out yet.
> [db1: ~]# service iscsi stop
> Logging out of session [sid: 1, target: target0, portal:
> 172.16.10.11,3260]
> iscsiadm: Could not logout of [sid: 1, target: target0, portal:
> 172.16.10.11,3260]:
> iscsiadm: initiator reported error (9 - internal error)
> Stopping iSCSI daemon: [ OK ]
This runs the logout all command above so it fails for the same reason.
> [db1: ~]# iscsiadm -m session
> tcp: [1] 172.16.10.11:3260,4 target0
>
> CentOS 5.4 (2.6.18-164.11.1.el5)
> iscsi-initiator-utils.x86_64 6.2.0.871-0.16.el5
>
> Thanks for your help,
> Paul
>
>
> --
> ea926p
>
--
ea926p
It seems we might have a partially torn down session.
Does this always occur or does it only occur if you run the exact
commands you listed above?
Does the session ever get logged into properly (does the session state
very show logged in)?
Does this just happen with one session?
If you can replicate it easily can you dun iscsid by hand with debugging on:
iscsid -d 8 -f &
iscsiadm -m node -L automatic
iscsiadm -m node -U all
Send all the outpout from iscsid for both the login and logout command.