problems upgrading an Ubuntu EC2 node

[Amos Shapira]

Thanks for coming back with the solution.

Though in a broader perspective: "you are holding it wrong" - get used to
the fact that you are running in the cloud and use it right - learn to
build your images from scratch so you can move to a  updated base image and
automatically install and configure your system on top of it. Otherwise I
can guarantee that you'll hit such a problem (or be very worried about it)
in your next upgrade.
On 23 Feb 2016 9:09 a.m., "Amit Aronovitch" <aronovitch at gmail.com> wrote:

> Posting the fix to list, in case someone searches the archives:
>
> Turns out that there were some leftover upstart files in /etc/init/, which
> apparently belonged to an old package (lxcguest) which had been uninstalled
> but left configured (possibly a remainder from a previous upgrade).
> Moving them away (by attaching and mounting the root volume onto another,
> live, machine) made the upgraded-ubuntu-machine bootable.
>
> The solution was taken from this link (which also details the diagnosis):
>
> http://www.nicksherlock.com/2015/01/my-ec2-server-wouldnt-boot-after-apt-get-dist-upgrade-i-fixed-it/
>
> Thanks Shimi for the quick response and for pointing out that link to me.
>
> AA
>
> p.s. I still have no idea why attaching this volume to a stopped machine
> had made it unbootable (upstart cannot be affected by extra disks that are
> not even automounted via fstab).
>
>
> _______________________________________________
> Linux-il mailing list
> Linux-il at cs.huji.ac.il
> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20160223/6dacca6f/attachment.html>