UPStart errors on Xenial with systemd

[Serge Hallyn]

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):
> > > Guys,
> > >
> > >  Almost all daemons that I install on Xenial, I'm seeing the following
> >
> > Hi,
> >
> > could you give a specific example?
> >
> > thanks,
> > -serge
> >
> > > 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.  could you show the output of

dpkg -l | egrep -e '(systemd|upstart|init)'

?