missing /var/run/eucalyptus

[Chris Jones]

After applying the latest jaunty updates I rebooted and now eucalyptus-nc will not start. looking through the httpd-nc_error_log this seems to be because /var/run/eucalyptus did not exist. Creating it and chowning eucalyptus:eucalyptus allows the NC to start.

Perhaps the postinst of eucalyptus-common should be creating it?

[Daniel Nurmi (nurmi)]

in addition, the directory /var/run/eucalyptus/net should also be (re)created

[Soren Hansen (soren)]

I'm assuming /var/run/eucalyptus/net is a node controller only thing, correct?

[Launchpad Janitor (janitor)]

This bug was fixed in the package eucalyptus - 1.5~bzr232-0ubuntu1

---------------
eucalyptus (1.5~bzr232-0ubuntu1) jaunty; urgency=low

  * New upstream snapshot. (LP: #342024, #341965)
    + Correctly set up swap and ephemeral storage for KVM VM's. (LP:
      #332973)
    + Use correct names for devices. (LP: #334665)
    + Use compression for image transfers. (LP: #332971)
    + Don't fail if first attempt at image download fails. (LP: #337027)
    + Don't time out if image transfer takes more than one hour, but is
      still on-going. (LP: #337870)
    + Don't allow to delete in-use volumes. (LP: #342121)
    + Correctly handle failure to attach volumes (LP: #342077)
    + Handle unknown EBS block device names with KVM backend. (LP: #342076)
    + Make euca_conf -delnode remove the node properly. (LP: #342055)
  * Drop addnode-ssh-magic.patch. Adopted upstream.

eucalyptus (1.5~bzr212-0ubuntu4) UNRELEASED; urgency=low

  * Also create /var/run/eucalyptus/net for the node controller.
    (LP: #338764)
  * Added bridge-utils and dhcp3-server as recommended packages for the
    node controller. (LP: #338846)

 -- Soren Hansen <email address hidden> Tue, 17 Mar 2009 23:14:50 +0100