Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Failed to start Login to default iSCSI targets

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
Nibe21
Posts: 1
Joined: 2021-01-30 22:39

Failed to start Login to default iSCSI targets

#1 Post by Nibe21 »

I've just upgraded my packages and my Debian distribution to the newest one which is now the "Bullseye". Unfortunately, I've noticed that I've got some errors so I run again the command 'sudo apt upgrade' but I've got this error (see below). It seems that something during the distribution upgrade went wrong with open-iscsi. Thanks for helping.

sudo apt upgrade Reading package lists... Done

Building dependency tree

Reading state information... Done

Calculating upgrade... Done

The following packages have been kept back: aisleriot libpython2-stdlib libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5 libqt5svg5 libqt5widgets5 python2 python2-minimal qdirstat qt5-gtk-platformtheme w3m

0 upgraded, 0 newly installed, 0 to remove and 13 not upgraded. 1 not fully installed or removed.

After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y

Setting up open-iscsi (2.1.3-1) ...

Job for open-iscsi.service failed because the control process exited with error code.

See "systemctl status open-iscsi.service" and "journalctl -xe" for details.

invoke-rc.d: initscript open-iscsi, action "restart" failed.

open-iscsi.service - Login to default iSCSI targets Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Fri 2021-01-29 12:03:41 CET; 6ms ago

Docs: man:iscsiadm(8)

man:iscsid(8)

Process: 3451492 ExecStartPre=/bin/systemctl --quiet is-active iscsid.service (code=exited, status=0/SUCCESS)

Process: 3451494 ExecStart=/sbin/iscsiadm -m node --loginall=automatic (code=exited, status=19)
Main PID: 3451494 (code=exited, status=19)

gen 29 12:03:41 TACsrv iscsiadm[3451494]: iscsiadm: initiator reported error (8 - connection timed out)

gen 29 12:03:41 TACsrv iscsiadm[3451494]: iscsiadm: Could not login to [iface: eth1, target: iqn.2000-01.com.synology:rs-clindia.Target-1.fdc0e7fc14, po rtal: 10.110.40.249,3260].

gen 29 12:03:41 TACsrv iscsiadm[3451494]: iscsiadm: initiator reported error (8 - connection timed out)

gen 29 12:03:41 TACsrv iscsiadm[3451494]: iscsiadm: Could not log into all portals on eth1, trying next interface

gen 29 12:03:41 TACsrv iscsiadm[3451494]: iscsiadm: Could not login all leading-login portals

gen 29 12:03:41 TACsrv iscsiadm[3451494]: Logging in to [iface: eth1, target: iqn.2000-01.com.synology:rs-clindia.Target-1.fdc0e7fc14, portal: 192.168.1 00.60,3260]

gen 29 12:03:41 TACsrv iscsiadm[3451494]: Logging in to [iface: eth1, target: iqn.2000-01.com.synology:rs-clindia.Target-1.fdc0e7fc14, portal: 10.110.40 .249,3260]

gen 29 12:03:41 TACsrv systemd[1]: open-iscsi.service: Main process exited, code=exited, status=19/n/a

gen 29 12:03:41 TACsrv systemd[1]: open-iscsi.service: Failed with result 'exit-code'.

gen 29 12:03:41 TACsrv systemd[1]: Failed to start Login to default iSCSI targets.

dpkg: error processing package open-iscsi (--configure): installed open-iscsi package post-installation script subprocess returned error exit status 1

Processing triggers for initramfs-tools (0.139) ... update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64

modinfo: ERROR: could not get modinfo from 'crc32': No such file or directory

Errors were encountered while processing: open-iscsi

E: Sub-process /usr/bin/dpkg returned an error code (1)

User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 132 times

Re: Failed to start Login to default iSCSI targets

#2 Post by Head_on_a_Stick »

Is this actually Debian or are you using a derivative? Note that bullseye hasn't been released yet.

Judging by the kernel version listed in your terminal output (which should be enclosed in code tags btw) you have tried to upgrade from jessie to bullseye, which isn't a good idea. Try going from jessie to stretch to buster and then to bullseye. Follow the comprehensive upgrade guides supplied by the release notes for each version (bullseye doesn't have a guide because it's still a development branch so you're on your own with that).
deadbang

Post Reply