replacement_timeout Override

[Marc Smith]

Hi,

I'm using open-iscsi version 2.1.1. I noticed that my
"replacement_timeout" value set in the node record is not being
applied, or rather is not overriding the default value set in
iscsid.conf:

# iscsiadm -m node -T internal_redirect | grep replacement_timeout
node.session.timeo.replacement_timeout = 5

# cat /etc/iscsi/iscsid.conf | grep replacement_timeout
node.session.timeo.replacement_timeout = 120

# cat /sys/class/iscsi_session/session1/recovery_tmo
120

# iscsiadm -m session -P 2 | grep Recovery
Recovery Timeout: 120

I can certainly change this value in iscsid.conf, but I was thinking
my value in the node record would override this (for this specific
target). Is it expected that this value should override what's in
iscsid.conf? If so, then I assume I've hit a bug, or perhaps I have
something configured incorrectly?

Thanks for your time.

--Marc

[Ulrich Windl]

>>> Marc Smith <msmi...@gmail.com> schrieb am 14.03.2020 um 15:28 in Nachricht
<29983_1584196109_5E6CEA0D_29983_1691_1_CAH6h+hdZ7QvF_WuLU5PJVpe4RpjM4EeEW7aBQVZ
fOrZV...@mail.gmail.com>:

I think whatever it was designed to do, there should be a "notice" at least that some specified setting is ignored if it is.

>
> --Marc
>
> --
> You received this message because you are subscribed to the Google Groups
> "open-iscsi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to open-iscsi+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/open-iscsi/CAH6h%2BhdZ7QvF_WuLU5PJVpe4RpjM4
> EeEW7aBQVZrfOrZV1PLCA%40mail.gmail.com.

[Marc Smith]

Okay, so after digging a bit, the default values from iscsid.conf are
in fact being superseded by the specific session values. That is
demonstrated when I run "iscsiadm -m node -T internal_redirect". The
only problem is the values aren't applied to the running session (the
sysfs attribute files for the session are not updated when the record
is updated).

I was changing the values for a session that was already established.
The solution is to set the node record values, then simply logout and
login.

--Marc

[The Lee-Man]

I'm glad you figured it out. Sorry I didn't reply sooner.