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

[James Lewis]

Up until a few minutes ago, I had not found this bug, and had been
starting sshd from the init.d script instead of upstart... but as of the
last patch, the init.d script was modified to use upstart to start sshd,
so I had to find the solution... commenting oom_never solved the
problem, but now I need to identify why that is there in the first
place.

-- 
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

  POSSIBLE FIXES:
  1. Ignore any errors when trying to set "oom never" for the job?!
  2. Only apply "oom never" if not in a virtualized context (see comment #2).

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