In newer versions of iscsid (RHEL6) the init.d script has been changed,
such that the start method won't do anything unless discovery etc has
already occurred at least once.
As a result, there's now a new option in iscsid.conf - 'iscsid.startup'
which you can set to be a command to be run when iscsiadm is unable to
connect to the iscsid daemon:
http://groups.google.com/group/open-iscsi/browse_thread/thread/afdaaedad9050da8
The iscsi RA shouldn't fail if it notices iscsid isn't running if this
value is set - this patch checks the config file to see if it exists,
and if it does, doesn't return an error.
One side-effect of this change in behaviour is that this startup will
only be carried out for certain iscsiadm actions. Since (in RH anyway)
the init.d script also loads the iscsi kernel modules, some actions in
the RA will now fail if these modules haven't been loaded.
The solution seems to be to 'manually' load the modules (e.g. via
/etc/modprobe.d). I'm not sure if this will have HA effects, since this
will be a 'one-off' operation, e.g at boot.
Please let me know if you have any comments/suggestions on this patch,
or think that a different approach to starting the iscsid daemon from
the RA is now needed.
Thanks,
Matthew
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
such that the start method won't do anything unless discovery etc has
already occurred at least once.
As a result, there's now a new option in iscsid.conf - 'iscsid.startup'
which you can set to be a command to be run when iscsiadm is unable to
connect to the iscsid daemon:
http://groups.google.com/group/open-iscsi/browse_thread/thread/afdaaedad9050da8
The iscsi RA shouldn't fail if it notices iscsid isn't running if this
value is set - this patch checks the config file to see if it exists,
and if it does, doesn't return an error.
One side-effect of this change in behaviour is that this startup will
only be carried out for certain iscsiadm actions. Since (in RH anyway)
the init.d script also loads the iscsi kernel modules, some actions in
the RA will now fail if these modules haven't been loaded.
The solution seems to be to 'manually' load the modules (e.g. via
/etc/modprobe.d). I'm not sure if this will have HA effects, since this
will be a 'one-off' operation, e.g at boot.
Please let me know if you have any comments/suggestions on this patch,
or think that a different approach to starting the iscsid daemon from
the RA is now needed.
Thanks,
Matthew
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.