I'll mark the bug as fix released as I think Ubuntu releases no longer
suffer from this problem. Also, all Ubuntu releases still receiving
normal support have moved away from upstart.
** Changed in: upstart (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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:
Fix Released
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
