[Bug 634900] Re: "oom never" makes ssh upstart job fail to start in OpenVZ container

Fabian 634900 at bugs.launchpad.net
Wed Jun 29 22:05:45 UTC 2011


Hi,

yes I was bitten by it too. Just wasted 2 hours figuring it out via a plesk recovery console (strato).
Importance medium is a joke!! Often ssh is your only way to access a remote server, so a lot of people will get cur from their servers.

And no, I don't want to critique your wonderfull work, but sshd probles
should be treated with highest priority.

Sincerely, Fabian

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/634900

Title:
  "oom never" makes ssh upstart job fail to start in OpenVZ container

Status in “upstart” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: upstart

  /etc/init/ssh.conf uses "oom never", which causes the job failing to
  start in an OpenVZ container.

  Host:
   - kernel: 2.6.32-5-openvz-amd64 (Debian testing)
  Container:
  openssh-server: 1:5.3p1-3ubuntu4 (Lucid)
  Upstart: 0.6.5-7 (Lucid)

  This is a known problem (mentioned on
  http://ubuntuforums.org/showpost.php?p=9170868&postcount=2).

  What information is required to debug this? Some strace output?

  WORKAROUND:
   - comment the "oom never" line

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/634900/+subscriptions




More information about the foundations-bugs mailing list