UPStart errors on Xenial with systemd

[Tom H]

On Wed, Mar 30, 2016 at 10:46 PM, Serge Hallyn <serge.hallyn at ubuntu.com> wrote:
> Quoting Martinx - ジェームズ (thiagocmartinsc at gmail.com):
>> On 30 March 2016 at 14:08, Serge Hallyn <serge.hallyn at ubuntu.com> wrote:
>>> Quoting Martinx - ジェームズ (thiagocmartinsc at gmail.com):
>>>>
>>>> Almost all daemons that I install on Xenial, I'm seeing the following
>>>
>>> could you give a specific example?
>>>
>>>> error:
>>>>
>>>> ---
>>>> initctl: Unable to connect to Upstart: Failed to connect to socket
>>>> /com/ubuntu/upstart: Connection refused
>>>> ---
>>>>
>>>> It is running systemd by default, so, why those upstart jobs are called?
>>
>> Sure! Here are the examples...
>>
>> apt install apache2
>> .....
>> Enabling conf serve-cgi-bin.
>> Enabling site 000-default.
>> initctl: Unable to connect to Upstart: Failed to connect to socket
>> /com/ubuntu/upstart: Connection refused
>> insserv: warning: script 'cron' missing LSB tags and overrides
>> insserv: Default-Start undefined, assuming empty start runlevel(s) for
>> script `cron'
>> insserv: Default-Stop undefined, assuming empty stop runlevel(s) for
>> script `cron'
>> Processing triggers for systemd (229-3ubuntu1) ...
>> ....
>
> I'm not seeing htat.

Me neither; but upstart isn't installed on either of my two 16.04 instances.

Don't these messages come from "initctl version" being run in postinst
scripts to check whether upstart's pid 1? I vaguely remember a Debian
bug a year or two ago being filed for this and initctl was silenced
when systemd was pid 1 and upstart installed.