On Wed, Feb 13, 2019 at 2:16 PM, Chris Lamb <la...@debian.org> wrote:
Hi Pirate,
> (ie. I don't think you can rule out apparmor either just yet.)
yes, culprit is apparmor only. After aa-teardown, I can start redis
service.
Great stuff. What's the next step here? Cearly this should Just
Work but I'm not sure where the bug is right now. I suggest the
next part of this process is that you re-enable apparmor with
logging.
Should we not involve apparmor maintainers? Reassign to apparmor and
add affects redis-server?
