Marc Ballarin wrote:
> I guess the proper thing here, would simply be to document this in the
> release notes. Perhaps in a general form, as there might be more
> packages affected[1] and more users might run ancient or strange kernels
> for whatever reason (Hosting environments, bad ARM
Am 28.05.2017 um 11:13 schrieb Chris Lamb:
Urgh. This makes it very difficult for me to justify this change, alas. :(
It sounds like you want to get out of this old container to be honest and
not spend your time and effort trying to work around all its problems
and issues. (You also *want* the
tags 863477 + unreproducible
severity 863477 minor
thanks
> Unfortunately, this is a provider kernel. I don't know anything about
> its patches or configuration. I don't even have /dev/kmsg or any kernel
> related file inside the container.
Urgh. This makes it very difficult for me to justify
Am 27.05.2017 um 20:13 schrieb Chris Lamb:
Can you elaborate more on exactly what this kernel is? eg. what version,
what makes Virtuozzo special here, etc. etc. Trying to work out the
scope of the problem.
Unfortunately, this is a provider kernel. I don't know anything about
its patches or
Hi Marc,
> I upgraded a hosted Virtuozzo container from Jessie to Stretch. After the
> upgrade, redis-server fails to start:
[..]
> 3. An ancient kernel and/or Virtuozzo is in use. I could not reproduce
> it on a system running the default Debian kernel 4.9.
Can you elaborate more on exactly
Package: redis-server
Version: 3:3.2.9-1
Severity: normal
Dear Maintainer,
I upgraded a hosted Virtuozzo container from Jessie to Stretch. After the
upgrade, redis-server fails to start:
May 27 12:47:44 run-parts[3349]:
redis-server.service: Failed at step NAMESPACE spawning /bin/run-parts:
Too
6 matches
Mail list logo
