Iscsciadm could not login to all portals? We can help you.

Generally, the backup server needs to log in to the iscsi targets on that HV. These targets are temporary for the backups.

As part of our Server Virtualization Technologies and Services, we assist our customers with several OnApp queries.

Today, let us see how we can fix this issue.

Iscsciadm could not login to all portals

In most cases, the backups fail with the following output:

Remote Server: 37.72.173.162
Running: iscsiadm -m node -o new -T "iqn.2015-04-11:onapp.com:backup-cih8vr6t2to5cu" -p 10.0.1.1
New iSCSI node [tcp:[hw=,ip=,net_if=,iscsi_if=default] 10.0.1.1,3260,-1 iqn.2015-04-11:onapp.com:backup-cih8vr6t2to5cu] added

Running: iscsiadm -m node -T "iqn.2015-04-11:onapp.com:backup-cih8vr6t2to5cu" -l
Logging in to [iface: default, target: iqn.2015-04-11:onapp.com:backup-cih8vr6t2to5cu, portal: 10.0.1.1,3260] (multiple)

iscsiadm: Could not login to [iface: default, target: iqn.2015-04-11:onapp.com:backup-cih8vr6t2to5cu, portal: 10.0.1.1,3260].

iscsiadm: initiator reported error (8 - connection timed out)

iscsiadm: Could not log into all portals

Fatal: Execution of iscsiadm -m node -T "iqn.2015-04-11:onapp.com:backup-cih8vr6t2to5cu" -l failed
Executing Rollback...

This can happen on all OnApp Versions, LVM/SAN Data Store, and Dedicated Backup Server.

Now, let us see the method our Support Techs employ in order to fix this.

How to fix ‘Iscsciadm could not login to all portals’?

To fix this, we restart tgtd on the VM’s hypervisor.

To do so, we run the command:

service tgtd restart

If tgtd is stuck, we need to kill the old processes and then restart it.

[root@sjhypervisor1 ~]# ps aux | grep tgtd
root 13240 0.0 0.0 103296 836 pts/10 S+ 12:10 0:00 grep tgtd
root 28097 0.0 0.0 54836 1152 ? Ss 02:10 0:03 tgtd
root 28098 0.0 0.0 19916 424 ? S 02:10 0:01 tgtd
[root@sjhypervisor1 ~]# kill -9 28097 28098
[root@sjhypervisor1 ~]# /etc/init.d/tgtd restart
Stopping SCSI target daemon: not running [FAILED]
Starting SCSI target daemon: [ OK ]
[root@sjhypervisor1 ~]#

Conclusion

In short, this issue occurs when the backup server cannot log in to the iscsi targets on that HV. In this article, we saw how our Support Techs resolve this for our customers.