6+ minute apt-daily.service boot delay
glgxg at sbcglobal.net
Tue Nov 15 02:12:55 UTC 2016
On 11/14/2016 2:03 PM, Tom H wrote:
> On Mon, Nov 14, 2016 at 9:12 PM, NoOp <glgxg at sbcglobal.net> wrote:
>> On 11/14/2016 7:36 AM, Oliver Grawert wrote:
>>> On So, 2016-11-13 at 18:11 -0800, NoOp wrote:
>>>> On 11/13/2016 03:51 PM, Karl Auer wrote:
>>>>> On Sun, 2016-11-13 at 14:42 -0800, NoOp wrote:
>>>>>> Ubuntu 16.04 running as a Virtualbox Version 5.1.8 r111374
>>>>>> guest - booted today after recent update & the boot took over 7
>>>>> That sort of delay is almost always either a failing hard disk or a
>>>>> network issue.
>>>> Reboot after purging: bind9, miredo, clamav
>>> smells like
>>> (which slows down DNS resolution on boot ... as karl mentioned above,
>>> looks like a network issue, not like the fault of apt)
>> That smells right... looking at syslogs with miredo installed I was seeing:
>> miredo-checkconf: Invalid host name “teredo-debian.remlab.net” at
>> line 6: Name or service not known
>> miredo-checkconf: Server address not specified
>> miredo-checkconf: Fatal configuration error
>> systemd: miredo.service: Control process exited, code=exited status=255
>> systemd: Failed to start Teredo IPv6 tunneling.
>> systemd: miredo.service: Unit entered failed state.
>> systemd: miredo.service: Failed with result 'exit-code'.
>> I'll reinstall later today & check the result then.
> I assume that you mean re-install miredo!
> Both the Debian bug above and the following one
> advise to add:
> to "miredo.service" (preferably as a drop-in in
> It's due to the problem that systemd exposes the fact that depending
> on "network.target" - corresponding to the "$network" LSB target -
> isn't enough for certain services, including, apparently, mired.
Thanks Tom - works:
$ /etc/init.d/miredo status
● miredo.service - Teredo IPv6 tunneling
Loaded: loaded (/lib/systemd/system/miredo.service; enabled; vendor
Active: active (running) since Mon 2016-11-14 18:01:59 PST; 2min 46s ago
Process: 2112 ExecStartPre=/usr/sbin/miredo-checkconf -f
/etc/miredo/miredo.conf (code=exited, status=0/SUCCESS)
Main PID: 2194 (miredo)
├─2194 /usr/sbin/miredo -f
├─2200 /usr/sbin/miredo -f
└─2202 /usr/lib/x86_64-linux-gnu/miredo/miredo-privproc 3
Nov 14 18:01:58 gg systemd: Starting Teredo IPv6 tunneling...
Nov 14 18:01:59 gg systemd: Started Teredo IPv6 tunneling.
Nov 14 18:02:00 gg miredo: miredo: Starting...
Nov 14 18:02:00 gg miredo: Starting...
Nov 14 18:02:01 gg miredo: miredo: New Teredo address/MTU
Nov 14 18:02:01 gg miredo: miredo: Teredo pseudo-tunnel started
Nov 14 18:02:01 gg miredo: miredo: (address:
Nov 14 18:02:01 gg miredo: New Teredo address/MTU
Nov 14 18:02:01 gg miredo: Teredo pseudo-tunnel started
Nov 14 18:02:01 gg miredo: (address:
$ cat /lib/systemd/system/miredo.service
Description=Teredo IPv6 tunneling
ExecStartPre=/usr/sbin/miredo-checkconf -f /etc/miredo/miredo.conf
ExecReload=/bin/kill -HUP $MAINPID
Now I still have to figure out how to trigger apt-daily.service at will
on boot to test.
More information about the ubuntu-users