I ran into this problem today on 10.04.4 LTS, and the workaround works
for me.
--
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
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
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
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
Dito. Very annoying after the restart of my server in an OpenVz
container, and i have to write the support.
--
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
Same here. Luckily I was able to fix it using the Plesk filesystem browser and
editing the file.
+1 for increasing importance.
--
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
Same here with 10.04.02 in OpenVZ
--
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
--
ubuntu-bugs mailing list
** Description changed:
Binary package hint: upstart
- /etc/init/ssh.conf uses oom never, which causes the job to start in an
- OpenVZ container.
+ /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
I can also confirm this in my updated 10.04.2 install which runs in an
OpenVZ container on a CentOS host.
--
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
I just updated my 10.04 LTS to 10.04.1 and fell into this trap. It is
very annoying and I think the importance should be increased. The
problem is that the original /etc/init.d/ssh included a test for virtual
environments (searching for some string in /proc/self/status, it's gone
after the update,
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/634900/+attachment/1565901/+files/Dependencies.txt
** Description changed:
Binary package hint: upstart
/etc/init/ssh.conf uses oom never, which causes the job to start in an
OpenVZ container.
Host:
- -
11 matches
Mail list logo
