UPStart errors on Xenial with systemd

Serge Hallyn serge.hallyn at ubuntu.com
Tue Apr 5 13:30:13 UTC 2016


Quoting Martin Pitt (martin.pitt at ubuntu.com):
> Hello Martinx,
> 
> Martinx - ジェームズ [2016-04-04 18:49 -0300]:
> > 
> > Symlink:
> > 
> > cron -> /lib/init/upstart-job
> > 
> > And a file:
> > 
> > cron.dpkg-new
> > 
> > Maybe, during "do-release-upgrade" from 14.04 to 16.04, it didn't upgraded
> > that file / link...
> > 
> > This looks like an upgrade bug!
> 
> Right, it sounds like the new "cron" got unpacked, but not configured,
> i. e. the upgrade crashed somewhere in the middle. What's the output
> of "dpkg -s cron"? It should have "Status: install ok installed", if
> it's anything like "unpacked", or "unconfigured" or so it's broken.

Note I can easily reproduce this by creating a 14.04 lxd container and
doing do-release-upgrade in there.

> Does "sudo apt-get -f install" clean this up?

No.

> Can you put the upgrade logs from /var/log/dist-upgrade/ somewhere?
> This hopefully has some clues where the upgrade failed.
> 
> Martin
> -- 
> Martin Pitt                        | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)




More information about the ubuntu-server mailing list