On Tue, 2019-07-23 at 17:06 +0300, Dokuchaev Ivan wrote: > I don't know how much "+moreinfo" you need, Ritesh, without > specifying > what do you really want to hear, but the only hint I get at system > boot > (with systemd.log_target=kmsg systemd.log_level=debug) is this: > > rc.local[413]: iscsiadm: initiator reported error (19 - encountered > non-retryable iSCSI login failure) >
This is useful. So from the information so far, it looks like your network is not usable for the iscsi service, which immediately gives up. > Which is misleading, since invoking "iscsiadm -m node -L all" > successfully connects after a login. And I must note, that even then > it What is configuring your network ? But either way, the dependency chain should take care of that. What is the output of `iscsi.service` and `iscsid.service` Both the services start after the network target is completed. So you need to look at your network. I suspect that is at fault here. > only appears after creating and populating rc.local, without it issue > still reproduces, but there is no indication in either > journald/console > logs, only silent failure. I don't know much about your setup. But if you have systemd configured default, all your system logs should be persistent and available through journalctl. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
