On ചൊ, ഫെബ്രു 5, 2019 at 11:14 വൈകു, Chris Lamb
<la...@debian.org> wrote:
severity 921176 serious
thanks
Hi Pirate,
[Dropping severity as it only affects LXC right now]
It is working on the same host machine with stretch(-backports)
container (5:5.0.3-3~bpo9+2). So host machine seems fine.
Thanks for looking into this and providing some LXC basics.
(However, I am not sure why I do not have working networking inside
my container so I cannot debug it better on my end.)
But loopback is enough for redis-server, right?
On the other hand, the first thing I would do if this was working
would be to try removing more hardening features as previously
discussed on this bug number until it (likely) worked. Could you
try this please?
I tried removing all hardening features and it still won't start. I
tried to start manually by running redis-server /etc/redis/redis.conf
as root and that worked.
Also, perhaps enable some deeper logging? Or check the actual
redis-server.log file too?
There is nothing in /var/log/redis. I think its failing even before
redis-server gets a chance to log.
I found this https://github.com/systemd/systemd/issues/10032 and tried
updating systemd on host to 240-5 (from 238-5) and also updating
apparmor and disabling apparmor. But none of it worked.
