Thanks for your response. I'm using Kubuntu 19.04. I disabled the iscsi
service and in fact the boot was much faster:
$ systemd-analyze blame
10.079s rtslib-fb-targetctl.service
6.134s NetworkManager-wait-online.service
928ms snap-lxd-10972.mount
While I don't need the QNAP/iscsi to boot, disabling the iscsi service is
not optimal, as I
need access to data on QNAP to operate.
While I'm not a novice, I confess that I'm in "deep water" when it comes to
investigating systemd
dependencies and fixes. The iscsiuio.service exists on my Kubuntu
initiator, but I don't know how to determine if it's
causing the problem, or for that matter even if it's being used. Regards
Broadcom, are you referring to use on the Kubuntu
initiator, or the QNAP target?
Any further tips or links to diagnose and/or fix appreciated .... Thx
On Tuesday, June 25, 2019 at 6:37:09 AM UTC-7, The Lee-Man wrote:
>
> On Saturday, June 22, 2019 at 11:00:44 AM UTC-4, Randy Broman wrote:
>>
>> I have open-iscsi installed on Kubuntu 19.04, to access shared storage on
>> a QNAP NAS server. The setup works, but open-iscsi slows boot:
>>
>> $ systemd-analyze blame
>> 2min 6.105s open-iscsi.service
>> 10.076s rtslib-fb-targetctl.service
>> 6.042s NetworkMan.....
>> ..
>>
>> and I don't need QNAP/open-iscsi to boot, so I'm trying to set up a timer
>> to delay iscsi connection until after the boot completes and the
>> Kubuntu/Plasma desktop
>> loads. Here's what I have:
>>
>> $ cat /lib/systemd/system/open-iscsi.timer
>> [Unit]
>> Description=open-iscsi timer
>>
>> [Timer]
>> # Time to wait after booting before it run for first time
>> OnBootSec=3min
>> Unit=open-iscsi.service
>>
>> [Install]
>> WantedBy=timers.target
>>
>> $ ls -l /lib/systemd/system/open-iscsi.service
>> -rw-r--r-- 1 root root 1068 Dec 11 2018
>> /lib/systemd/system/open-iscsi.service
>>
>> ls -l /etc/systemd/system/timers.target.wants/open-iscsi.timer
>> lrwxrwxrwx 1 root root 36 Jun 21 20:59
>> /etc/systemd/system/timers.target.wants/open-iscsi.timer ->
>> /lib/systemd/system/open-iscsi.timer
>>
>> (I ran $ sudo systemctl daemon-reload and $ sudo systemctl enable
>> open-iscsi.timer after creating the timer)
>>
>> What am I doing wrong, and/or what do I need to do to fix this?
>>
>> Thx!
>>
>
> I don't know anything about systemd timers, but there should be no reason
> for this.
>
> What distro are you using? What iscsi service files are there, and which
> ones are enabled?
>
> In SUSE we have iscsid.socket, iscsid.service, and iscsi.service. The
> first two are for the iscsid daemon, and the last is for iscsi
> logins/logouts. Then, if you're using broadcom, you might also have
> iscsiuio.socket and iscsiuio.service.
>
> I investigated a bug once where a customer was unhappy the iscsi service
> was taking so long to startup, according the systemd "blame", but it really
> wasn't taking a long time, but the dependencies made it look that way. You
> can always completely disable iscsi serivces and compare the actual boot
> time to when it is enabled to see if it really impacting your boot time.
>
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/open-iscsi.
To view this discussion on the web visit
https://groups.google.com/d/msgid/open-iscsi/37c0b6be-68ec-474e-b95d-e9450bfc4000%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
