> Importance medium is a joke You will always be able to access the container from the host. Of course, this won't work easily if you do not have access to the host. However, OpenVZ is not supported by Ubuntu and this is just one of the reasons why you would be better using Debian for server machines. I am increasing the importance, but that does not make it more likely to get addressed in upstart unfortunately.
** Changed in: upstart (Ubuntu) Importance: Medium => High ** Description changed: 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). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/634900 Title: "oom never" makes ssh upstart job fail to start in OpenVZ container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/634900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
