At work we tried to run iscsi on a server. Two network interfaces, one for
outside network, one for storage. The iscsi target was on the storage network
behind eth1 and kept giving weird errors, which showed in the syslog like:
Jan 6 16:43:54 fokke iscsid: Could not bind connection 0 to eth1
Jan 6 16:43:54 fokke iscsid: cannot make a connection to 172.16.0.3:3260 (1)
Jan 6 16:48:16 fokke iscsid: iSCSI logger with pid=21827 started!
Jan 6 16:48:17 fokke iscsid: transport class version 2.0-724. iscsid version 2.0-868
Jan 6 16:48:17 fokke iscsid: iSCSI daemon with pid=21828 started!
Jan 6 16:48:17 fokke iscsid: send fail Connection refused
Jan 6 16:48:37 fokke iscsid: Could not bind connection 0 to eth1
Jan 6 16:48:37 fokke iscsid: cannot make a connection to 172.16.0.3:3260 (1)
The culprit? SELinux. Disabling SELinux completely made iscsid
function normally and log in to the storage system and our configured
volume show up. It seems SELinux gets in the way a lot of times, I usually
have to disable it on systems.