Hi Pirate,
> Initially I tried editing /lib/systemd/system/redis-server.service and
> later I edited /lib/systemd/system/redis-server\@.service as well
> (edited both these files)
>
> > b) Exactly how you are editing the shipped .service file.
>
> I tried adding changing true to false initially, then adding # in front
> of the options
Ah, so you are not using:
systemctl edit --full
You are likely not actually testing the service file you believe
you are, leading to a misleading report. You might need a "systemctl
daemon-reload" too.
> apparmor was at 2.11.1-4, updating it to 2.13.2-7 fixed the above
> error, but redis still can't be started like before (same error
> message) even after stopping apparmor on the host.
^^^^^^^^
Don't you mean disabled with aa-disable or something? I'm not 100%
certain but simply stopping the service may not be enough. A reboot
with the service disabled, etc. might be what is needed (perhaps
consult the Debian Wiki on this?)
(ie. I don't think you can rule out apparmor either just yet.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] 🍥 chris-lamb.co.uk
`-
