Following up to this, I was running testing under this same openvz
kernel, and I noticed that su displayed a similar message about
setrlimit, and failed.
So perhaps the problem is really in PAM? Or multiple things just don't
work with that openvz kernel.
--
see shy jo
signature.asc
On Mon, Jul 30, 2018 at 04:50:42PM -0400, Joey Hess wrote:
> I don't get the impression the hosting provider is going to be of any help;
> they're of the bagain basement variety and are struggling with the concept
> that a newer kernel is also needed for eg, running systemd.
Oh dear.
> Based on
Colin Watson wrote:
> I grabbed the kernel source in question from
> https://wiki.openvz.org/Download/kernel/rhel6/042stab127.2 (there are a
> few newer versions, but it's apparently fairly recent and none of the
> newer ones mention anything about resource limits). I can't see
> anything in the
On Sun, Jul 22, 2018 at 11:40:40AM +0100, Colin Watson wrote:
> Do you know of a good support/bug contact for OpenVZ? I'm not familiar
> with it at all, and I think we need some idea of what the problem is
> there before we even have a clue about what a reasonable workaround in
> OpenSSH might
On Wed, Jul 11, 2018 at 02:58:00PM -0400, Joey Hess wrote:
> After upgrading some openvz container at a hosting provider to unstable,
> ssh stopped working; incoming connections closed before password prompt.
>
> In auth.log, there was this:
>
> ssh_sandbox_child: setrlimit(RLIMIT_NOFILE, { 0, 0
Package: openssh-server
Version: 1:7.7p1-2
Severity: normal
After upgrading some openvz container at a hosting provider to unstable,
ssh stopped working; incoming connections closed before password prompt.
In auth.log, there was this:
ssh_sandbox_child: setrlimit(RLIMIT_NOFILE, { 0, 0 }):
6 matches
Mail list logo
